AWS targets software release bottlenecks with DevOps Agent update

AWS has added release management features to its DevOps Agent, now in preview, that automatically assess code changes against organizational standards, identify release risks, and generate tests. The new capabilities aim to address bottlenecks in reviewing, testing, and safely releasing AI-generated code, potentially accelerating software delivery while improving reliability.

The problem with software development today may no longer be writing code. With AI coding assistants generating code faster than ever, the bigger challenge is reviewing, testing, and safely releasing it. AWS is betting that software teams need help with that part of the process, adding release management features to its DevOps Agent. The new features, currently in preview, automatically assess code changes against organizational standards, identify potential release risks, and generate tests tailored to individual changes before they reach production. The release readiness feature, in particular, runs the code in an AWS-managed isolated environment, executing lightweight user journey tests to verify the software builds, runs, and passes basic functional checks before the change enters the pipeline, the company wrote in a blog post. The findings of these tests can be viewed through the DevOps Agent console, as comments on pull requests in GitHub or GitLab, or can be invoked directly through IDEs via Kiro https://www.infoworld.com/article/4135310/aws-adds-design-first-and-bugfix-workflows-to-kiro.html or the Claude Code https://www.infoworld.com/article/4116598/anthropic-expands-claude-code-beyond-developer-tasks-with-cowork.html plugin, it added. Running code in isolated environments and delivering the results directly through developer tools helps address two longstanding challenges in software delivery, said Pareekh Jain https://pareekh.com/about/ , principal analyst at Pareekh Consulting. It enables teams to validate how code changes behave before deployment, catching issues that static analysis may overlook, while reducing context switching by embedding findings into existing workflows, in turn accelerating fixes, Jain said. The analyst pointed out that the release readiness capability addresses a key bottleneck in AI-driven software development: “While AI coding agents can generate code quickly, reviews, compliance checks, dependency validation, and release approvals still slow deployment.” “By automatically checking code changes against internal standards, security policies, and dependency impacts, AWS helps developers, DevOps https://www.infoworld.com/article/2255028/what-is-devops-bringing-dev-and-ops-together-for-better-software.html teams, and SREs https://www.infoworld.com/article/2257232/what-is-an-sre-the-vital-role-of-the-site-reliability-engineer.html identify issues earlier, reduce manual review effort, and improve release confidence,” Jain added. These gains in productivity for developers could also translate into tangible business benefits for CIOs, according to Jain. “Release readiness as a feature could help enterprises capture more value from AI-generated code while reducing operational overhead by eliminating the need for additional QA and DevOps resources. This means that they can accelerate software delivery without sacrificing reliability,” the analyst noted. While release readiness reviews focus on assessing whether a code change is safe to move through the delivery pipeline, AWS is also adding a separate feature aimed at validating how those changes behave in production-like environments. Named autonomous release testing, the new capability generates and runs change-specific test plans for web and API-based applications in customer-provisioned, production-like environments before the change actually merges, the company wrote in the blog post. For Jain, autonomous release testing is “even more” important for developers and SREs as it “automates one of the most time-consuming parts of software delivery.” “Developers spend less time creating and maintaining tests, while SREs benefit from fewer rollbacks and improved system reliability,” Jain said. These benefits stem from the feature’s ability to automatically generate tests tailored to individual code changes, covering functional correctness, behavioral regressions, and integration scenarios that might otherwise require significant manual effort, Jain added. However, AWS is not alone in trying to bring AI deeper into the software delivery lifecycle. Microsoft-owned GitHub has been expanding Copilot’s code review capabilities, allowing the service to automatically review pull requests https://docs.github.com/en/copilot/concepts/agents/code-review , suggest fixes, and provide feedback directly within developer workflows. Google, meanwhile, has been steadily broadening the scope of Gemini Code Assist https://docs.cloud.google.com/gemini/docs/code-review/review-repo-code beyond code generation to support software development tasks such as code review and developer assistance. AWS’s differentiation, though, according to Jain, lies in tying those capabilities to release management and operational workflows that span development and production environments. For development teams interested in evaluating DevOps Agent’s new capabilities, AWS said both features are available in preview at no additional cost in the US East N. Virginia region. AWS DevOps Agent, billed per agent-second, is included in the AWS Free Tier for new customers. Additionally, new AWS DevOps Agent customers receive a 2-month free trial starting with their first operational task after general availability. Each trial month includes up to 10 agent spaces, 20 hours of investigations incident response , 15 hours of evaluations incident prevention , and 20 hours of on-demand SRE tasks chat , the company said. Once those limits are exhausted, customers are charged based on consumption, with investigations, evaluations, and on-demand SRE tasks each priced at $0.0083 per agent-second, AWS added. A prerequisite for using the new release management features includes connecting at least one GitHub or GitLab repository to an AWS DevOps Agent Space.