> For the complete documentation index, see [llms.txt](https://docs.impossiblecloud.com/impossible-cloud-help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.impossiblecloud.com/impossible-cloud-help/impossible-cloud-storage-guide/cli-user-guide/aws-cli-credentials-and-config-chain.md).

# AWS CLI Credentials & Config chain

If you use the AWS CLI tool for your operations and application implementation, it's important to note that the CLI searches for credentials and configuration data in a specific hierarchical order.

### Command Line Options

For example: using options like "--profile", "--region", "--output" etc...

If the necessary data is not found through command line options, the CLI will check for environmental variables.

### Environmental Variables

AWS\_ACCESS\_KEY\_ID

AWS\_SECRET\_ACCESS\_KEY

AWS\_SESSION\_TOKEN

AWS\_DEFAULT\_REGION

... and so on. If the data is still not found, the CLI will look for it in the CLI credentials file, which can be found at the following locations:

1. For Linux: **\~/.aws/credentials**
2. For Windows: **C:\Users\\\<user-name>\\.aws\credentials**

Finally, if the data is still not found, the CLI will search for it in the CLI configuration file, which can be found at the following locations:

1. For Linux: **\~/.aws/config**
2. For Windows: **C:\Users\<user-name>.aws\config**


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.impossiblecloud.com/impossible-cloud-help/impossible-cloud-storage-guide/cli-user-guide/aws-cli-credentials-and-config-chain.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.