1 Answer
- Newest
- Most votes
- Most comments
1
Hello.
I think it's probably due to a misconfiguration of the bucket policy that makes it impossible to operate using an IAM user.
If you can no longer do anything as an IAM user, use the AWS account root user to modify or delete the bucket policy.
https://repost.aws/knowledge-center/s3-accidentally-denied-access
You can sign in as the root user of your AWS account by following the steps in the document below.
By the way, the root user can perform all operations, so please be careful when handling it.
https://docs.aws.amazon.com/signin/latest/userguide/introduction-to-root-user-sign-in-tutorial.html
Relevant content
- asked 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 9 months ago
- AWS OFFICIALUpdated 9 months ago