Amazon Inspector
by Amazon Web Services
Amazon Inspector scans EC2 instances, container images in ECR and Lambda functions, then reports findings by CVE, severity and resource, with coverage, aggregations and SBOM exports on top. Vulnerability counts only mean something when tied to owners and fix dates. A Lake copy lets you join Inspector with tickets and deployment data to measure how fast each team actually patches.
- Category
- IT, Security & Monitoring
- Type
- Vulnerability management
- Interface
- REST API
- Built with
- Connect Anything
- Credentials
- AWS access keys
02Data
What you can sync.
- Findings
- Coverage
- Finding aggregations
- Sbom exports
Keep Amazon Inspector findings in your own Lake, on your servers, and report on it with the rest of IT.
Need more? Name any other Amazon Inspector data the API returns, and the AI adds it to the connector.
03Credentials
Credentials you will need.
- AWS access keys
Amazon Inspector uses AWS access keys. You add the credentials once, when the AI asks for them, and it tells you where to create them in Amazon Web Services if you need help.
04Questions
Questions you can answer.
Once Amazon Inspector data is in your Lake, ask an AI Mind in plain words or build the answer in DataPrism BI.
- What is the mean time to remediate critical findings, by account and resource type?
- Which container images in ECR carry the same CVE across many repositories?
- Which packages listed in SBOM exports show up in images with critical findings?
- What share of EC2 instances and Lambda functions are not covered by scanning?
05How it works
How it works in DataMind.
-
Pick Amazon Inspector.
Open Lake, pick Amazon Inspector in the source picker and name the connection. Connect Anything opens with a ready prompt that points the AI at the Amazon Inspector API docs.
-
Answer a few questions.
The AI reads the Amazon Inspector documentation, then asks which credentials you will use, which data to sync (for example findings and coverage), whether you want a one-time load or a recurring sync, and which accounts or filters apply.
-
Your data lands in Lake.
The connector agent writes a Python connector for Amazon Inspector, tests it against the live API and shows you sample rows. Then the data loads into your Lake on your schedule, ready for the Warehouse, DataPrism BI and AI Minds.
06Pairs
Works well with Amazon Inspector.
Sources teams join with Amazon Inspector in the Warehouse, each one connected the same way.