- Newest
- Most votes
- Most comments
In what region have you setup you S3 bucket? S3 transfer acceleration is supported in the following regions: https://docs.aws.amazon.com/AmazonS3/latest/userguide/transfer-acceleration.html if your bucket is setup in one of the supported regions, in order to troubleshoot this issue and identify the root cause, please open a support case with AWS using the following link: https://console.aws.amazon.com/support/home#/case/create
My bucket is in us-east-1 it should be supported
So S3 Transfer acceleration uses CloudFront in the backend as listed in this whitepaper (https://docs.aws.amazon.com/whitepapers/latest/s3-optimizing-performance-best-practices/use-amazon-s3-transfer-acceleration-to-minimize-latency-caused-by-distance.html)
Cloudfront distribution is always deployed in us-east-1; thus, the verification requirement is us-east-1.
This is a verification mechanism that aws uses so email delivery is standard, what you can also try is to deploy a cloudfront distribution. If it's deployed successfully, s3 acceleration can be enabled.
The other option is that you reach out to AWS support and they can verify your account manually
Transfer acceleration was used in AWS Cloudfront on the back end. Because Cloudfront is a global service like IAM etc. validation is a must in us-east-1. You can also contact AWS support to verify your account manually.
For anyone reaching this page, the issue is account verification in N.virginia region.
Refer to this blog for details - https://engineering.doit.com/amazon-s3-transfer-acceleration-access-denied-how-to-fix-d2494aa95918
Even if we have my S3 buckets in any other region (say ap-southeast-2), will we need to run EC2 instances in us-east-1 for a few hours to resolve this?
But what if we don't get the email you mentioned about request validation?
It's still not clear.
Relevant content
- Accepted Answerasked 3 years ago
- asked 4 months ago
- asked a year ago
- asked 6 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 3 months ago
Hi Donoval, could you please post your IAM policy/policies attached to your IAM user/role and bucket policy(if there is one) here.
Still facing the issue even after trying all of the following: