> For the complete documentation index, see [llms.txt](https://docs.ox.security/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ox.security/ox-integrations/3rd-party-integrations/cloud-security/aws/aws-automatic-connection.md). # AWS Automatic Connection Use this method to quickly connect a single AWS account. The AWS CloudFormation template automatically creates the IAM role and permissions required for OX to securely access your AWS environment and collect cloud security findings. This is the recommended connection method for most deployments. ### Step 1: Deploy the CloudFormation stack 1. Sign in to the AWS Management Console. 2. In OX, on the AWS connector page, select **CloudFormation Assume Role**. 3. On the **Create stack** page: 1. Select both acknowledgment checkboxes. 2. Select **Create stack**. 4. Wait for the stack deployment to complete. 5. Open the **Outputs** tab. 6. Copy the **OxRoleArn** value. > **Note** > > If a CloudFormation stack named **ox-security** already exists, specify a different stack name. Otherwise, the deployment fails because the stack name must be unique. ### Step 2: Connect AWS in OX 1. In OX, go to **Settings** > **Connectors**. 2. Select **AWS**.
3. In the **AWS Role ARN** field, paste the **OxRoleArn** value. 4. Select **Connect**. Verify that the connector status changes to **Connected**. --- # 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.ox.security/ox-integrations/3rd-party-integrations/cloud-security/aws/aws-automatic-connection.md?ask=&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.