S3 bucket creation - Can't add Write roles to it

AWS S3 bucket gets created, however I can’t make changes to it or upload content to it with an IAM user. It doesn’t allow me to create a write access role.

Is this on the KodeKloud AWS Playground? IAM roles are not currently supported. The team are currently looking into getting this added.

It is KK AWS playground. Failed to create bucket. If IAM is not supported, then S3 buckets can’t be created without appropriate rules.

========
To create a bucket, the s3:CreateBucket permission is required.

View your permissions in the IAM console . Identity and Access Management in Amazon S3

API response

Access Denied

I just created an S3 bucket in us-east-2. What region are you trying to create your bucket in?
Refer to the playground for the supported regions:
AWS SandBox Playground | KodeKloud

Yes, I agree it works in the specified regions. But there are IAM rules still restricting to access S3. Unfortunately, this created S3 of no use if it doesn’t allow creating policies to access it for Pipeline testing etc. What I am trying to do is, test this S3 bucket as an artifact base and build my pipeline around it so I can statically host a website for testing.

==============
Your bucket policy changes can’t be saved

You either don’t have permissions to edit the bucket policy, or your bucket policy grants a level of public access that conflicts with your Block Public Access settings. To edit a bucket policy, you need the s3:PutBucketPolicy permission. To review which Block Public Access settings are turned on, view your account and bucket settings. Learn more about Identity and access management in Amazon S3

API response

Access Denied

Hi Mohan, We will fix this issue ASAP, There was an issue S3 bucket policies where they are creating buckets with root user, We cannot able to delete those buckets, so we are finding an alternative solution to fix the issue, we should have the alternative solutions by EOD of next week

Has this been fixed?

Hi @mohankumar101 , The team is still actively working on resolving the issue regarding S3 bucket policies. We appreciate your patience, and we’ll keep you posted once we have developments or solutions in place.

Best,

When can I have a potential fix for this please?