☁️ Cloud & Databases

AWS Bedrock AgentCore Ate My NAT Gateway Budget—Here's Why

A voice agent on AWS Bedrock AgentCore Runtime racked up $29 in NAT Gateway charges in six days—almost entirely from invisible S3 traffic. Here's what actually happened, and why your VPC setup is probably vulnerable to the same surprise.

AWS CloudWatch metrics showing inbound NAT Gateway traffic spike with S3 IP addresses identified in VPC Flow Logs

⚡ Key Takeaways

  • Bedrock AgentCore Runtime's warm pool continuously recycles container images from S3, generating massive hidden data transfer costs through NAT Gateways 𝕏
  • A free S3 Gateway VPC Endpoint completely eliminates this cost and should be standard infrastructure for any VPC with private subnets 𝕏
  • This pattern affects all containerized workloads on AWS—the problem isn't Bedrock-specific, it's systemic and largely undocumented 𝕏
Published by

Open Source Beat

Community-driven. Code-first.

Worth sharing?

Get the best Open Source stories of the week in your inbox — no noise, no spam.

Originally reported by Dev.to

Stay in the loop

The week's most important stories from Open Source Beat, delivered once a week.