Ep 3 Blog 1:03 w/ Justy & Cody

No OAuth Required: An MCP Client For AWS IAM

Dennis Traub for AWS Posted on Nov 18 • Edited on Nov 20 No OAuth Required: An MCP Client For AWS IAM # ai # agents # mcp # aws When Anthropic published the Model Context Protocol (MCP) , I immediately started experimenting with deployment options on AWS: First, I tried running MCP servers as AWS Lambda functions. A great solution in terms of simplicity and cost, but it also meant I had to manually manage session state across invocations.

Embed this episode

Paste this on any site — the player is a self-contained iframe with no cookies or trackers.

<iframe src="https://sandrise.io/exploring-next/embed/3"
  width="100%" height="180" style="max-width:640px;border:0;border-radius:12px;overflow:hidden"
  title="Exploring Next — Episode 3 audio player"
  loading="lazy" allow="autoplay" referrerpolicy="strict-origin-when-cross-origin"></iframe>
Embed & API docs →
Voice OpenAI TTS

Transcript

Host A Welcome back to Exploring Next! Today we're looking at No OAuth Required: An MCP Client For AWS IAM.

Host B Yeah, this one caught our eye because Dennis Traub for AWS Posted on Nov 18 &bull; Edited on Nov 20 No OAuth Required: An MCP Client For AWS IAM # ai # agents # mcp # aws When Anthropic published the Model Context Protocol (MCP) , I immediately started experimenting with deployment options on AWS: First, I tried running MCP servers as AWS Lambda functions.

Host A So the big idea is A great solution in terms of simplicity and cost, but it also meant I had to manually manage session state across invocations.

Host B What stood out to me is Next, I deployed them as containers on Amazon ECS, which immediately solved session state management for me, but I had to pay for a running server, even when it sat idle.

Host A If you're curious, give the original a read: https://dev.to/aws/no-oauth-required-an-mcp-client-for-aws-iam-k1o.

Host B And let us know what you try next!