> For the complete documentation index, see [llms.txt](https://docs.konvu.com/konvu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.konvu.com/konvu/get-started/connect-your-environment/cloud/amazon-web-services.md).

# Amazon Web Services

Connect your AWS account so Konvu can read container findings from AWS Inspector and Amazon ECR.

Connecting your AWS account lets Konvu read container vulnerability findings from your AWS environment. A single connection covers:

* **AWS Inspector** — container findings from Inspector's continuous scanning of your ECR images (see [AWS Inspector](/konvu/get-started/bring-in-findings/container-and-cloud-scanners/aws-inspector.md) for what flows into triage).
* **Amazon ECR basic scanning** — findings from ECR's built-in image scanning.
* **Your Amazon ECR container registry** — Konvu reads the ECR repositories in the connected account and region.

The integration covers container images in **Amazon ECR**; it does not connect non-AWS registries (such as GCR, Docker Hub, or Harbor).

{% hint style="info" %}
The AWS connection is configured at the organization level. Each connection maps to one AWS account in one region — connect again to bring in additional accounts or regions.
{% endhint %}

## Prerequisites

* An AWS account with Amazon ECR repositories
* Permission in that account to create an IAM role (via Terraform or the IAM console)
* AWS Inspector enabled in the account/region if you want Inspector findings (ECR basic scanning works without it)

## Connect your AWS account

Konvu connects by assuming a read-only IAM role in your account, scoped with an external ID that Konvu generates for you. You don't share access keys.

1. Go to the [integrations page](https://app.konvu.com/configuration/integrations) in Konvu and click **Connect AWS**.
2. **Region** — choose the AWS region to connect. Konvu shows the **External ID** for this connection on the same step (read-only; you can regenerate it). This value is already baked into the IAM policy Konvu generates in the next step.
3. **IAM setup** — Konvu generates the IAM role for you, with your external ID already included. Pick a tab:

   * **Terraform** (default) — copy the HCL block and apply it in your environment.
   * **JSON** — copy the trust policy and the permissions policy into a role in the AWS IAM console.

   Leave **Verify AWS Inspector permissions** on (the default) to include Inspector findings. Turn it off to grant ECR-only access — Konvu will then import ECR basic scan findings only. Create the role in AWS, then copy the resulting **role ARN** back into Konvu.
4. **Account details** — enter:
   * **Nickname** (optional) — a label for this connection, e.g. `Staging ECR`
   * **AWS account ID** — the 12-digit account ID
   * **IAM role ARN** — the ARN of the role you just created
5. Click to save. Before the connection is created, Konvu assumes the role with your external ID and runs a read-only check against ECR (and Inspector, if you left verification on). The connection is only saved if the check succeeds; otherwise the error is shown inline on the field (for example, the role assumed successfully but can't call the required ECR read APIs).

### IAM permissions Konvu needs

The generated policy is read-only. It requests:

* **ECR (always):** `ecr:GetAuthorizationToken`, `ecr:BatchCheckLayerAvailability`, `ecr:BatchGetImage`, `ecr:DescribeImages`, `ecr:DescribeImageScanFindings`, `ecr:DescribeRepositories`, `ecr:GetDownloadUrlForLayer`, `ecr:ListImages`
* **Inspector (optional, when verification is on):** `inspector2:ListFindings`, `inspector2:ListCoverage`, `inspector2:BatchGetFindingDetails`

## Your Amazon ECR container registry

ECR is connected as part of the AWS connection above — there is no separate registry step. Once the role is in place, Konvu reads the ECR repositories in the connected account and region and imports their image findings. It scans the repositories it finds in that account/region; there is no per-repository selection.

To cover ECR in more than one account or region, add the AWS connection again for each account/region pair.

## Verify the connection

After connecting, Konvu runs an initial sync. To confirm:

1. Go to **Integrations** in Konvu and open the AWS connection. The detail drawer shows your **ECR repositories**, **Container images**, and finding counts (**Inspector findings**, **Basic scan findings**).
2. Navigate to the **Triage** page — your container findings should appear there.

If counts stay at zero, verify that the account/region has ECR repositories with scanned images, that the role ARN and external ID are correct, and — for Inspector findings — that AWS Inspector is enabled in that region.

## Next steps

* [AWS Inspector](/konvu/get-started/bring-in-findings/container-and-cloud-scanners/aws-inspector.md) — what Inspector container findings bring into Konvu
* [Triage findings](/konvu/triage-and-remediation/exploitability-assessment.md) to review Konvu's assessments on your container findings


---

# 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.konvu.com/konvu/get-started/connect-your-environment/cloud/amazon-web-services.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.