Takeaway: On November 20, 2026, AWS said Amazon S3 now supports at least 11,000 GET/HEAD requests per second for general purpose buckets, up from 5,500. The increase applies automatically to existing read requests in all AWS Regions, with no application changes and no additional charge beyond standard S3 request pricing.
The details below come from that official What’s New post. This is a request-rate change for general purpose buckets, not a new storage class, and it is separate from the language and country-targeting update we covered earlier today in Amazon Bedrock Web Search Adds Languages and Country Targeting.
What changed
AWS says general purpose S3 buckets now support at least 11,000 GET and HEAD requests per second, up from 5,500. The What’s New headline describes the change as an increase “by up to 2x.” The post presents the higher rate as a way to retrieve data faster for read-intensive workloads. The examples it gives are machine learning training, data analytics, and data transfers.
The announcement is limited to GET and HEAD requests on general purpose buckets. It does not state a new rate for PUT, POST, DELETE, or COPY requests, and it does not mention directory buckets or other S3 bucket types.
How to get the most from the higher rate
To maximize throughput, AWS says you should distribute your requests across multiple prefixes so that S3 can scale each one independently. The What’s New post does not define a prefix, publish a per-prefix number, or say that 11,000 requests per second is a per-prefix cap. It states the “at least 11,000” figure for general purpose buckets, and it treats prefix distribution as the way to maximize throughput.
The post also does not require a new API, a new bucket setting, or a request to AWS Support. It says the increase applies automatically to your existing read requests.
Regions, changes, and pricing
AWS says the increase applies automatically to existing read requests in all AWS Regions. Applications do not need to change. There is no additional charge beyond standard S3 request pricing.
The post does not introduce a new request-pricing tier, a promotional credit, or a free-tier change. “No additional charge beyond standard S3 request pricing” means the usual GET and HEAD request prices still apply; AWS is not describing a surcharge for the higher rate, and it is not saying those requests became free.
What AWS did not announce
The November 20 post does not change write-request rates, list a latency improvement, or publish benchmark results. It does not say whether the previous 5,500 figure was a hard cap in every account, and it does not guarantee that every workload will reach 11,000 requests per second. It also does not discuss S3 Express One Zone, S3 Transfer Acceleration, or CloudFront. For local testing of AWS APIs, we previously covered the AWS Emulator; this announcement is about the live S3 service, not a local emulator.
Key facts
| Item | What official sources say |
|---|---|
| Announcement | AWS What’s New post, dated November 20, 2026. |
| Product | Amazon S3 general purpose buckets. |
| New read rate | At least 11,000 GET/HEAD requests per second, up from 5,500. Headline: an increase by up to 2x. |
| Intended workloads | Read-intensive work such as machine learning training, data analytics, and data transfers. |
| How to maximize throughput | Distribute requests across multiple prefixes so S3 can scale each prefix independently. |
| Regions | All AWS Regions. |
| Customer impact | Applies automatically to existing read requests. No application changes required. |
| Pricing | No additional charge beyond standard S3 request pricing. |
FAQ
What did AWS announce on November 20, 2026?
AWS said Amazon S3 now supports at least 11,000 GET/HEAD requests per second for general purpose buckets, up from 5,500. The What’s New post describes the change as an increase by up to 2x.
Does this apply to every S3 bucket type?
The official post is about general purpose buckets. It does not mention directory buckets or other S3 bucket types, and this article does not extend the new rate to those products.
Did AWS also raise write request rates?
No. The announcement is limited to GET and HEAD requests. It does not state a new rate for PUT, POST, DELETE, or COPY requests.
Do applications need to change?
AWS says the increase applies automatically to existing read requests, with no changes required to your applications.
Is there an extra charge for the higher rate?
AWS says there is no additional charge beyond standard S3 request pricing. The post does not introduce a new pricing tier or say that GET and HEAD requests became free.
Which Regions are included?
AWS says the increase applies in all AWS Regions.
How can you maximize throughput?
AWS says you should distribute requests across multiple prefixes so that S3 can scale each prefix independently. The What’s New post does not publish a per-prefix number or treat 11,000 requests per second as a documented per-prefix cap.
Will every workload reach 11,000 requests per second?
AWS states the figure as “at least 11,000” for general purpose buckets, and it does not guarantee that every workload will reach that rate. The post also does not publish latency or benchmark results.
