# Build a data foundation for agentic AI on AWS: From lakehouse to MCP

DevFeed: [Build a data foundation for agentic AI on AWS: From lakehouse to MCP](<https://devfeed.tech/articles/build-a-data-foundation-for-agentic-ai-on-aws-from-lakehouse-to-mcp-129558.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/big-data/build-a-data-foundation-for-agentic-ai-on-aws-from-lakehouse-to-mcp/>)

Author: Adrien Lebret

Published: 2026-11-11T21:03:43Z

Content type: article

Language: en

Sources: [AWS Big Data Blog](<https://devfeed.tech/sources/aws-big-data-blog.md>)

Topics: [AI-Ready Data](<https://devfeed.tech/topics/ai-ready-data.md>), [Multi Agent Systems](<https://devfeed.tech/topics/multi-agent-systems.md>), [data-engineering](<https://devfeed.tech/topics/data-engineering.md>), [Amazon Bedrock Knowledge Bases](<https://devfeed.tech/topics/amazon-bedrock-knowledge-bases.md>), [AWS Glue](<https://devfeed.tech/topics/aws-glue.md>), [Amazon Bedrock](<https://devfeed.tech/topics/amazon-bedrock.md>), [AWS IAM](<https://devfeed.tech/topics/aws-iam.md>), [databricks](<https://devfeed.tech/topics/databricks.md>), [Amazon OpenSearch Service](<https://devfeed.tech/topics/amazon-opensearch-service.md>), [Data pipelines](<https://devfeed.tech/topics/data-pipelines.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agentic](<https://devfeed.tech/tags/agentic.md>), [agentic-ai](<https://devfeed.tech/tags/agentic-ai.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-data](<https://devfeed.tech/tags/ai-data.md>), [aws](<https://devfeed.tech/tags/aws.md>), [build](<https://devfeed.tech/tags/build.md>), [building](<https://devfeed.tech/tags/building.md>), [context](<https://devfeed.tech/tags/context.md>), [context-engineering](<https://devfeed.tech/tags/context-engineering.md>), [data](<https://devfeed.tech/tags/data.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [foundation](<https://devfeed.tech/tags/foundation.md>), [governance](<https://devfeed.tech/tags/governance.md>), [interoperability](<https://devfeed.tech/tags/interoperability.md>), [lakehouse](<https://devfeed.tech/tags/lakehouse.md>), [like](<https://devfeed.tech/tags/like.md>), [mcp](<https://devfeed.tech/tags/mcp.md>), [model](<https://devfeed.tech/tags/model.md>), [model-context-protocol](<https://devfeed.tech/tags/model-context-protocol.md>), [uncategorized](<https://devfeed.tech/tags/uncategorized.md>)

## AI overview

The article presents a four-pillar AWS data foundation for agentic AI: a unified lakehouse, context engineering, interoperability, and governance. Amazon SageMaker Lakehouse and S3 Tables bring operational, analytical, and AI data into a governed foundation with Apache Iceberg, zero-ETL ingestion, and federated queries. Context engineering combines knowledge bases, short- and long-term memory, and tools that fetch selected data, addressing stateless models' limited context windows. For collaboration, A2A supports agent-to-agent communication over HTTP and JSON, while MCP standardizes agent access to resources, tools, and prompts; Amazon Bedrock AgentCore Gateway centralizes connections, authentication, audit logging, and permission-scoped semantic tool discovery. Amazon SageMaker Data Catalog adds dataset discovery, lineage, quality indicators, and publish-and-subscribe access controls. The article recommends establishing the lakehouse and ingestion first, developing context capabilities before scaling orchestration, and treating governance as an ongoing effort from the start.

## Source excerpt

Building a data foundation ready for agentic AI relies on a unified lakehouse and interoperability protocols like Model Context Protocol (MCP). This post walks through four pillars for building an agentic AI data foundation on AWS: a unified lakehouse, context engineering, multi-agent interoperability, and data governance.