This is still quite confusing I think.
Amazon S3 automatically adjusts the prefix value according to the request rate.
So as an end-user I have no way of impacting prefixing at all, because it's all automatic?
A partitioned prefix in a bucket can support 3,500 PUT/COPY/POST/DELETE or 5,500 GET/HEAD requests per second.
And by extension it's impossible to know what the actual limit is? Because this is a lower bound that is multiplied by a prefix value that is managed by AWS and invisible to us as the end user?
For prefixes, "/" is just another character. The "/" does not indicate a partition placement.
This also implies that the prefix partitioning can happen anywhere in the key name?
Thank you for your comment. We'll review and update the Knowledge Center article as needed.
In the video on youtube, you said the prefix is "BucketName/Project/WordFiles/", but in this post, you said the prefix is “BucketName/Project/WordFiles/123.txt”. Which is correct?
Thank you for your comment. We'll review and update the Knowledge Center article as needed.
It's been 3 months and you still haven't updated the article or even properly acknowledged the questions. "Thank you, we will review, etc." is not an adequate response because it is generic. You should be answering the specific questions with specific answers if you expect folks to actually get help from this knowledge-center.
This post is quite unclear and confusing. It also points to the 2018 video which is out of date. Probably best to just delete this post and point to the current s3 performance whitepaper at: https://docs.aws.amazon.com/whitepapers/latest/s3-optimizing-performance-best-practices/introduction.html
Relevant content
- asked 3 months ago
- asked 2 months ago
- Accepted Answerasked 2 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago