 |
VOOZH | about |
|
VOOZH | about |
We’re so glad you’re here. You can expect all the best TNS content to arrive Monday through Friday to keep you on top of the news and at the top of your game.
Check your inbox for a confirmation email where you can adjust your preferences and even join additional groups.
Follow TNS on your favorite social media networks.
Become a TNS follower on LinkedIn.
Check out the latest featured and trending stories while you wait for your first TNS newsletter.
The bottleneck in software development has moved.
Writing code is no longer the constraint. Getting it safely to production is. AWS is targeting that shift with two new capabilities added to its AWS DevOps Agent, announced Wednesday at the AWS Summit New York.
The new release management features, now available in preview, extend the DevOps Agent beyond its existing post-deployment operations work into the delivery pipeline itself. Specifically, AWS is adding a release readiness review and an autonomous release testing capability. Both are aimed at helping review and test processes keep pace with the accelerating volume of AI-generated code.
“With so much code that is being written today by AI agents, a real bottleneck has shifted,” Neha Goswami, director of Agentic AI for Agentic DevOps at AWS, tells The New Stack. “It’s less about writing of the code, and it’s really about how to get this thing out — how do we get it out in production, and how do we get it out safely.”
The first capability evaluates code changes against production requirements before they merge. The agent checks for cross-repository dependency risks that could affect other services, access control changes measured against the AWS Well-Architected Framework, and compliance with any internal standards the team has defined. Those standards are written in plain English via a Global Instructions editor. No additional tooling is required. When no standards are provided, the agent falls back to general best practices.
As part of the review, the agent runs the software in an AWS-managed isolated environment, executing lightweight user journey tests to verify the build runs and passes basic functional checks before entering the pipeline. The output is has three options: BLOCK, Proceed with Caution, or Safe to Release. Findings come out in the AWS DevOps Agent console and as comments on pull requests in GitHub or GitLab, and can also be invoked directly from the IDE via the Kiro plugin or Claude Code plugin.
The dependency-tracking dimension is what Goswami says makes the tool different from existing static analysis.
“This is going really beyond just static code analysis,” she says. “Even in the low users, we have been able to find some issues where the repo-level dependency was not being tracked by any of our existing solutions.” In one early case, a change that had already passed human review was blocked when the agent identified a cross-repository dependency conflict the reviewer had missed.
The second capability goes further into the delivery process, generating and running change-specific test plans for web and API-based applications in customer-provisioned, production-like environments before the change merges. Rather than executing a static test suite, the agent reasons about what the change does and builds tests tailored to it. These tests cover functional correctness, behavioral regressions, and integration scenarios. Every run produces structured artifacts including metrics, logs, traces, and an execution summary.
The distinction between where each feature runs matters: the readiness review uses an AWS-managed isolated environment; the release testing runs in the customer’s own provisioned environment. That separation puts more responsibility and control on the customer side for the testing phase.
Goswami, a 22-year Amazon veteran who started in internal developer tooling, framed AWS’s competitive edge as its ability to benchmark at internal scale. AWS DevOps Agent’s release management features were tested against Amazon’s own engineering workflows before external release, with thousands of internal developers using the tooling.
“We have coded these agentic capabilities just the way we do this work,” she says, pointing to the operational excellence practices baked into how the agent decides what to test and what guardrails to apply. “A lot of what you would see is the best practices and the operational excellence that we have built into our culture, the agent acts in the same way.”
The release readiness review and autonomous release testing features are available now in preview, at no additional cost, in the US East (N. Virginia) region only. GitHub and GitLab are the supported source control platforms at launch. General availability is expected in the coming months, though AWS did not provide a specific date.
AWS DevOps Agent has been generally available for post-deployment operations, such as incident investigation, root cause analysis, and mitigation recommendations, since earlier this year. This new release marks its expansion into the pre-deployment side of the software delivery lifecycle, completing the loop from code creation to production, the company says.
