The example builds a customer-360 domain across Amazon Redshift and Amazon Aurora, with the agent reaching Mosaic through its MCP server. The post says joins, metric definitions, and caller-specific row and column filters remain inside Mosaic rather than in the agent prompt. It describes user-identity propagation to preserve those controls end to end. The same Mosaic definitions are also exposed through JDBC/ODBC, XMLA, and REST. This is a vendor-described architecture example; the post does not establish independent performance or security validation.
Build a semantic layer for agentic AI on AWS with Strategy Mosaic and Amazon Bedrock AgentCore
In one minute
AWS and Strategy published a walkthrough that connects a Strategy Mosaic semantic layer to a Strands agent hosted on Amazon Bedrock AgentCore.
What changed: Introduces Strategy Mosaic’s semantic layer as a distinct AWS agentic-AI use case, integrating with Bedrock AgentCore and data services.