# Amazon — Pluggable Agentic AI Framework: A seven-layer composable enterprise agentic AI reference architecture on Amazon Bedrock AgentCore

- Company: Amazon (amazon.com)
- Announced: 2026-11-09T19:05:54+00:00
- Category: not stated
- Coverage: not counted
- Announcement: no
- Group: routine
- Source: https://aws.amazon.com/blogs/machine-learning/pluggable-agentic-ai-framework-a-seven-layer-composable-enterprise-agentic-ai-reference-architecture-on-amazon-bedrock-agentcore/
- Record: https://forck.live/items/33589-pluggable-agentic-ai-framework-a-seven-layer-composable-enterprise-agentic-ai
- Subject: Bedrock / Nova

Amazon's AWS published a seven-layer composable reference architecture, the Pluggable Agentic AI Framework, for taking multi-agent AI applications from prototype to production scale. The framework addresses a gap the post says stalls most agentic AI initiatives: prototypes show a model can do a task but are not built to survive production traffic, cost pressure and security review. Each of the seven layers has a distinct responsibility and a stable contract, and the services shown reflect the reference implementation rather than mandatory choices, so organizations can substitute alternatives that fit their existing infrastructure. The Data and Knowledge layer owns retrieval, embeddings and access to structured and unstructured data, with Amazon Bedrock Knowledge Base, Vector Engine for Amazon OpenSearch Serverless, Amazon S3 Vectors and Amazon DynamoDB as example building blocks. Model and Inference choices should be driven by configuration rather than hardwired into application logic, with a routing layer and a proxy such as LiteLLM providing a common interface across providers. Orchestration should use a single agent for straightforward tasks and a supervisor delegating specialist agents for complex cross-domain workflows, with specialists discovered from a centralized agent registry through protocols like MCP and A2A. Security and Guardrails should be built in from day one, treating all external content as untrusted, authenticating every request through a service like Amazon Bedrock AgentCore Identity, and granting agents temporary scoped credentials instead of persistent secrets.

## Evidence

Verbatim from https://aws.amazon.com/blogs/machine-learning/pluggable-agentic-ai-framework-a-seven-layer-composable-enterprise-agentic-ai-reference-architecture-on-amazon-bedrock-agentcore/:

> “How do we run our AI agents in production at scale?” is the question every customer eventually asks. It comes bundled with several questions. How do we handle thousands of concurrent user requests securely and confidently? How do we make sure the agents stay reliable under real traffic instead of failing silently? How do we know if an agent still meets the quality and safety standards it passed during testing? What are agent security best practices? Should that be deterministic or non-deterministic? And many more. A proof-of-concept answers none of these, because it is built to show the agent model can do the task, not to survive production traffic, cost pressure, and security review.
> 
> That gap between a working prototype and a system that runs reliably, securely, frugally and responsibly at scale, is where most agentic AI initiatives stall, and it is rarely the model’s fault. Every team building an agent tends to rebuild the same scaffolding from scratch: its own routing logic, its own guardrails, its own observability, all applied after the fact rather than built in from the start. The teams need a shared, production-ready architecture that every agent can build on.

---

Record: https://forck.live/items/33589-pluggable-agentic-ai-framework-a-seven-layer-composable-enterprise-agentic-ai
Catalogue: https://forck.live/llms.txt
Current issue: https://forck.live/feed.md
