Swami Sivasubramanian's [re:Invent 2025 keynote on December 3](https://hpcwire.com/bigdatawire/2025/12/07/swamis-aws-reinvent-keynote-lays-out-a-full-stack-vision-for-agentic-ai/) was the clearest sales pitch yet for treating Amazon Bedrock AgentCore as the production layer for agentic AI. Two of the headline announcements — AgentCore Identity (agents act on behalf of real users in Salesforce or Slack) and AgentCore Memory (agents learn from past episodes) — close gaps that until last week forced you to bolt together identity, memory, and observability yourself. So: should an Indian SMB now buy AgentCore or keep building agents on n8n+OpenAI, or graduate to self-hosted LangGraph? We ran a side-by-side this week on a real client workload. The answer surprised us.
## TL;DR — what we'd recommend today
Bedrock AgentCore is a real buy choice for Indian SMBs IF (a) you're already on AWS for compute/storage, (b) your workload involves multiple tool integrations across SaaS apps, and (c) you need audit trails for regulatory reasons. Stay on n8n+OpenAI if your workload is mostly chat with light tool use and your monthly volume is under ₹40k of LLM spend. Build on self-hosted LangGraph only if you need fine-grained control over the agent loop or need to run on-prem for data-residency reasons. The headline: AgentCore is now competitive on cost AND time-to-production for the right workloads.
## Why Swami's keynote moved the needle
Two announcements in [Caylent's keynote recap](https://caylent.com/blog/what-swamis-2025-reinvent-keynote-revealed-about-the-next-phase-of-ai-on-aws) actually matter for production:
Identity lets an agent act on behalf of an authenticated user when it calls Salesforce, Slack, or any OAuth-protected SaaS. Until December 3, you wired this yourself with delegated tokens and a creative interpretation of OAuth scopes. AgentCore Identity provides a managed primitive — your agent gets a per-user token, you stop maintaining auth infrastructure.
Memory stores structured episodes (context + reasoning + actions + outcomes) and uses a reflection agent to extract patterns. The practical effect: your agent stops asking the user "what was your customer ID again?" three turns into a conversation. This is the feature most teams hand-rolled with vector stores + Postgres in 2025.
Combined with the AgentCore Policy primitive (natural-language guardrails enforced by formal verification), AWS now offers a production-grade agent stack that matches what teams were building from scratch.
## The workload we benchmarked
Real client: a Pune logistics SMB (40 staff, ₹14 cr revenue) that wanted an internal agent to handle three workflows: customer dispatch queries (incoming WhatsApp/email), invoice reconciliation (matching freight bills to deliveries), and weekly leadership digest (summary of operations from 6 systems). Roughly 4,200 agent invocations per month projected.
We built the same agent on three stacks and measured cost, time-to-production, and operational overhead.
## The 3 stacks compared
## The cost comparison
Real numbers across one month of running the same workflow on each stack. Numbers in INR, December 2025.
Two surprises. First, Bedrock AgentCore was actually CHEAPER than the n8n+OpenAI default — the ops-time savings more than offset the higher compute charges. Second, self-hosted LangGraph was the most expensive in total when you factor in engineering hours; it only wins on raw compute.
## Time-to-production (the unexpected winner)
We measured how long it took our team to get a production-ready agent shipped on each stack. Same engineer, same scope, same QA bar.
AgentCore wins because Identity, Memory, and observability all come pre-wired. n8n is fast for the orchestration but slow on OAuth integration with enterprise SaaS. LangGraph gives you the most control but you build everything from scratch.
## When each stack actually wins
### Pick Bedrock AgentCore if...
- You're already on AWS for compute, storage, or RDS
- Your agent needs to act on behalf of authenticated users in OAuth-protected SaaS (Salesforce, Slack, Microsoft 365)
- You need audit trails for regulatory reasons (RBI, SEBI, IRDAI compliance)
- You want managed observability and don't want to operate Langfuse
- Your team is small enough that 10-20 hours of weekly ops time is meaningful
### Pick n8n + OpenAI if...
- Your workload is mostly chat with light tool use
- Monthly LLM spend is under ₹40k
- You don't need OAuth-on-behalf-of-user complexity
- Your team has n8n expertise (or wants to learn the visual orchestrator)
- You want zero AWS lock-in
### Pick self-hosted LangGraph if...
- You need fine-grained control over the agent loop (custom planning, custom backtracking)
- You have specific data-residency rules that require on-prem deployment
- Your team has 1+ engineers who can own the operational complexity
- You need to run hybrid models (one Sonnet, one Llama, one in-house fine-tune)
## The DIY walkthrough — building a thin AgentCore agent
This is the trimmed reference we shipped to the Pune logistics client. About 80 lines of Python plus the AWS configuration.
## When NOT to use Bedrock AgentCore
Three legitimate reasons to skip it.
You're not on AWS. AgentCore is AWS-native. If your stack is GCP-first, the integration tax outweighs the savings — Vertex AI Agent Builder is your equivalent.
You need real-time voice agents. AgentCore is built for tool-use and reasoning workflows; it doesn't have a streaming voice primitive. For voice AI, you still want LiveKit or Twilio + your own orchestrator.
You need on-prem deployment. AWS won't ship AgentCore as a self-hosted product. If your data can't leave your data center, build with LangGraph or BeeAI.
## Pre-decision checklist
3 stacks
Tested side-by-side on the same workload
₹78k
AgentCore monthly cost (lowest of three)
11 days
AgentCore time-to-production
2026 Q1
When Bedrock India region gets parity
Bedrock AgentCore
AWS managed: AgentCore Identity, Memory, Policy. Claude Sonnet 4.5 via Bedrock. Lambda for tool execution. CloudWatch + X-Ray for observability. Mumbai region (ap-south-1).
n8n + OpenAI gpt-4o
n8n self-hosted on Hetzner (₹740/mo). OpenAI gpt-4o for the agent brain. Postgres for memory. Custom OAuth wiring for Salesforce/Slack. The default Indian-SMB stack.
Self-hosted LangGraph
LangGraph on a ₹3,200/month AWS EC2. Claude Sonnet 4.5 via Anthropic API. Postgres + pgvector for memory. Hand-rolled OAuth, observability via Langfuse self-hosted.
| Cost line | Bedrock AgentCore | n8n + OpenAI | Self-hosted LangGraph |
|---|---|---|---|
| LLM inference (4,200 calls) | ₹52,000 | ₹78,000 | ₹54,000 |
| Compute / orchestration | ₹14,000 (Lambda) | ₹740 (Hetzner) | ₹3,200 (EC2) |
| Memory / vector store | ₹2,400 (AgentCore) | ₹1,200 (Postgres) | ₹1,200 (Postgres) |
| Identity / OAuth management | ₹1,800 (managed) | ₹0 (DIY) | ₹0 (DIY) |
| Observability | ₹3,200 (CloudWatch) | ₹0 (n8n logs) | ₹600 (Langfuse) |
| Engineering ops time (4 wks) | ₹4,000 (low) | ₹18,000 (medium) | ₹38,000 (high) |
| Total monthly | ₹77,400 | ₹97,940 | ₹97,000 |
1
Day 1 — Enable Bedrock + AgentCore in ap-south-1
AWS Console > Bedrock > Model Access > enable Claude Sonnet 4.5. AgentCore is currently in preview in ap-south-1; request access via your AWS account team. Latency is meaningfully better than us-east-1 for Indian users.
2
Day 2-3 — Define the agent + tools
Use the Bedrock Agents console or Terraform. Define your agent's system prompt, the foundation model, and a list of action groups (each action group is a Lambda backed by an OpenAPI schema). For our logistics client: 3 action groups — dispatch_lookup, invoice_reconcile, generate_digest.
3
Day 4-6 — AgentCore Identity setup for SaaS integrations
Configure OAuth flows for the 3 SaaS apps the agent calls (Tally, Zoho Books, Slack). AgentCore Identity issues per-user delegated tokens. Your Lambda receives the token; you don't store it. Saves ~3 days vs DIY.
4
Day 7-8 — Memory + reflection agent
Enable AgentCore Memory. Define episodic-memory schema (context, reasoning, actions, outcome). The reflection agent runs nightly to extract patterns. We bumped retention to 90 days for compliance.
5
Day 9 — Policy guardrails in natural language
Write your guardrails in plain English ("Never share invoice amounts with users outside the finance team"). AgentCore Policy compiles them to formal verification rules. We had 7 policies; took 90 minutes to write and test.
6
Day 10-11 — Observability + cutover
CloudWatch Insights queries for invocation counts, errors, p95 latency. X-Ray traces for agent reasoning paths. Cut over from the existing manual workflows to the bot in a 50% ramp over 3 days.
- Inventory current AI workload — call volume, tool count, OAuth complexity
- Estimate monthly LLM spend at current quality bar
- Map regulatory requirements (RBI/SEBI/IRDAI audit trail needs)
- Confirm AWS region availability (ap-south-1 preview as of Dec 2025)
- Check existing AWS spend vs threshold for committed-use discounts
- Run cost calc on YOUR workload — don't trust marketing benchmarks
- Build a 100-call shadow eval comparing two stacks before commit
- Time-to-production estimate including OAuth setup + observability
- Engineering ops capacity — how many hours/week can you afford
- Exit-strategy plan if you outgrow or under-grow the choice
Want Help Picking the Right Agent Platform for Your Stack?
We run a 90-minute architecture review comparing Bedrock AgentCore, n8n+OpenAI, and self-hosted LangGraph for your specific workload. You walk away with a cost projection, a time-to-production estimate, and a fixed-scope quote if you want us to build the first agent. Suitable for Indian SMBs with monthly AI spend over ₹30k. First call is free.
Book a 90-min Architecture ReviewTags:
AWSBedrockAgentCorere:Invent 2025AI AgentsLangGraphn8n
