--- title: AWS Service Announcements Worth Knowing: March 2026 Edition description: March 2026 roundup: Nova Forge, Durable Functions, Graviton5, Trainium3, Route 53 Global Resolver. July 2026 retrospective on what still matters four months later. url: https://www.joinhorizon.co/blog/aws-service-announcements-march-2026/ datePublished: 2026-04-02T00:00:00.000Z dateModified: 2026-10-28T00:00:00.000Z author: palaniappan-p category: AWS News tags: aws, amazon-bedrock, nova, lambda, graviton, announcements, cloud --- # AWS Service Announcements Worth Knowing: March 2026 Edition > March 2026 roundup: Nova Forge, Durable Functions, Graviton5, Trainium3, Route 53 Global Resolver. July 2026 retrospective on what still matters four months later. > **July 2026 note:** This remains a **historical March 2026** roundup. We did not rewrite it as current news. Below each cluster, a short **Still matters?** callout marks what still drives decisions four months later. For later months see [May 2026](https://www.joinhorizon.co/blog/aws-service-announcements-may-2026/) and [June 2026](https://www.joinhorizon.co/blog/aws-service-announcements-june-2026/). AgentCore production path: [production guide](https://www.joinhorizon.co/blog/amazon-bedrock-agentcore-production/) · [pricing components](https://www.joinhorizon.co/blog/amazon-bedrock-agentcore-pricing-12-components/). March 2026 was dense: re:Invent 2025 launches finishing rollout plus AI, compute, database, and tooling updates. This is a practitioner view of what changed then and what still matters now. ## AI and machine learning ### Nova Forge SDK: fine-tune your own Nova models AWS released the **Nova Forge SDK** in March, giving enterprises a dedicated path to fine-tune and customize Amazon Nova foundation models on their own data. Forge lets you adapt Nova's reasoning and generation behavior to domain-specific vocabulary, tone, and task patterns, and deploy the result directly within Amazon Bedrock without managing separate infrastructure. This was missing from the Nova launch. Nova models are strong out of the box, but regulated industries (financial services, healthcare, legal) have always needed adaptation before production. Forge closes that gap. ### NVIDIA Nemotron 3 Super on Bedrock The **NVIDIA Nemotron 3 Super** model is now available on Amazon Bedrock (announced March 23, 2026). It joins a model roster that already includes Mistral, Google Gemini, OpenAI GPT models, MiniMax, Moonshot, and Qwen. AWS is positioning Bedrock as a model marketplace rather than a single-model platform. For teams evaluating models, this means you can benchmark across providers without changing infrastructure, IAM policies, or billing setup. ### Bedrock AgentCore and Nova Act: the stateful agent stack Two updates fit together. **Bedrock AgentCore** received stateful runtime improvements with memory streaming notifications, enabling agents to maintain long-term context across sessions rather than starting fresh each time. That matters for any agent that handles multi-session workflows: onboarding, support escalations, iterative research tasks. **Nova Act** hit general availability for browser-based agent automation. Treat reliability as a measured property of _your_ UI suite, and run soak tests before trusting autonomous browser workflows in production. Together, these two updates are AWS's answer to autonomous agents: stateful memory in Bedrock, and browser execution via Nova Act. **Still matters (July 2026)?** Yes. AgentCore is now a first-class production surface (runtime, memory, gateway, observability). Treat March’s “stateful agent stack” note as the starting point; use the [AgentCore production](https://www.joinhorizon.co/blog/amazon-bedrock-agentcore-production/) and [12-component pricing](https://www.joinhorizon.co/blog/amazon-bedrock-agentcore-pricing-12-components/) posts before budgeting browser/code tools. ### Web Grounding for Nova models AWS added **Web Grounding** as a built-in tool for Nova models on Bedrock. It is a turnkey RAG option that lets Nova models pull in up-to-date information from the web without you building and maintaining your own retrieval pipeline. The model decides when to retrieve, retrieves relevant content, and incorporates it into the response. For teams building assistants or Q&A tools over knowledge that changes frequently, this removes a good deal of infrastructure overhead. ### Elastic Beanstalk gets AI-powered troubleshooting A smaller announcement: **Elastic Beanstalk** can now feed degraded environment data (recent events, instance health, logs) directly to Amazon Bedrock and return step-by-step troubleshooting recommendations. Beanstalk is not a new service. The fact that AWS is wiring Bedrock into it suggests AI-assisted operations is being pushed into every managed service, not just purpose-built AI products. --- ## Compute and serverless ### Lambda Durable Functions: workflows up to 1 year **Lambda Durable Functions** (announced at re:Invent 2025, now rolling out) lets you build multi-step workflows that run reliably for up to one year, without paying for idle compute time between steps. The runtime handles checkpointing, retries, and state persistence. This sits between Step Functions and traditional Lambda. If your workflow has long pauses between steps (waiting for human approval, polling an external API, processing large batches), Durable Functions eliminates the orchestration overhead while keeping costs tied to actual execution. **Still matters?** Yes. Durable Functions remain the right question when you want Lambda semantics with year-scale pauses. Compare against Step Functions Express/Standard before standardizing. ### Lambda Managed Instances now supports Rust **Lambda Managed Instances**, the capability that lets you run Lambda functions on your own EC2 while retaining serverless operational simplicity, now supports Rust as a runtime. This matters for teams with performance-critical functions that need more control over the underlying compute, particularly ML inference or high-throughput data processing workloads. ### Graviton5 CPU: 192 cores, 33% lower latency The **Graviton5** chip is now in broader regional rollout. The headline numbers: 192 processor cores in a dense design that cuts inter-core communication latency by up to 33% compared to Graviton4, with higher memory bandwidth. For compute-heavy workloads (big data processing, HPC, in-memory databases), this is a large jump. Graviton5 instances are also AWS's strongest argument for moving off x86 on price-performance grounds. **Still matters?** Yes. Evaluate m9g/c9g (and peers) on a real staging soak; see [Graviton5 GA notes](https://www.joinhorizon.co/blog/ec2-m9g-m9gd-graviton5-ga-2026/). ### Trainium3 UltraServers reach GA **Trainium3 UltraServers** are now generally available for large-scale ML training. Powered by AWS's own Trainium3 chips, UltraServers are designed for the scale of foundation model training, with dense interconnects, high memory bandwidth, and deep integration with SageMaker. For teams doing pre-training or fine-tuning at scale, this gives you an alternative to GPU clusters that's tightly integrated with the AWS stack. --- ## Databases and networking ### Database Savings Plans expand to OpenSearch and Neptune Analytics **Database Savings Plans** now extend coverage to **Amazon OpenSearch Service** and **Amazon Neptune Analytics**, adding to the existing RDS and Aurora coverage. A one-year commitment gives up to 35% off eligible serverless and provisioned instance usage. If you're running OpenSearch for search or log analytics, or Neptune for graph workloads, this is straightforward cost reduction with no architectural change required. ### Route 53 Global Resolver: now generally available **Amazon Route 53 Global Resolver** hit general availability on March 16, 2026. It provides a globally distributed DNS resolution layer that reduces DNS latency for users across regions without requiring you to manage resolver infrastructure in each region manually. For multi-region applications where DNS resolution latency is a real concern (real-time applications, globally distributed APIs), this removes operational complexity. ### Amazon S3 turns 20 Not an announcement exactly, but **Amazon S3 turned 20 in March 2026**. It launched in March 2006 and effectively created the cloud storage market. It remains the foundation of most AWS architectures. --- ## Developer tools and modernization ### AWS Transform: AI-powered migration at scale **AWS Transform** is an AI-powered modernization service that learns your codebase's patterns, automates transformations across repositories, and reportedly cuts execution time by up to 80% compared to manual migration. The mainframe-specific variant transforms legacy COBOL and other mainframe applications into cloud-native architectures while automating the testing process, reducing timelines from years to months. For AWS consulting partners, this is the product most likely to change how large-scale migration engagements are scoped. The 80% time reduction claim deserves skepticism on complex codebases, but even a 40% reduction in migration execution time has significant commercial impact. --- ## Security and pricing changes ### VPC Encryption Controls: free preview is over Starting **March 1, 2026**, VPC Encryption Controls transitioned from free preview to a paid feature. This service lets you audit and enforce encryption-in-transit for all traffic flows within and across VPCs in a region. Monitor mode detects unencrypted traffic, and enforce mode blocks it. If your team enabled this during the preview period and forgot about it, check your billing. It's not an expensive feature, but it's now on your bill. --- ## What still matters (July 2026 retrospective) Four months later, three March themes still drive architecture reviews: 1. **Bedrock/AgentCore as ops infrastructure:** budget memory, gateway, and browser/code tools explicitly. It is not a demo API. 2. **Graviton5 / Trainium3:** silicon evaluation is no longer optional for price-performance reviews. 3. **Durable Functions + Managed Instances:** Lambda’s edges (long workflows, bring-your-own EC2) remain the right fork vs Step Functions / ECS. ## When this roundup is the wrong doc - **You need current-month news:** read [May](https://www.joinhorizon.co/blog/aws-service-announcements-may-2026/) / [June](https://www.joinhorizon.co/blog/aws-service-announcements-june-2026/) instead. - **You need a production AgentCore SOW:** start with the production + pricing posts linked above, not this archive. - **You only care about VPC Encryption Controls billing:** check Cost Explorer for that line item; the rest of this post is noise for you. ## What to do Monday morning 1. Skim Cost Explorer for VPC Encryption Controls (preview → paid as of 2026-03-01). 2. If you run agents: inventory AgentCore components against the 12-component pricing post. 3. Pick one Graviton5 candidate workload for a 72-hour staging soak. 4. Decide Durable Functions vs Step Functions for any approval-gated workflow still on cron+SQS. 5. Archive this post as historical context; pin May/June for ongoing news. Need a fit assessment for your estate? [Contact us](https://www.joinhorizon.co/contact-us/). --- *Source: https://www.joinhorizon.co/blog/aws-service-announcements-march-2026/*