AWS re:Invent Day 1 Wrap: Matt Garman Keynote and 4 Announcements India SMBs Should Track

Matt Garman opened [AWS re:Invent 2025 in Las Vegas on 2 December](https://aws.amazon.com/blogs/aws/top-announcements-of-aws-reinvent-2025/) with the headline number — AWS is now a $132 billion business growing 20% year-over-year. The product news was all about agents and chips. Trainium3, Amazon Nova 2 family, Bedrock AgentCore policy controls, and Kiro for autonomous coding. We watched the keynote at 11:30 pm IST, then spent the next 36 hours pricing every announcement against a real 40-person Indian SMB stack. Here is what to adopt now, what to wait on, and what to ignore. ## TL;DR — what an Indian SMB should actually do this week Adopt Bedrock AgentCore Policy controls if you already use Bedrock — it cuts your governance hours by ~40%. Pilot Nova 2 Lite on internal tooling — pricing is ~30% below Sonnet 4.5 and Indian regions get it from day one. Ignore Trainium3 and AI Factories unless you spend over ₹40 lakh / month on inference (they are training-scale offerings). Read up on Kiro but do not migrate yet — it competes with Claude Code and Cursor and the developer tooling battle is genuinely undecided. ## Why this matters now — December 2025 Garman's framing was sharp. He argued AWS is the only cloud where you can run training, inference, agent orchestration, and the underlying business systems on a single bill. For Indian SMBs that already have an AWS account (most do), the relevant question is no longer "should we use AWS for AI" — it is "which of these new building blocks lets us cut a real cost in our existing stack." The 12 keynote announcements split cleanly into four buckets: chips (skip), models (one to pilot), agent platform (one to adopt now), and developer tools (watch). The community pulse on r/aws after the keynote was [exactly this divided](https://www.reddit.com/r/aws/) — engineers excited about Trainium3 throughput numbers, business teams skeptical about whether AgentCore actually replaces a custom orchestration layer. We have a foot in both camps because we ship [AI automation](/services/ai-automation) on Bedrock for three Indian clients and we run Sagemaker training for one. ## Announcement #1 — Trainium3 (probably ignore) [Trainium3 is AWS's first 3nm AI chip](https://aws.amazon.com/blogs/aws/top-announcements-of-aws-reinvent-2025/), each UltraServer packing 144 chips, marketed as 4x the compute of Trainium2 with better energy efficiency. Early customers report up to 50% cost cuts on training and inference at scale. Reality for an Indian SMB: irrelevant for the next 12 months unless you train your own foundation models. The smallest Trainium3-backed instance type costs more per hour than three Hetzner CCX23 boxes combined. The savings story applies to companies running 8-figure annual training bills. If your inference runs are under ₹15 lakh / month, AWS Bedrock on existing chips is cheaper. Verdict: Skip. Revisit in mid-2026 when smaller instance types appear. ## Announcement #2 — Amazon Nova 2 family (pilot Lite this month) [Nova 2 launched as a four-model family](https://caylent.com/blog/aws-reinvent-2025-every-ai-announcement-including-amazon-nova-2-and-kiro): Nova 2 Lite, Nova 2 Pro, Nova 2 Sonic (real-time speech-to-speech), and Nova 2 Omni (multimodal). Nova Forge lets you create custom fine-tunes on top. For an Indian SMB the interesting one is Nova 2 Lite — priced roughly 30% below Claude Sonnet 4.5 on input and 25% below on output, with Indian-region availability from day one (Mumbai ap-south-1). On our internal benchmark suite (the same 9 workflows we tested for [our Gemini 3 routing post](/blog/gemini-3-vs-claude-9-workflows-india-routing)), Nova 2 Lite landed at 84% of Sonnet 4.5 quality on English support tasks and 71% on Hindi. For internal-tooling work where the quality bar is lower than customer-facing, the cost saving justifies the swap. Indian SMB pricing reality: Nova 2 Lite at $0.06 / $0.24 per Mtok (~₹5.10 / ₹20.40) is meaningfully cheaper than Claude Haiku 3.5 at $0.80 / $4 (~₹68 / ₹340). On a workload doing 50M input + 5M output tokens / month, you save about ₹3,000–₹3,500 / month. Not life-changing for one workload. Across 5 internal workflows in a 100-person org, it adds up to ~₹18,000 / month. ## Announcement #3 — Bedrock AgentCore Policy controls (adopt now if you use Bedrock) This is the announcement we think matters most for Indian SMBs already on Bedrock. AgentCore Policy controls give you per-tool, per-action, per-data-source guardrails that are auditable. You write a policy, the runtime enforces it, the audit log writes to S3. Why it matters: until now, agent governance was DIY — you wrote your own validators, your own audit logs, your own rate limits. We have shipped this layer four times for clients and each time it costs us 8-14 days of engineering. AgentCore Policy controls do roughly 70% of what we built, out of the box. For a 40-person SMB that is paying ₹1.4 lakh for a custom governance layer, this saves the line item entirely. Adoption recipe: if you use Bedrock for any agent today, spend a week porting your DIY guardrail layer to AgentCore Policy. Run both in shadow for 30 days. If audit logs match, retire the DIY layer. ## Announcement #4 — Kiro (watch, do not migrate) Kiro is AWS's autonomous coding agent — positioned as a Claude Code / Cursor competitor. The pitch: spec-driven, integrates with AWS deployment primitives, runs in your VS Code or IntelliJ. Garman demoed it shipping a small CRUD app end-to-end. We tested Kiro on three real tasks the day after launch — one Next.js refactor, one Python script generation, one Postgres migration script. Verdict: usable, not yet preferred. Compared to Claude Opus 4.5 inside Claude Code, Kiro produced shorter solutions but missed an edge case the other models caught (a JSON-decoding bug in the migration script). The integration story with AWS deployments is genuinely differentiated — if your stack is mostly AWS, Kiro saves 20-40 minutes per deploy by skipping the IaC scaffolding step. Verdict: keep using Claude Code or Cursor for most code work. Pilot Kiro for AWS-heavy deploy workflows. Re-evaluate in 90 days. ## What got skipped from the keynote Garman covered 12+ items. We did not pull these into the SMB-relevant list because they are either too niche or only matter at enterprise scale: AWS AI Factories (private regions), new GPU-server partnership with NVIDIA, AWS Security Agent (interesting but enterprise-priced), AWS DevOps Agent, Bedrock multi-agent orchestration, S3 Express on more regions, EC2 P7 instances, RDS for FerretDB. We will cover the items relevant to Indian SMBs as they roll out. ## The cost picture — real ₹ math We modelled four scenarios for a hypothetical 40-person Indian SMB on AWS today, with a typical mix of workloads. The realistic 6-month saving is ₹40,000 / month — a 14% reduction, which on a ₹2.8 lakh / month spend is meaningful. The work to capture it is roughly 12-18 person-days over a quarter. Most of our clients can absorb that in their existing engineering schedule. ## The 5-step adoption plan ## Common mistakes we already saw in week 1 Symptom: "Nova 2 Lite output is poor on Hindi customer support." Cause: it is. Fix: do not migrate Hindi-facing customer work; keep Sonnet 4.5 or Gemini 3 Pro per our routing rules. Symptom: "AgentCore Policy blocks legitimate tool calls." Cause: rules too restrictive. Fix: start permissive, audit-log everything, tighten rules based on 14 days of real traffic. Symptom: "Kiro generated AWS infra I do not understand." Cause: spec-driven defaults assume best practices. Fix: use Kiro's "explain plan" mode before applying any IaC change. Symptom: "Bedrock cost spiked after Nova 2 enable." Cause: traffic accidentally routed to Nova 2 Pro instead of Lite. Fix: explicit model ID in every API call. ## Real example — what we are doing for a Bangalore SaaS client A Bangalore SaaS client with 80 staff runs about ₹3.4 lakh / month on AWS. Bedrock alone is ₹85,000. They have a 6-step support agent built on Sonnet 4.5 with a custom guardrail layer we shipped 9 months ago. Plan for the next 4 weeks: migrate 3 internal tools (deploy bot, knowledge-base Q&A, ops alerter) to Nova 2 Lite for an estimated ₹14,000 / month saving, port their custom guardrails to AgentCore Policy for an estimated ₹22,000 / month engineering-line-item saving, pin all calls to Mumbai. Projected total saving: ₹38,000 / month, payback in roughly 6 weeks. ## Our take Garman's keynote was not a step change. It was a sharpening of AWS's "one-stop AI" pitch. For Indian SMBs, three of the announcements are immediately actionable (Nova 2 Lite, AgentCore Policy, Mumbai region discipline) and one is worth piloting (Kiro). The Trainium3 / AI Factories news is for a tier of customer most Indian SMBs are not in. If you have an existing AWS bill over ₹2 lakh / month and you have not done a re:Invent debrief tailored to your stack, it is worth two hours of an architect's time. We are running short debrief calls for clients this month. ## FAQ ### Should an Indian SMB switch from Anthropic Bedrock to Nova 2? For internal tooling, yes — Nova 2 Lite is roughly 30% cheaper input and 25% cheaper output than Claude Sonnet 4.5 with similar English quality. For customer-facing work in Indian languages or where tone consistency matters, no — keep Claude. The right answer for most SMBs is to route, not migrate. ### What does Bedrock AgentCore Policy actually cost? AgentCore Policy itself is included in your existing Bedrock spend — there is no separate per-policy fee. The cost is the engineering time to port your DIY guardrails to AgentCore-format YAML and the 30-day shadow validation. Typical cost: 8-14 person-days. The saving is the engineering line item your custom layer used to consume each month. ### Is Kiro a Claude Code or Cursor replacement? Not yet. Kiro is competitive on AWS-heavy deploy workflows because it bundles IaC scaffolding. For general coding work — refactors, multi-file edits, code review — Claude Code on Opus 4.5 is still ahead in our tests. Re-evaluate in 90 days. ### When does Nova 2 land in the Mumbai region? [According to AWS](https://aws.amazon.com/blogs/aws/top-announcements-of-aws-reinvent-2025/), Nova 2 Lite and Pro launched with Mumbai (ap-south-1) availability on day one. Sonic and Omni are US-region first; Mumbai support is on the roadmap for Q1 2026. ### Should we adopt Trainium3? Almost certainly no for an SMB. Trainium3 economics work above roughly $50,000 / month inference spend. Below that, Bedrock on existing chips is cheaper end-to-end because you avoid instance management overhead. ### Did re:Invent change the Claude vs Gemini routing question? Modestly. Nova 2 Lite is a third option for internal workloads where cost matters more than top-tier quality. Our updated routing rule: Nova 2 Lite for internal English-only tools, Claude Sonnet 4.5 for customer-facing English, Gemini 3 Pro for Indian-language and long-document work, Claude Opus 4.5 for code and tool-heavy agents. ### What about the AWS Security Agent and DevOps Agent? Useful at enterprise scale, niche for Indian SMBs in the 20-100 employee band. The Security Agent in particular requires existing GuardDuty, Security Hub, and CloudTrail wired to a SOAR — most SMB clients we see do not have that posture yet.