too risky to use, no?

I've tried it here and there and like it so far , seems like they're moving from 20+ mcps to centralized but not all have made it over yet this is def nice becauase they release the iam for it so you can set perms depending on if they did it via mcp or not https://aws.amazon.com/blogs/security/understanding-iam-for-managed-aws-mcp-servers/

oh iam is cool. so you can limit risky stuff

it does need sigv4 via aws proxy so pairs nice with atmos auth and atmos mcp stuff. i got it working with this in atmos.yaml

mcp:
  enabled: true
  servers:
    atmos:
      description: "Atmos MCP server — exposes Atmos AI tools to Claude Code"
      command: atmos
      args:
        - "mcp"
        - "start"
    aws-mcp:
      description: "AWS Agent Toolkit MCP server (<https://docs.aws.amazon.com/agent-toolkit/>)"
      identity: "core-corp/terraform"
      env:
        ATMOS_PROFILE: devops
      command: uvx
      args:
        - "mcp-proxy-for-aws@latest"
        - "<https://aws-mcp.us-east-1.api.aws/mcp>"
        - "--metadata"
        - "AWS_REGION=us-east-2"

then I did atmos mcp export to generate the

.mcp.json

for claude , which gives me

"aws-mcp": {
      "command": "atmos",
      "args": [
        "auth",
        "exec",
        "-i",
        "core-corp/terraform",
        "--",
        "uvx",
        "mcp-proxy-for-aws@latest",
        "<https://aws-mcp.us-east-1.api.aws/mcp>",
        "--metadata",
        "AWS_REGION=us-east-2"
      ],
      "env": {
        "ATMOS_PROFILE": "devops",
      }
    }

also have

toolchain:
  aliases:
    uv: astral-sh/uv

Wow, seriously?! 1. ✅ AWS releases a hosted MCP 🎉 2. ❌ But requests must be signed with AWS Signature Version 4 (SigV4), 3. ❌so Claude Code can’t directly do that itself. 4. ❌ User must run a local proxy to sign requests

Atmos ftw 😏, I do like the sigv4 stuff for the context keys in iam but yeah aws put in few loops 🤦🏽‍♂️