AgentCore course → Field cards → Service map
AgentCore service map
Every capability, its maturity, and whether it runs in
ca-central-1 — one printed side. Context in
Lesson 2.
Verified 2026-08-051. This
surface changes monthly; treat anything older than six weeks as suspect.
| Group | Capability | One-line job | Status | In Canada |
|---|---|---|---|---|
| Compute | Runtime | Serverless host for an agent loop you wrote | GA Oct 2025 | Yes |
| Compute | harness | Managed agent loop declared in configuration | GA Jun 2026 | Yes |
| Tools & access | Gateway | Turns APIs, Lambda, and MCP servers into governed tools | GA Oct 2025 | Yes |
| Tools & access | Identity | Inbound and outbound auth against your existing IdP | GA Oct 2025 | Yes |
| Tools & access | Policy | Deterministic authorization on every tool call | GA ~Dec 2025 | Yes (caveat below) |
| Tools & access | Browser | Managed cloud browser for web interaction | GA Oct 2025 | Yes |
| Tools & access | Code Interpreter | Isolated sandbox for agent-written code | GA Oct 2025 | Yes |
| State | Memory | Short-term and long-term agent state | GA Oct 2025 | Yes |
| Quality loop | Observability | OpenTelemetry step-level tracing | GA Oct 2025 | Yes |
| Quality loop | Evaluations | Automated quality scoring on sessions and traces | GA Mar 2026 | Yes |
| Quality loop | Optimization | Trace-driven prompt and tool-description improvement | Preview May 2026 | Yes |
| Ecosystem | AWS Agent Registry | Org-wide catalog of agents, MCP servers, tools, skills | GA 6 Aug 2026 | No |
| Ecosystem | Payments | Agent micropayments over x402 | Preview Apr 2026 | No |
Also GA: the AgentCore CLI (Apr 2026, IaC deployment), Runtime session storage Preview (includes Canada), and Guardrails within Policy. No charge for the harness, the CLI, or skills.
The three Canada gaps, the Policy caveat, and one deadline
Not in ca-central-1: Payments (N. Virginia, Oregon,
Frankfurt, Sydney), AWS Agent Registry (N. Virginia, Oregon, Ireland, Sydney, Tokyo),
and Guardrails within Policy (N. Virginia, London, Stockholm, Sydney,
Tokyo).1
Policy itself is in ca-central-1. Two things
are not: the Guardrails screening inside it, and any guarantee about where its
inference runs — authorization prompts from Canada route to any
commercial region globally, with no opt-out and no CloudTrail record of
where.2 Detail on
the Canada card.
Agent Registry GA moved it to its own agent-registry
namespace with breaking schema changes. Anyone on the preview must migrate by
17 September 2026 or lose the data, and must adopt
AgentRegistryFullAccess.3
Migration traps in Lesson
6.
← Back to Lesson 2 · Canada & data residency → · Pricing cheat sheet →