> 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/bring-in-findings/container-and-cloud-scanners/aws-inspector.md).

# AWS Inspector

Bring AWS Inspector container vulnerability findings into Konvu.

AWS Inspector continuously scans the container images in your Amazon ECR repositories. The Inspector integration imports those container findings into Konvu, where they feed the same triage flow and evidence you already use for SCA and SAST.

Inspector findings arrive through your **AWS cloud connection**. The same connection also brings in Amazon ECR basic scanning findings — see [Connect AWS](/konvu/get-started/connect-your-environment/cloud/amazon-web-services.md) for the account setup.

## What this integration brings in

For each container finding:

* Vulnerability identifier (CVE)
* Affected package name and version
* Severity (critical, high, medium, low)
* The ECR repository / image the finding came from
* Observed date

Konvu imports container findings. Inspector findings and ECR basic scan findings are listed separately in the AWS connection's detail drawer, under **Inspector findings** and **Basic scanning — ECR findings**.

{% hint style="info" %}
The AWS connection is configured at the company level. Each connection maps to one AWS account in one region.
{% endhint %}

## Enable Inspector findings

1. Connect your AWS account under [**Connect Your Environment > Cloud > Amazon Web Services**](/konvu/get-started/connect-your-environment/cloud/amazon-web-services.md).
2. On the **IAM setup** step, leave **Verify AWS Inspector permissions** on. This grants the read-only `inspector2` permissions Konvu needs to pull Inspector findings.

If you connect AWS with Inspector verification turned off, Konvu imports ECR basic scan findings only — no Inspector findings.

{% hint style="info" %}
Inspector findings require AWS Inspector to be enabled in the connected account and region. Enable it in the AWS console first if you haven't already.
{% endhint %}

## Verify findings are flowing

1. Go to **Integrations** in Konvu and open the AWS connection. The detail drawer shows the **Inspector findings** count.
2. Navigate to the **Triage** page — your Inspector container findings should appear there.

If the count stays at zero, confirm that AWS Inspector is enabled in the connected region, that the account has scanned ECR images, and that you connected with **Verify AWS Inspector permissions** on.

## Next steps

* [Connect AWS](/konvu/get-started/connect-your-environment/cloud/amazon-web-services.md) — full AWS account connection and ECR registry setup
* [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/bring-in-findings/container-and-cloud-scanners/aws-inspector.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.