# Amazon — Serverless MCP server for AI agent data lake access on Amazon ECS Fargate

- Company: Amazon (amazon.com)
- Announced: 2026-11-06T17:13:13+00:00
- Category: not stated
- Coverage: not counted
- Announcement: no
- Group: routine
- Source: https://aws.amazon.com/blogs/machine-learning/serverless-mcp-server-for-ai-agent-data-lake-access-on-amazon-ecs-fargate/
- Record: https://forck.live/items/32724-serverless-mcp-server-for-ai-agent-data-lake-access-on-amazon-ecs-fargate
- Subject: Bedrock / Nova

Amazon's North America Sort Center team built a serverless Model Context Protocol server on Amazon ECS Fargate so planning teams can query operational data conversationally. The team says the problem was that agents were wired directly to databases and APIs, so each new dataset needed custom code and each agent reimplemented its own access control. The server acts as a centralized, agent-agnostic gateway between AI agents and the enterprise data lake, and exposing a new dataset requires only a JSON metadata file that the server discovers on the next pipeline sync. The architecture separates client, MCP server, tools and knowledge-base refresh layers, with Amazon Cognito handling authentication, Amazon DynamoDB storing session state, and Amazon Bedrock orchestrating tools built with FastMCP. Amazon Athena and Amazon Redshift run SQL against the data lake, while Amazon Bedrock Knowledge Bases handles semantic search and AWS Lambda manages ingestion into Amazon S3. A context mapping configuration scopes each query to relevant tables, which the team says kept end-to-end interaction latency in the 15–20 second range in its testing.

## Evidence

Verbatim from https://aws.amazon.com/blogs/machine-learning/serverless-mcp-server-for-ai-agent-data-lake-access-on-amazon-ecs-fargate/:

> Organizations building applications powered by artificial intelligence (AI) face a recurring challenge: giving large language model (LLM) agents access to enterprise data lakes without duplicating integration logic across every agent and application. Most teams begin by wiring agents directly to databases and APIs, with no shared gateway such as a Model Context Protocol (MCP) server in between. Each new dataset demands custom code, and each agent reimplements its own access control. As the number of datasets or agents grows, permission enforcement drifts, and onboarding a new data source becomes a multi-day engineering effort.
> 
> Our team supports Amazon’s North America Sort Center (NASC) network, where planning teams rely on operational data to manage capacity, labor, and package flow. To give those teams conversational access to that data, we built a serverless Model Context Protocol (MCP) server on Amazon Elastic Container Service (Amazon ECS) with AWS Fargate to address this problem for planning teams in NASC. The server acts as a centralized, agent-agnostic gateway between AI agents and our enterprise data lake.

---

Record: https://forck.live/items/32724-serverless-mcp-server-for-ai-agent-data-lake-access-on-amazon-ecs-fargate
Catalogue: https://forck.live/llms.txt
Current issue: https://forck.live/feed.md
