AWS S3 empty bucket policy

mangotango

I have all my user permission needs covered using IAM, therefore I keep my bucket policy sections completely empty.

I was wondering if this is a good practice and if it raises any potential issues from any perspective.

Perhaps there is some configuration that is good to set as default?

Just double checking.

John Rotenstein

Typically:

  • When you want to grant 'public' access to an Amazon S3 bucket, use a Bucket Policy
  • When you want to grant access to specific IAM Users, attach an IAM policy to the IAM Users or IAM Groups

It sounds like your needs are satisfied via IAM policies, so that's perfectly good (and actually preferable!).

Collected from the Internet

Please contact [email protected] to delete if infringement.

edited at
0

Comments

0 comments
Login to comment

Related

AWS S3 bucket policy with condition

AWS S3 Bucket Policy is not valid

AWS S3 Bucket Policy Whitelist

I have a Query about AWS S3 bucket policy

AWS S3 Web Console overriding bucket policy

AWS S3 Bucket policy editor access denied

AWS S3 - permission to edit bucket policy

AWS S3: Setting a bucket policy for multiple users in an account

AWS S3: user policy for specifc bucket

AWS S3 Bucket Policy Explicit Deny

AWS s3 bucket multiple StringEquals conditions policy

AWS S3 Bucket Policy not working on mobile browsers

lost accss to AWS S3 bucket via policy

AWS - S3 - Creating a Bucket Policy - Error: Access Denied

How to specify AWS S3 bucket policy

AWS S3 Bucket policy Access Denyed

aws s3 bucket policy - allow range of ip addresses

AWS S3 bucket encryption - bucket property setting vs. bucket policy setting

Access denied when put bucket policy on aws s3 bucket with root user (= bucket owner)

S3 Bucket Policy to allow S3 Access to Current Authenicated user in AWS Console?

AWS: Could not able to give s3 access via s3 bucket policy

How to empty a S3 bucket using the AWS SDK for GOlang?

AWS S3 bucket policy for Get object, error in the policy generator Json code

How do I unlock or delete an AWS S3 bucket that inadvertently locked with a bucket policy?

Access denied on AWS s3 bucket even with bucket and/or user policy

Unable to use aws:username to get the current IAM uername in AWS S3 bucket policy

Does AWS S3 copy to same bucket preserves TTL (Expiration date - Lifecycle Policy)?

AWS IAM Policy Issues writing to s3 bucket for Grafana alerts

AWS Cloudfront - S3 with CloudFront Origin Access and Referer bucket policy