Reference architecture on AWS
The enterprise AI architecture, built on AWS.
24 layers and 37 named AWS services, each with its release status.
GA 36 Gap 1
Plan around these
1 choice on AWS is not generally available.
Preview and Beta services are not production commitments. Confirm means vendor sources disagree or no dated source was found. Gap means there is no native service, so a partner product or your own build fills the layer. Each needs a fallback and an owner before a production release depends on it.
- Semantic layer and metrics: No native universal semantic layer Gap
Layer by layer
What each layer must do, and what AWS offers for it.
Bedrock and AgentCore for models and agents, Glue, Lake Formation and SageMaker Unified Studio for data, and IAM, Macie and Security Hub for control. Each release status was checked on 13 November 2026. 36 of 37 services are generally available. Service names link to AWS’s own documentation. The architecture stays the same on every platform; only the products change.
Brain Holds approved business meaning and knowledge.
| Layer and what it must do | AWS services and status | How RJL approaches it |
|---|---|---|
| Catalog, metadata and lineageRecord what exists, what it means, where it came from and who owns it. |
| The Federated Data Platform |
| Semantic layer and metricsApproved metrics and definitions, versioned, with an owner. |
| Ontology or Semantic Layer? |
| Ontology and knowledge graphThe entities and relationships the business agrees on. |
| Context Before Query |
| Knowledge retrieval and vector searchFind permitted evidence in documents and records, filtered by entitlement. |
| Securing AI Retrieval |
| Master data and entity resolutionMatch, survive and share one party identifier, tested for false merges. |
| Data Products in Practice |
Nervous system Carries approved work through connectors, APIs, tools and events.
| Layer and what it must do | AWS services and status | How RJL approaches it |
|---|---|---|
| SaaS and enterprise source connectorsBring data from CRM, ERP, service and HR applications. |
| The Federated Data Platform |
| Change data capture and streamingMove changes from source systems as they happen. |
| The Federated Data Platform |
| APIs, events and workflowVersioned interfaces and workflows, including write-back to systems of record. |
| Agent Patterns |
| Agent tools, gateway and MCPExpose narrow tools to agents through one governed gateway. |
| Agent Onboarding |
Body Stores, computes, delivers and operates.
| Layer and what it must do | AWS services and status | How RJL approaches it |
|---|---|---|
| Storage, open tables and historyKeep raw, time-stamped history where analytics needs it. |
| Data Products in Practice |
| Warehouse, lakehouse and operational storesQuery, join and serve data at the latency each use needs. |
| The Federated Data Platform |
| Pipelines and transformationConform, test and publish, with releases matched to consequence. |
| Data Is Not Just Code |
| Data products and sharingPublish governed products with contracts, owners and access. |
| Data Product Certification |
| Models and AI platformRun approved models with routing, quotas and versions. |
| Choosing an Agent Platform |
| Agent runtime and memoryRun agents with sessions, memory and limits. |
| Choosing an Agent Platform |
| Observability, evaluation and costTrace every request, evaluate quality and measure cost per task. |
| AI Token Economics |
Immune system Identifies, classifies, enforces policy and responds to threats.
| Layer and what it must do | AWS services and status | How RJL approaches it |
|---|---|---|
| Identity for people and agentsGive every agent its own identity, owner and permissions. |
| Agent Onboarding |
| Access policy at the dataEnforce rows, columns and attributes where the data lives. |
| Context Before Query |
| Classification, DLP and DSPMLabel sensitive data and documents, and watch where copies go. |
| Securing AI Retrieval |
| AI guardrails and action policyCheck prompts, outputs and tool calls before they take effect. |
| Agent Patterns |
| Security operations (SIEM and SOAR)Detect, investigate and respond, with agent activity in scope. |
| The Reference Implementation |
| Keys and confidential computingControl keys and protect data while it is in use. |
| Confidential Computing for AI |
Control plane One record of what was approved, released and observed.
| Layer and what it must do | AWS services and status | How RJL approaches it |
|---|---|---|
| Agent registry and release controlKnow every agent, tool and version that is approved to run. |
| Agent Onboarding |
| Audit and governance evidenceReconstruct who did what, with which version and authority. |
| AI Governance Evidence |
Getting data in
SaaS and enterprise source connectors on AWS.
| Source | AWS option and status |
|---|---|
| Salesforce | Glue zero-ETL GA |
| SAP | Glue zero-ETL (SAP OData) GA |
| ServiceNow | Glue zero-ETL GA |
| Workday | Partner or custom Gap |
| Microsoft Dynamics 365 / Dataverse | AppFlow or partner Confirm |
| Relational databases (CDC) | DMS and zero-ETL GA |
| Mainframe and Db2 | DMS (Db2 sources) and Mainframe Modernization Confirm |
| Kafka and event streams | Amazon MSK and Kinesis GA |
| Documents (SharePoint, Drive, Confluence) | Bedrock Knowledge Bases connectors GA |
Examples, not endorsements. Status reflects public vendor sources checked on 13 November 2026; confirm with the vendor before you commit. Richard has worked closely with several vendors named here as a customer and practitioner. No vendor reviewed or paid for this content. Download the full catalog (JSON).
The same architecture on Microsoft Azure · Google Cloud · Snowflake · Databricks, or a mixed estate.
Next step
Bring your AWS estate and one workflow.
In a working session we map what you run today to these layers, mark the gaps that matter for the workflow, and agree what has to be true before it reaches production.