What is AWS Inspector and where does it fit in a DevSecOps pipeline?
Quick Answer
AWS Inspector is used for AWS-native vulnerability scanning, running at the image stage. Explain the class of problem it catches, why catching it there is cheaper than catching it in production, and how it reports findings back to developers.
Detailed Answer
Describe AWS Inspector by the failure it prevents, not by its feature list. It belongs to AWS-native vulnerability scanning and runs at the image stage of delivery, which matters because the cost of fixing a defect rises sharply the later it is found — the core argument behind shifting security left.
Strong answers cover continuous scanning of EC2, Lambda and ECR images, the SSM agent dependency for EC2, network reachability analysis, the Inspector risk score vs raw CVSS, suppression rules, and routing findings into Security Hub or EventBridge. Interviewers also listen for the operational side: who owns the rules, how findings reach the developer who introduced them, how false positives get suppressed without silently disabling coverage, and what the break-glass path is when a fix genuinely cannot ship in time.
Tie it to the wider toolchain. Security scanning is only useful when its output is actionable, deduplicated across tools, and attached to a specific commit, image digest or resource — otherwise teams learn to ignore it.
Code Example
# Where AWS Inspector sits in the pipeline # stage: image # 1. run the scan against the artifact produced by this stage # 2. compare findings against the agreed severity threshold # 3. an EventBridge rule alerting or blocking promotion on a Critical finding # 4. publish the report so developers see it on the commit or pull request
Interview Tip
Anchor AWS Inspector to a stage and a gate: what it scans, when it runs, and what makes the build stop.