refactor(cdn): remove ACL parameter from S3 uploads, rely on bucket policy instead #153
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This change removes the object-level ACL parameter from S3
putObjectcalls, eliminating the need for thes3:PutObjectAclIAM permission.Motivation
Object-level ACLs are being phased out in favor of bucket policies as an AWS best practice. By removing the
ACL: 'public-read'parameter, we can tighten IAM permissions and manage public access centrally through bucket policy instead.Changelog
ACLparameter fromuploadFileToStoragefunctionDEFAULT_ACLconstantTest Plan