> For the complete documentation index, see [llms.txt](https://docs.secoda.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.secoda.co/integrations/security/connecting-via-aws-cross-account-role.md).
# Connecting via AWS Cross Account Role
### **Getting Started with AWS Cross Account Roles**
To start the process of connecting your AWS account to Secoda, navigate to the [New Integrations](https://app.secoda.co/integrations/new) page and select an AWS integration. Select the "Role" Option.
Cross-account roles are a mechanism provided by AWS to allow you to grant secure access to Secoda without requiring that you hand over sensitive secrets like Secret Access Keys.
The Secoda UI will display an **AWS Account ID** and a randomly generated **External ID**, as shown below, which must be plugged into an IAM Role you create in your AWS account. Store these values for future reference.
Neither the Account ID nor the External ID are secrets, so don't worry about keeping them somewhere secure.
1. From your AWS console, navigate to **IAM** > **Roles** and click **Create Role**.
2. Under **Select type of trusted entity**, choose **Another AWS account**.
3. Proceed to attach permissions to the role, choose a name, then create the role.
* The exact permission policies you attach depend on which Secoda features you intend to use. Consult the documentation for those services for further guidance. Regardless, make sure to add the permissions `sts:AssumeRole` to your policy.
4. Copy the **Role ARN** from AWS IAM and paste it into the **Role ARN** field in Seoda. Click **Create** to complete the process.
For more information, read [AWS's tutorial](https://docs.aws.amazon.com/IAM/latest/UserGuide/tutorial_cross-account-with-roles.html) on delegating access cross-account using IAM Roles.
---
# 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.secoda.co/integrations/security/connecting-via-aws-cross-account-role.md?ask=&goal=
```
`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.
