Amazon Inspector uses separate scan types for running workloads and machine images. Choose the coverage and finding delivery path that match the resource.
EC2, ECR, and Lambda scanning
Amazon Inspector finds vulnerable software and unintended network exposure. A findingA finding reports a vulnerability or unintended exposure detected in a resource. is a report of a detected issue. A CVEA CVE entry identifies a publicly known software vulnerability., or Common Vulnerabilities and Exposures entry, identifies a publicly known vulnerability.
How it works
- For private ECR images, use enhanced scanning and choose scan on push or continuous scanning. Continuous scans respond to relevant new CVEs while images remain eligible.
- For Lambda, scan dependencies in functions and layers. Add code scanning to inspect custom application code.
| Workload | Scan method | Selection cue |
|---|---|---|
| Private ECR image | Enhanced scanning | Operating system and language packages |
| Lambda function | Standard plus optional code scanning | Dependencies plus custom code |
Exam cues
- If the question says container images need rescanning for new CVEs, think ECR enhanced continuous scanning, because it reassesses eligible images.
- If the question says Lambda dependencies are covered but custom code is not, think Lambda code scanning, because standard scanning covers dependencies.
Remember
- ECR enhanced scanning offers scan on push and continuous scanning.
- Lambda code scanning requires standard scanning.
Trap: Lambda standard scanning checks dependencies, not custom application code. Add Lambda code scanning to inspect custom code.
From the AWS docs (4)
- Amazon Inspector finds software vulnerabilities and unintended network exposure in supported workloads.
- ECR enhanced scanning uses Inspector to find operating system and programming language package vulnerabilities in private registry images.
- ECR enhanced scanning supports scan on push and continuous scanning; continuous scanning rescans eligible images when relevant new CVEs appear.
- Lambda standard scanning checks dependencies in functions and layers; optional Lambda code scanning checks custom code and requires standard scanning.
AMI scanning and finding prioritization
Amazon Inspector machine image scanning checks Amazon Machine Images (AMIs), the templates used to launch EC2 instances. It examines their disk snapshotsAn EBS snapshot is a backup of the data on an EBS volume., so an image can be inspected without starting a server.
How it works
- Activate machine image scanning separately from EC2 instance scanning. The default continuous mode follows in-scope AMIs and new relevant CVEs.
- Use an on-demand scan for a single image at a particular point in time. It does not enroll that image in continuous scanning.
- For EC2 package findingsA finding reports a vulnerability or unintended exposure detected in a resource., examine the Inspector score alongside its base Common Vulnerability Scoring SystemCVSS describes the severity of a vulnerability using a score and security metrics. (CVSS) score. Reachability and exploitabilityExploitability describes conditions that affect whether a vulnerability can be used in an attack. add context for prioritization.
- Route finding events through EventBridge, an event router that sends matching events to targets such as Lambda or SNS. Use the Security Hub CSPM integration for supported findings.
Exam cues
- If the question says scan both golden AMIs and running instances continuously, think separate machine image and EC2 scan types, because they inspect different resources.
- If the question says check one build image without activating Inspector, think on-demand machine image scanning, because it runs a single evaluation.
- If the question says an on-demand AMIAn AMI is an image used to launch EC2 instances. scan is missing from Security Hub CSPM, think EventBridge or the EC2 console, because those results bypass Inspector’s normal findings views.
Remember
- Machine image scanning defaults to continuous mode.
- Continuous AMI scans react to image creation, copy, registration, enablement, and new CVEs within the configured scope.
- On-demand results are absent from Inspector’s console,
ListFindings, and Security Hub CSPM. - The Inspector score for EC2 package findings adds environment context; Ubuntu Linux instances do not have this score.
Trap: A CVSS base score need not come from NVD. Inspector also uses supported vendor scores.
Inspector publishes a finding event.
An EventBridge rule sends the matching event to a Lambda response.
From the AWS docs (9)
- Machine image scanning is activated separately from EC2 scanning.
- Inspector scans owned AMIs for operating system and programming language package vulnerabilities using their backing EBS snapshots, without launching instances.
- Continuous is the default machine image scan mode; in-scope images are scanned on creation, copy, registration, or enablement and rescanned for new CVEs.
- An on-demand machine image scan evaluates one AMI once, needs no Inspector activation, and does not enroll the image in continuous scanning.
- On-demand AMI findings are delivered through EventBridge; they do not appear in the Inspector console, ListFindings, or Security Hub CSPM, but are viewable in the EC2 console.
- For EC2 package vulnerability findings, the Inspector score combines CVSS base information with environment details including network reachability and exploitability.
- Inspector uses supported vendor CVSS base scores and otherwise NVD scores; the Inspector score is not available for Ubuntu Linux instances.
- Inspector publishes finding events to EventBridge, where rules can route them to response targets such as Lambda or SNS.
- With the Inspector integration active, Security Hub CSPM receives supported Inspector findings for centralized security analysis.
Scan coverage and Classic assessments
Amazon Inspector uses workload scan types to assess resources. Understanding how EC2 inventory is collected and which Lambda functions qualify helps explain scan coverage. First activation enables EC2, ECR, and Lambda standard scanning.
How it works
- For EC2, Inspector compares collected software metadata with security advisories. Agent-based scanning uses Systems Manager AgentSSM Agent is software on a server that enables Systems Manager to manage it., while agentless scanning uses EBS snapshotsAn EBS snapshot is a backup of the data on an EBS volume.. Hybrid mode combines the methods for managed and eligible unmanaged instances.
- For Lambda, check the function’s eligibility: a supported runtime,
$LATEST, recent invocation or update, and no exclusion tag. - Recognize the historical Inspector Classic assessment model: EC2 instances launched from golden AMIs used an Inspector agent, tag-selected assessment targets, and assessment templates.
Exam cues
- If the question says an EC2 instance is managed or eligible but unmanaged, think hybrid scanning, because it uses agent-based and agentless methods respectively.
- If the question says a Lambda function has not been invoked or updated for more than 90 days, think scan eligibility, because recent activity is required.
- If the question says an Inspector agent, assessment targets, and templates, think Inspector Classic, because those describe its historical assessment model.
Remember
- Hybrid is the default EC2 scan mode.
- Lambda eligibility requires a supported runtime,
$LATEST, an invocation or update within 90 days, and no exclusion tag. - Lambda code scanning and machine image scanning require separate activation.
- Inspector Classic support ended May 20, 2026.
Trap: An Inspector agent and tag-selected assessment targets describe Inspector Classic. Current Inspector uses workload scan types, and Classic support has ended.
From the AWS docs (6)
- EC2 scans compare collected software metadata with security advisories; agent-based scanning uses Systems Manager Agent and agentless scanning uses EBS snapshots.
- Hybrid is the default EC2 scanning mode and uses agent-based scanning for managed instances and agentless scanning for eligible unmanaged instances.
- Historically, Inspector Classic assessed EC2 instances launched from golden AMIs using an Inspector agent, tag-selected assessment targets, and assessment templates.
- Amazon Inspector Classic reached end of support on May 20, 2026.
- First activation enables EC2, ECR, and Lambda standard scanning; Lambda code scanning and machine image scanning require separate activation.
- Eligible Lambda functions use a supported runtime, are $LATEST, were invoked or updated within 90 days, and are not excluded by tags.
Flashcards
Nothing to review here right now. Pick other topics or another filter.
·
All 11 cards as a list
Which AWS service finds vulnerable packages in EC2 instances, private ECR images, and Lambda functions?
Amazon Inspector. Select the scan type for each workload; findings identify software vulnerabilities and unintended network exposure.
A team wants private ECR images reassessed when new relevant CVEs appear after image push. Which Inspector setting fits?
ECR enhanced continuous scanning. It rescans images that remain eligible when relevant new CVEs appear.
A team enabled Amazon Inspector Lambda standard scanning and wants flaws in its own function code detected. What must it add?
Lambda code scanning. Standard scanning checks dependencies; code scanning checks custom application code.
A team needs ongoing scans of golden AMIs and running EC2 instances, with automated finding response. Is Inspector EC2 scanning enough?
Enable EC2 scanning and separately activate continuous machine image scanning. Use EventBridge finding events to trigger a response.
What does the Amazon Inspector score add to the base CVSS score for an EC2 package finding?
Environment context, including network reachability and exploitability. Inspector uses supported vendor base scores or NVD scores; the score is unavailable on Ubuntu Linux instances.
A build pipeline needs one vulnerability check of a new AMI without enrolling the account in Inspector. Which scan fits?
An on-demand machine image scan. It checks one AMI once and does not start continuous scanning.
A team runs an on-demand Inspector AMI scan but finds no result in ListFindings or Security Hub CSPM. Where should it look?
Receive the findings through EventBridge, or view them in the EC2 console. On-demand AMI findings are absent from Inspector ListFindings and Security Hub CSPM.
Must Amazon Inspector launch an EC2 instance to scan an owned AMI for package vulnerabilities?
No. Machine image scanning reads software inventory from the AMI backing EBS snapshots.
How does Amazon Inspector collect EC2 software information, and what scan mode is the default?
Systems Manager Agent or EBS snapshots. The default hybrid mode combines agent-based scanning for managed instances with agentless scanning for eligible unmanaged instances.
An older Amazon Inspector design uses tag-selected assessment targets, assessment templates, and an Inspector agent. Which version is this?
Inspector Classic. Its support ended May 20, 2026. Current Inspector uses workload scan types.
An Amazon Inspector Lambda function has not been invoked or updated for more than 90 days. Why might it be outside scan coverage?
Lambda scan eligibility requires an invocation or update within 90 days, a supported runtime, $LATEST, and no exclusion tag.