Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Migrate away from bucket ACLs #71

Open
zack-is-cool opened this issue Oct 27, 2023 · 0 comments
Open

Migrate away from bucket ACLs #71

zack-is-cool opened this issue Oct 27, 2023 · 0 comments

Comments

@zack-is-cool
Copy link
Member

Checkov throwing this error

Check: CKV2_AWS_65: "Ensure access control lists for S3 buckets are disabled"
        FAILED for resource: module.bastion.aws_s3_bucket_ownership_controls.session_logs_bucket
        File: /s3-buckets.tf:29-38

We should be moving away from bucket ACLs according to AWS and moving to IAM/Bucket policies
https://aws.amazon.com/blogs/security/iam-policies-and-bucket-policies-and-acls-oh-my-controlling-access-to-s3-resources/

What about S3 ACLs?
An S3 ACL is a sub-resource that’s attached to every S3 bucket and object. It defines which AWS accounts or groups are granted access and the type of access. You can attach S3 ACLs to both buckets and individual objects within a bucket to manage permissions for those objects. As a general rule, AWS recommends that you use S3 bucket policies or IAM policies for access control. S3 ACLs are a legacy access control mechanism that predates IAM. By default, object ownership is set to the bucket owner enforced setting, and all ACLs are disabled, as can be seen in Figure 1.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant