# AWS makes Continuum code vulnerability service generally available

published: 2026-11-06T10:05:31.367Z
topic: infrastructure
source: https://www.infoq.com/news/2026/11/aws-continuum-ga/?utm_campaign=infoq_content&utm_source=infoq&utm_medium=feed&utm_term=AI%2C+ML+%26+Data+Engineering
url: https://aiagentnews.io/stories/aws-makes-continuum-code-vulnerability-service-generally-available

AWS has made the code vulnerabilities capability of Continuum generally available in US East (N. Virginia) and US West (Oregon), four months after a gated preview. The service runs exploits in an isolated sandbox to confirm which findings are reachable, and proposes fixes that a person must approve before they ship.

AWS has made the code vulnerabilities capability of Continuum generally available in US East (N. Virginia) and US West (Oregon), four months after a gated preview. The service finds and validates vulnerabilities, then delivers fixes as automated patches or as pull requests in connected repositories. It builds a context graph from those repositories and the surrounding AWS environment, with an optional collector that adds resource and network data.

Validation runs each exploit in an isolated sandbox and attaches proof-of-concept code with reproduction steps, producing an attack path and a blast radius assessment. Pricing has two parts: a context fee starting at $200 per million lines protected per month, and an inference fee of $10 per Continuum inference unit. AWS's worked example of 100 million lines with 10,000 vulnerabilities at two units each comes to $218,200.

For now, every remediation starts in a mode where a person approves the proposed fix before it ships. AWS plans to let Continuum apply some classes of fix on its own once criteria such as test coverage and historical success rate are met. Penetration testing is documented separately in the AWS Security Agent User Guide and is priced at $50 per task-hour.

## Why it matters if you build agents

If you build agents that triage or fix code, expect validated findings to arrive with exploit evidence and fix proposals that still need review before merge. Budget for the per-finding inference cost, which AWS's example puts at roughly $20 per validated finding. Findings the sandbox cannot prove fall outside the described workflow, so plan a path for them yourself.