> For the complete documentation index, see [llms.txt](https://docs.kangal.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kangal.dev/integrations/aws.md).

# AWS

The AWS integration validates an AWS identity and returns lightweight account and region metadata. It signs direct AWS Query API requests with Signature Version 4.

## Required values

| Type          | Field               | Required | Notes                               |
| ------------- | ------------------- | -------- | ----------------------------------- |
| Configuration | `region`            | Yes      | AWS region, for example `us-east-1` |
| Secret        | `access_key_id`     | Yes      | Dedicated AWS access key ID         |
| Secret        | `secret_access_key` | Yes      | Matching secret access key          |
| Secret        | `session_token`     | No       | Required for temporary credentials  |

The identity must be allowed to call STS `GetCallerIdentity`. IAM `ListAccountAliases` and EC2 `DescribeRegions` provide the optional details.

## What sync calls

1. STS `GetCallerIdentity` in the configured region. Failure stops the sync.
2. IAM `ListAccountAliases` against the global IAM endpoint.
3. EC2 `DescribeRegions` with `AllRegions=true` in the configured region.

Alias and region failures are recorded as warnings and do not fail a sync after identity validation succeeds.

## Metadata returned

The result contains `account_id`, `arn`, `user_id`, `account_aliases`, `region`, `region_count`, and `regions`. A `warnings` array is included when the IAM or EC2 request fails.


---

# 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.kangal.dev/integrations/aws.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.