English edition · cyberattaques.org in FrenchFrançais
IT news

AWS Continuum for code vulnerabilities reaches general availability

AWS has made Continuum for code vulnerabilities generally available, a service that uses AI to find, validate and prioritise flaws in code and then proposes fixes as pull requests. It is aimed at development and security teams managing code in AWS environments.

What to do now Illustration photo (source code security review)

Amazon Web Services announced on its news blog on 22 October 2026 that AWS Continuum for code vulnerabilities is now generally available. The service focuses on application code security.

According to AWS, the service uses artificial intelligence to identify vulnerabilities in the code running in a customer's environment. It then validates them and ranks them by priority. For each confirmed issue, it produces a fix that is ready for review and delivered as a pull request.

AWS presents this as a replacement for the usual manual process. The company says that process takes hours of investigation, followed by days of coordination between teams before a fix is applied.

The announcement does not cover pricing, regional availability, supported programming languages or compatible code hosting platforms. It also does not explain how vulnerabilities are validated. Teams considering the service will need to check the AWS documentation for those details.

Because the proposed fixes arrive as pull requests, they still pass through human review and whatever code review workflow a team already has. Engineers keep control over which changes are merged.

Action plan

What to do now

  1. Check the AWS documentation for pricing, regions, supported languages and supported code repositories before planning adoption.
  2. Trial the service on a non-critical repository before rolling it out more widely.
  3. As general good practice, have every generated pull request reviewed and run through your normal testing pipeline before it is merged.
  4. Review the access the service is granted to code and repositories, and keep it to the minimum required.

Sources