WEBVTT

00:00.000 --> 00:03.160
Next, AWS wrote up a serverless MCP gateway pattern

00:03.160 --> 00:06.560
for data lakes instead of wiring every agent directly

00:06.560 --> 00:09.320
into every database and API.

00:09.320 --> 00:11.600
You'd also stop re-implementing access control

00:11.600 --> 00:13.480
every single time.

00:13.480 --> 00:15.920
AWS describes using Amazon ECS Fargate

00:15.920 --> 00:18.520
with one MCP server in the middle.

00:18.520 --> 00:22.160
That single server sits between your agents and the data lake.

00:22.160 --> 00:24.960
New data sets get added with a JSON metadata file,

00:24.960 --> 00:26.720
not new code.