Andrew Krug
Tara Schofield
Max Saltonstall
Kunal Batra
After four days of AWS re:Invent—a 65,000-step marathon that included 60,000 attendees spread across five Las Vegas campuses—and navigating the latest installment of this 13-year-old cloud pilgrimage, we’re all a little dehydrated but significantly wiser. The volume of announcements felt less like a single flood and more like a river branching into three powerful currents. Making sense of this massive technological convergence requires zooming out.
This post is your retroactive field guide to connecting the dots that define the future of the cloud. Below, we’ll dive into the biggest announcements from three crucial domains:
Everyone is building AI agents, but how do you debug a nondeterministic black box? If one thing was clear in re:Invent’s opening keynote, it’s that builders have more capability than ever to train models, build agents, and provide value by using technologies like AWS Trainium 3 and Amazon Bedrock AgentCore. This evolving technology lowers the barrier to entry for almost anyone to build faster than ever before. But how do you hold these platforms accountable when it comes to reliability, safety, and security?
The lack of confidence combined with the staggering MIT study from August 2025 that showed most business generative AI pilots are failing necessitates increased observability and security controls. Last year at DASH, we launched LLM Observability, a way to continuously observe, secure, and act on findings from the LLMs you use. Just in time for re:Invent, we also launched two features in LLM Observability to help builders see the full picture of their stack: support for Strands Agents and for Amazon Bedrock Agents, both generally available. In order to ensure both safety and security, we released a set of detection rules to help drive down risk in the configuration for Bedrock instances.
The AWS commitment to empowering their customers and partners to build safely on their AI platform was also echoed in the release of Bedrock AgentCore Policies, enabling teams to have fine-grained control of identity and access throughout their agentic workflows.
When it comes to AI, builders now have more choice than ever. AWS dropped 18 fully managed open weight models for Bedrock—the largest simultaneous model expansion to date—spanning Gemma, Mistral, Qwen, NVIDIA Nemotron, and more. Pair that with the new serverless model customization capability in SageMaker AI, which lets teams fine-tune with reinforcement learning and direct preference optimization without managing infrastructure, and suddenly the number of variables explodes. This raises a new challenge: How do I tune all of these models for the best results?
LLM Observability now includes LLM Experiments and Playground, where you can experiment and optimize your LLM applications before pushing to production. In addition to model tuning, we released Prompt Tracking to help monitor performance, latency, and drift across prompt versions.
According to this year’s State of Cloud Security, over 84% of customers use more than one AWS account and 3 in 4 (75%) of AWS accounts are part of an AWS Organization. At this complexity and scale, security isn’t just about firewalls; it’s about identity, governance, and sprawl. Trust is the foundation that enables scale.
This year’s re:Invent was all about making security accessible and enabling interoperability using standards. This year, we led a session on detection engineering at scale and highlighted the challenges of manually detecting threats along with the benefits of Detection as Code (DaC). But before that, two major announcements came in the days leading up to re:Invent—or as we call it, pre:Invent:
IAM Policy Autopilot and the AWS Security Agent help teams build securely. Once you’re in production, you need visibility into how resources connect and which identities carry the most risk.
We launched two capabilities that help you understand your larger cloud footprint and prioritize risks using observability context. Security Graph visualizes critical attack paths, privilege escalation routes, and blast radii across your cloud infrastructure. A misconfigured Amazon S3 bucket becomes more than a compliance checkbox; you can see what data it exposes and who can reach it. And Cloud SIEM Risk Insights consolidates multiple data sources, such as SIEM threats and Cloud Security misconfigurations, to identify the riskiest IAM identities and prioritize fixes.
The agentic gold rush is changing both what we build and the speed at which we build it. When AI can generate code, summarize logs, and draft incident responses, the bottleneck shifts. It’s no longer the speed of writing but the speed of everything around the writing: reviewing code, deploying safely, catching vulnerabilities, and staying compliant. AI accelerates what’s possible, but your workflows decide what actually gets delivered.
A wave of re:Invent announcements centered on Kiro, AWS’s agentic IDE. Kiro focuses on moving from prototype to production, with AI agents that understand context across large codebases.
We launched three integrations to extend Kiro’s reach into production, bringing errors, deployments, traces, and incident context directly into the code editor:
The Infrastructure Innovations keynote at re:Invent emphasized how developers are moving faster than ever. As AI-assisted coding accelerates what’s possible, the ability to experiment, iterate, and fail fast is essential.
But increased development velocity without guardrails is just risk with momentum. How do you ensure code is safe, deployments are solid, and the cycle keeps improving?
At re:Invent, we released new AI capabilities for Code Security to help developers catch vulnerabilities and fix them without slowing down. AI-driven detection and remediation detects code vulnerabilities, intelligently filters out false positives, and helps developers remediate at scale, while Secret Scanning detects and blocks exposed credentials leaked in code.
With your code secured, the next question is: How fast can you get it to production? AWS announced several capabilities that remove friction across the deployment life cycle:
As these new deployment models gain traction, observability has to keep pace. We shipped support for these releases so you can maintain visibility across the full life cycle:
AWS spent the week removing friction between idea and production, with agentic IDEs that understand your codebase, container deploys that provision themselves, serverless workflows that can pause for a year and pick up where they left off, and more. That’s great for velocity, but it creates a challenge for platform teams: more paths to production means more surface area to standardize.
Our Internal Developer Portal gives platform teams a way to keep up. Developers get self-service access to provision infrastructure and spin up new services, while Scorecards make sure what they ship meets production-readiness standards before it goes out the door. The new options from AWS become paths you can actually govern instead of sprawl you have to chase.
And once everything’s flowing, DORA Metrics and CI Visibility tell you whether it’s actually working. Are deployments getting more frequent? Is the lead time for breaking changes improving? Where are pipelines getting stuck? That’s how you turn a week of announcements into measurable progress.
What really shapes the re:Invent attendee experience isn’t the scale but the mix of learning formats available throughout the week. This year, Builder Sessions let people get hands-on and build something in real time, while Chalk Talks created relaxed, whiteboard-based conversations where builders exchanged ideas and worked through real challenges together. Hands-on learning experiences like AWS GameDay provide the opportunity to solve real cloud engineering challenges in live environments, and this year, Datadog hosted a Cloud Architecture GameDay where brave players used observability to solve multiple challenges across a messy cloud environment.
Datadog also had the opportunity to play a part in the overall experience with a couple of sessions that drew strong interest from builders. Nick Hefty from Zendesk shared how his team keeps large multi-tenant systems running smoothly by constantly testing performance, watching for noisy neighbors, and staying ahead of potential bottlenecks. On the AI side, Kunal Batra led a session on building observable AI agents with AWS Strands and Bedrock AgentCore, breaking down the key challenges of running these agents at scale and showing how to operationalize the GenAI Lens of the Well-Architected Framework to address them.
Of course, no re:Invent journey is complete without swag. Between the expo and AWS shop, we left Las Vegas with heavier luggage and a refreshed wardrobe.
If there’s one takeaway from this year’s re:Invent, it’s that the era of siloed approaches is over. Agentic AI, security and governance, and developer velocity aren’t three initiatives; they’re one, and scaling requires treating them as one. The future of cloud success belongs to unified platforms that treat these domains as a single operational challenge.
This was just a quick summary of everything that excited us at re:Invent 2025. Check out all of Datadog’s launches at re:Invent and read about even more announcements on the AWS News Blog. We hope to see you next year.
此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。 原文来自 — 版权归原作者所有。