Use deny policies rather than conditions to reject insecure access #21
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.
There were some issues with the previous format, where the condition would be applied strangely and somewhat selectively. I couldn't reproduce them, but doing the policies this way is probably better.
This uses explicit "Deny" policies, which should be easier to understand, since they're applied before any other policies, making them simpler to manage.
Policies taken from https://github.com/terraform-aws-modules/terraform-aws-s3-bucket/blob/f90d8a385e4c70afd048e8997dcccf125b362236/main.tf#L965 and https://github.com/terraform-aws-modules/terraform-aws-s3-bucket/blob/f90d8a385e4c70afd048e8997dcccf125b362236/main.tf#L934