From the source
Amazon's guide shows how to build a semantic layer for agentic AI using EDB Postgres AI, running a Strands Agents agent on Amazon Bedrock AgentCore that queries the layer to answer customer 360 questions.
- EDB Postgres AI places the semantic layer inside the operational Postgres database as an AIDB extension, so business meaning lives next to the data in standard Postgres COMMENT statements.
- The join graph comes from Postgres foreign keys, and governance uses Postgres GRANT and row-level security through the Model Context Protocol endpoint that ships with AIDB.
- The model layer is
Anthropic Claude on Amazon Bedrock, the runtime layer is AgentCore runtime, and AgentCore Gateway handles inbound authorization while AgentCore Identity holds outbound credentials for tool targets.
- The guide walks through building an AIDB semantic knowledge base over a Postgres schema, exposing the AIDB tool catalog to an external agent through the built-in EDB MCP endpoint fronted by an Application Load Balancer and registered as an MCP target on AgentCore Gateway.
- It also shows how Postgres roles, column-level GRANT statements and row-level security produce different results for different callers while the prompt, tool catalog and agent code stay the same, and how AIDB captures OpenTelemetry traces for every SQL execution as rows in the aidb_otel schema, queryable with ordinary SQL.
- The example dataset is the Stardog C360 Knowledge Kit loaded into a single EDB Postgres AI instance in a dedicated c360 schema, with four tables and one derived view.