> 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.md).

# AWS

Amazon Web Services (AWS) is a cloud computing platform provided by Amazon.

Amazon Elastic Container Registry (Amazon ECR) is Amazon's managed container registry service for storing and managing container images.

Connecting AWS to OX enables OX to analyze your cloud environment and identify cloud security risks. The same integration also enables OX to analyze container images stored in Amazon ECR and consolidate cloud and container security findings in a single platform.

### Choose a connection method

OX supports multiple methods for connecting AWS. Choose the method that best fits your environment.

| Method                                                                                                        | Recommended for                                                                                                                         |
| ------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- |
| [**Automatic**](/ox-integrations/3rd-party-integrations/cloud-security/aws/aws-automatic-connection.md)       | Most deployments. OX provisions the required AWS IAM role and permissions by using AWS CloudFormation.                                  |
| [**Manual**](/ox-integrations/3rd-party-integrations/cloud-security/aws/aws-manual-connection.md)             | Organizations that prefer to create and manage the IAM role and permissions themselves.                                                 |
| [**Organization**](/ox-integrations/3rd-party-integrations/cloud-security/aws/aws-organization-connection.md) | Organizations that use AWS Organizations and want to onboard multiple AWS accounts through a management account.                        |
| [**Terraform**](/ox-integrations/3rd-party-integrations/cloud-security/aws/aws-with-terraform.md)             | Organizations that manage AWS infrastructure using Terraform and want to provision the AWS integration as infrastructure as code (IaC). |

### Terminology mapping

| AWS                                  | OX                 |
| ------------------------------------ | ------------------ |
| AWS Account                          | Cloud Account      |
| AWS Organizations Management Account | Management Account |
| AWS Organizations Member Account     | Cloud Account      |
| IAM Role                             | Connector Role     |
| Role ARN                             | Role ARN           |
| External ID                          | External ID        |
| AWS Organizations                    | AWS Organization   |
| Amazon EKS Cluster                   | Kubernetes Cluster |
| Amazon ECR Repository                | Container Registry |


---

# 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.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.