1 Answer
- Newest
- Most votes
- Most comments
1
Hello. Although you mentioned you're creating a new bucket, it's possible there are service-linked roles or organization-wide policies that automatically apply certain bucket policies. Solution: Check if there's an organizational policy or SCP (Service Control Policy) that might be preventing the creation or modification of S3 buckets.
Also double check do you enable:
Object Ownership Bucket owner preferred
Regards, Andrii
Relevant content
- asked 10 months ago
- asked 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 9 months ago
- AWS OFFICIALUpdated 2 years ago
Thank you for your reply, but I don't have permission to view my organization-wide policies.
The thing is that I have an existing CDK stack in the same AWS account and using the same IAM user, which includes similar S3 bucket code, and it deploys without any issues. The issue only occurs with the new stack.
In the new stack, I've only moved the S3 bucket code from the existing stack to the new stack. The IAM user has the necessary permissions to create and modify S3 buckets. I've also ensured that the S3 bucket name is unique and not recently used. Could you please help me identify the cause of this issue and suggest how to resolve it?