- Newest
- Most votes
- Most comments
Hello
If you logged into the web console using AWS root account and created an S3 bucket using this root account, you default to having root privileges for the entire AWS Account, so you do NOT need to make any AWS IAM policies. You can try to lift the policy restrictions on your root account and try enable S3 transfer acceleration again. Actually, I haven‘t meet the problem you described when using the root account when i use root account.
By the way,using the root account directly is NOT secure. I strongly recommend that you don't use the root user for your everyday tasks. Safeguard your root user credentials and use them to perform the tasks that only the root user can perform,for details please see: What is IAM?, I recommend you follow the Prerequisite: Setting up Amazon S3 steps to create a iam user.
when you use iam user(for example iam username is my-iam-username
),and this user has AdministratorAccess
permission policy
you can try to create a new s3 bucket and then configuring fast, secure file transfers using Amazon S3 Transfer Acceleration.this can help you locate the cause of the problem
Relevant content
- asked 4 months ago
- asked 6 months ago
- asked a year ago
- asked a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 9 months ago
thanks, I already tried your suggestion with an IAM user and ended up with the same issue. I even went into the IAM Policy Simulator and according to that tool, my user should be able to edit the bucket's properties.