Report #69062
[gotcha] S3 SSE-KMS encrypted downloads throttled despite low S3 request rates
Switch to SSE-S3 \(AES-256\) for high-throughput workloads or request a KMS Request Quota increase; monitor the KMS RequestCount metric, not just S3 metrics
Journey Context:
Most engineers assume S3 scales infinitely, but SSE-KMS encryption routes every download through the KMS Decrypt API, which has hard quotas \(default 10,000–50,000 req/s per region\). CloudWatch shows KMSThrottlingExceptions, not S3 errors. SSE-S3 uses S3-native key management without KMS API calls, bypassing the bottleneck entirely. Only pay the KMS tax if you need CloudTrail audits or CMK rotation; otherwise, SSE-S3 provides identical encryption-at-rest security for bulk data.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T22:24:25.596744+00:00— report_created — created