Troubleshooting HTTP 5xx errors from Amazon S3

Types of 5xx status errors

• AmazonS3Exception: Internal Error (Service: Amazon S3; Status Code: 500; Error Code: 500 Internal Error; Request ID: A4DBBEXAMPLE2C4D): The error code 500 Internal Error indicates that Amazon S3 can't handle the request at that time.
• AmazonS3Exception: Slow Down (Service: Amazon S3; Status Code: 503; Error Code: 503 Slow Down; Request ID: A4DBBEXAMPLE2C4D): The error code 503 Slow Down typically indicates that the number of requests to your S3 bucket is very high.

Troubleshoot 5xx errors

Because Amazon S3 is a distributed service, a very small percentage of 5xx errors is expected during normal use of the service. All requests that return 5xx errors from Amazon S3 can be retried. This means that it's a best practice to have a fault-tolerance mechanism or to implement retry logic for any applications making requests to Amazon S3. By doing so, S3 can recover from these errors.

To resolve these errors, see How do I troubleshoot a HTTP 500 or 503 error from Amazon S3?

Prevent 5xx errors

• Configure your applications to gradually increase request rates.
• Follow best practices to distribute objects across multiple prefixes.
• When building applications that upload and retrieve objects from Amazon S3, follow best practices guidelines to optimize performance.
• To optimize S3 performance and avoid 5xx errors, use the best practice design patterns. Also, see Amazon s3 performance tips and tricks.

Related re:Post Questions

• Receiving S3 503 slow down responses
• 500 Internal Server Error from OPTIONS method in REST API integration with S3
• EMRFS and S3 503 slow down responses
• S3 multipart upload to presigned URL returns HTTP 500 on OPTIONS request