Create

Sign in to ReadmeX

or

How we handle your data: Privacy Policy

ReadmeX

Your AI reading companion

What would you like to catch up on?

Pick a briefing, or ask your own question.

Your community and people briefings stay personal to you.

Story

Build an agentic AI semantic layer with EDB Postgres AI

AI summary

AWS Machine Learning Blog provides a tutorial for creating a semantic layer with EDB Postgres AI and exposing it to an external agent through the built-in MCP endpoint and Amazon Bedrock AgentCore Gateway. The example runs a Strands Agents agent on Amazon Bedrock AgentCore to answer customer 360 questions, while PostgreSQL grants and row-level security determine each caller's permitted rows and columns. The guide also describes storing OpenTelemetry traces for SQL executions in the aidb_otel schema.

In-depth insight

The tutorial shows how one agent setup can combine database-native business semantics, access controls, identity propagation, and audit records while querying live operational data.

In this post, we show how to build a semantic layer for agentic AI using EDB Postgres AI. We run a Strands Agents agent on Amazon Bedrock AgentCore that queries the layer to answer customer 360 (C360) questions. Earlier posts in this series built the same C360 pattern with Stardog’s knowledge graph, Denodo’s data virtualization platform, AtScale’s dimensional model, and Strategy Mosaic’s linked models.

EDB Postgres AI puts the semantic layer inside the operational Postgres database as an AIDB extension. 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 (MCP) endpoint that ships with AIDB.

By the end of this post you will know:

  • How to build an AIDB semantic knowledge base (SemKB) over a Postgres schema, how COMMENT ON statements and aidb.create_semantic_alias behave as the authoring surface, and how foreign keys crawl into join paths.
  • How to expose the AIDB tool catalog to an external agent through the built-in EDB MCP endpoint, fronted by an Application Load Balancer (ALB) and registered as an MCP target on AgentCore Gateway, a capability of Amazon Bedrock AgentCore.
  • How Postgres roles, column-level GRANT statements, and row-level security produce different results for different callers. The prompt, tool catalog, and agent code stay the same.
  • How AIDB captures OpenTelemetry traces for every SQL execution as rows in the aidb_otel schema, queryable with ordinary SQL.

#EDB Postgres AI#Amazon Bedrock AgentCore#Strands Agents#Claude#EDB MCP endpoint#AgentCore Gateway#AgentCore Identity#Amazon Cognito#Application Load Balancer#PostgreSQL

Original · 18 min readRead the original
Group chat

No comments yet. Start the conversation.