AWS Builder Center

AWS Lambda Just Got a Serious Bandwidth Upgrade

AWS Lambda functions now support up to 3,000 Mbps of network bandwidth — a huge jump for data-intensive, serverless workloads. Here's what changed, why it matters, and where it could break your assumptions about "serverless doesn't scale for heavy I/O."

Quietly tucked into a recent AWS weekly roundup: Lambda functions now support up to 3,000 Mbps of network bandwidth.
What changed: Functions running outside a VPC, configured with 2 GB of memory or more, now get network bandwidth that scales proportionally with memory — starting at 625 Mbps at 2 GB and scaling up to 3,000 Mbps at 10 GB.
Why this matters: Lambda has always scaled compute and memory together, but network throughput was the quiet bottleneck nobody talked about. If your function pulled large files from S3, streamed data to Kinesis, or shuffled payloads between services, you'd often hit invisible ceilings — not from CPU, not from memory, but from network.
This update directly targets that gap. Think:
  • Bulk S3 reads/writes for ETL pipelines
  • High-throughput data transformation before writing to DynamoDB
  • Streaming workloads reacting to Kinesis in near real-time
  • Large payload processing in event-driven architectures
The bigger shift: For years, the advice for heavy I/O workloads was "move off Lambda, use Fargate or EC2." This update chips away at that assumption. Serverless is quietly becoming viable for a category of workloads it used to struggle with.
My take: This isn't a flashy AI announcement, but it's the kind of infrastructure update that quietly changes what "serverless" is capable of. Sometimes the boring updates matter more than the exciting ones.
Question for the community: Have you hit network bandwidth limits in Lambda before? Did it push you toward Fargate or EC2 instead? Curious if this changes your architecture decisions going forward.
Drop your thoughts below 👇
#AWS #Serverless #AWSLambda #CloudComputing #DevOps
Any opinions in this article are those of the individual author and may not reflect the opinions of AWS.
Enjoyed reading this content? Let the author know!

Your likes, comments, shares, and saves help creators reach more builders.

Loading recommendations

Loading article