Artificial Intelligence1 min read

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

By · Published by Everything Blog

In short

The implementation replaces custom per-agent integration code with a standardized platform that securely routes queries to core analytical repositories. Structured across four independently scalable tiers, the system ingests new datasets seamlessly via a metadata-driven JSON setup without requiring service redeployments. Queries from interfaces like Slack and IDEs are processed through an Amazon Bedrock agent executing Python-based FastMCP tools under dedicated guardrail protections.

Key points

  • Centralizing access at the server level replaces fragmented connection patterns and elimi…: Centralizing access at the server level replaces fragmented connection patterns and eliminates the need to manage permissions independently for every agent.
  • Client session states are managed in Amazon DynamoDB while inbound network requests are p…: Client session states are managed in Amazon DynamoDB while inbound network requests are protected by AWS WAF and Amazon Cognito.
  • The serverless container design ensures bursty planning workloads are scaled reliably acr…: The serverless container design ensures bursty planning workloads are scaled reliably across Amazon Elastic Container Service with AWS Fargate.

Sources checked by our analysis pipeline: 1

Artificial Intelligence

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…

Artificial Intelligence