This repository was archived by the owner on Aug 18, 2025. It is now read-only.
Do not require public-read acl #13
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
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.
Issue:
some companies do not allow the usage of public-read ACL for S3. In that case the bin/deploy
aws s3 cp <filename> <target-bucket> --acl public-readwill fail.Description of changes:
This change removes the
--acl public-read. To make sure cloudformation is still able to access the file in the s3 bucket its execution role gets s3:GetObject permission on the template bucket.By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.