This repository has been archived by the owner on Jun 1, 2023. It is now read-only.
Update S3 Access Permissions for new AWS Policy #428
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.
Changes
When I was running the initial setup Terraform for staging, it seems like there was a change in the default configuration of S3 buckets and the ACL setup config is no longer valid. This relates to a change apparently arrived in April 2023 (this month) which disables ACLs by default.
For the state setup, it's fine to remove the ACL since the new default is to block public access which is the desired config.
For the main S3 storage for the static site, it seems there are still issues in Terraform regarding the policy change that are still be added. See the following Terraform issues:
Screenshots
This is what was happening.
For the state setup:
After the fix, this worked:
For the main deployment setup:
After the fix, this worked:
Checklist