> 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/access-keys.md).

# Access keys

Access keys combined with an S3-compatible endpoint are used with third-party applications. They are used to **make programmatic calls to AWS S3 API actions**.

There are two types of access keys:

* **Access key ID**
* **Secret access key**

Access and secret keys are generated under the **"IAM → keys"** tab in the console menu bar. To create a new access key, simply navigate to the menu and click **"Add key"** on the top. When creating a new key pair, you may use the respective button to copy or download it.

{% hint style="warning" %}
Please copy and save the secret key somewhere once it's created. The secret key is only shown once! After you leave the window, the secret key is hidden and you will need to create a new key pair to obtain a complete set of keys.
{% endhint %}

{% hint style="info" %}
For your protection, you should **never share your secret keys** with anyone.
{% endhint %}


---

# 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 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/access-keys.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 `automate deployments from our CI pipeline` 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.