What AWS announced
AWS announced general availability of Continuum for code vulnerabilities on October 22. AWS says it builds a context graph from repositories and cloud resources to prioritize issues and propose remediation pull requests. This announcement concerns the code-vulnerability capability, not every Continuum feature.
Evidence needs a closer look. The launch walkthrough distinguishes verdicts based on static analysis from sandbox demonstrations for findings it can reproduce. A proposed patch is not evidence that a fix was merged or deployed.
Check approval, access, and billing
Sources differ on automation. The short announcement describes an Enforce mode, while the launch blog says fixes need human approval and places automatic fixes in the future. Check the controls actually available in your account.
At launch, the detailed post lists US East (N. Virginia) and US West (Oregon). The pricing page lists a monthly context fee and usage-based inference fees. Keep those separate from penetration-testing charges, and confirm current access before planning a rollout.
Our take
For AI geeks and experienced AWS developers, begin with the evidence attached to each finding, the permissions granted, and the proposed diff. Keep review, merge, deployment, and verification as separate checkpoints. A working demonstration can support a specific finding; it does not establish complete coverage. We have not used Continuum or reproduced its results.