- Le plus récent
- Le plus de votes
- La plupart des commentaires
I'd suggest you to go through this re:Post Knowledge Center Article
Same topic is discussed in this re:Post answer, where it's discussed that If there is a fast spike in the request rate for objects in a prefix, Amazon S3 might return 503 Slow Down errors while it scales in the background to handle the increased request rate. To avoid these errors, you can configure your application to gradually increase the request rate and retry failed requests using an exponential backoff algorithm.
Additionally take a look at Optimizing S3 Performance
Hope this helps.
Abhishek
Hello, Amazon S3 has a limit of 5500 requests per second per prefix. Besides, there is a service quota limit per account. When you exceed the service quota, S3 got throttled. You can request a service quota increase. For further information you may visit the AWS documentation [https://docs.aws.amazon.com/general/latest/gr/s3.html#limits_s3].
I scan s3 as anonymous user, so there is no quota increase for me. And 5500 is not in my case.
Contenus pertinents
- demandé il y a 6 mois
- demandé il y a 6 mois
- demandé il y a 4 mois
- AWS OFFICIELA mis à jour il y a 2 ans
- AWS OFFICIELA mis à jour il y a un an
- AWS OFFICIELA mis à jour il y a 9 mois
- AWS OFFICIELA mis à jour il y a un an
I didn't encounter 503, it's just 404 instead of 403 (if bucket exists)