Why am I getting 503 Slow Down errors from Amazon S3 when the requests are within the supported request rate per prefix?
"The rate of requests to a prefix in my Amazon Simple Storage Service (Amazon S3) bucket is within the supported request rates per prefix, but I'm getting 503 Slow Down errors."
"The rate of requests to a prefix in my Amazon Simple Storage Service (Amazon S3) bucket is within the supported request rates per prefix, but I'm getting 503 Slow Down errors.ResolutionAmazon S3 supports a request rate of 3,500 PUT, COPY, POST, DELETE or 5,500 GET, HEAD requests per second per prefix in a bucket. When you create a prefix, Amazon S3 doesn't automatically assign the resources for this request rate. Instead, as the request rate for a prefix gradually increases, Amazon S3 automatically scales to handle the increased request rate.When you make requests at a high request rate that's close to the rate limit, Amazon S3 returns 503 Slow Down errors. To prevent these errors, maintain the request rate and implement a retry with exponential backoff. This allows Amazon S3 time to monitor the request patterns, and scale in the backend to handle the request rate.If there's a sudden increase in the request rate for objects in a prefix, then Amazon S3 might return 503 Slow Down errors. It returns these errors as it scales in the background to handle the increased request rate. To prevent these errors, configure your application to gradually increase the request rate. Then, use an exponential backoff algorithm to retry failed requests.If you exceed supported request rates, then it's a best practice to distribute objects and requests across multiple prefixes.Note: If the preceding resolutions don't resolve the errors, then get the request IDs for the failed requests, and contact AWS Support.Follow"