Understanding which access control mechanism to employ in order to control
and audit access to your S3 buckets and objects is tricky. This is because the
method to be chosen really depends on how you intend to use the buckets and
also the way you work within your organization.
I went through several resources, blogs, forums and Amazon's own resources
to make it understandable and easy to remember. It helped me understand many
points, I hope it helps you as well.
There are mainly 3 ways of regulating the
access to the buckets and objects in S3 which are namely:
- Bucket Policies
- Bucket ACLs
- IAM Policies
Bucket Policies: A “Bucket Policy” is an
internal regulation structure specific to S3 which means that bucket
policies can only be employed within S3 and nowhere else. They are
applied at the bucket level, which also means that a same policy should be
manually applied to each and every bucket for the same controls.
It allows AWS admins to apply
enforcement actions (allow or deny) per users/ groups (principals) for specific
actions (put, delete, read, etc.).
Typical Use Cases
- When granting cross-account access to S3 resources in a simple way, without using IAM.
You can use ACLs to grant
cross-account permissions to other accounts, but ACLs support only a finite set
of permission (List, Read, Write), these don't include all Amazon S3
permissions. For example, you cannot grant permissions on bucket sub-resources
using an ACL. Although both bucket and user policies support granting
permission for all Amazon S3 operations, the IAM policies are for managing
permissions for ONLY users in your account. For cross-account
permissions to other AWS accounts or users in another account, you must use a
bucket policy.
- When there is a need to write bigger policies in size. Bucket Policies can be up to 20 KB, (IAM policies can be up to 2 KB for users, 5 KB for groups and 10 KB for roles).
- When you prefer keeping the access controls within S3.
An interesting difference
between S3 Bucket Policies and IAM Policies is that in the Bucket Policies JSON
document, there is a “Principal” field to be filled detailing to which user or
group the actions are going to be applied. The principal field does not exist
in IAM policies because in order to be functional, they already have to be
assigned to a user or a group.
Typical Use Cases
- Creating centrally managed, user-based access policies and control everything from IAM.
- Manage a bigger number of buckets.
Bucket ACLs: The Bucket ACLs are the
legacy way of controlling access to buckets and objects in S3. They are more
granular compared to bucket policies as they can be applied per object and not
per bucket.
Bucket ACLs use an Amazon
S3–specific XML schema and do not look like bucket policies or IAM policies
which are JSON files.
There are currently only 3 actions
supported by Bucket ACLs which are List, Read and Write. Detailed permissions
such as in bucket policies or IAM policies are not possible with Bucket ACLs.
There are limits to managing
permissions using ACLs. For example:
- You can grant permissions only to other AWS accounts; you cannot grant permissions to users in your account.
- You cannot grant conditional permissions, nor can you explicitly deny permissions.
ACLs are suitable for
specific scenarios. For example, if a bucket owner allows other AWS accounts to
upload objects, permissions to these objects can only be managed using object
ACL by the AWS account that owns the object.
Typical Use Cases
- Cross-account access.
- Object level permission setting requirements within a bucket.
- The only recommended use case for the bucket ACL is to grant write permission to the Amazon S3 Log Delivery group to write access log objects to your bucket.
Bucket Policies and IAM
Policies are User-based policies while Bucket ACLs are resource based.
If you’re still unsure of which to use,
consider which audit question is most important to you:
- If you’re more interested in “What can this user do in AWS?” then IAM policies are probably the way to go. You can easily answer this by looking up an IAM user and then examining their IAM policies to see what rights they have.
- If you’re more interested in “Who can access this S3 bucket?” then S3 bucket policies will likely suit you better. You can easily answer this by looking up a bucket and examining the bucket policy.
