Fix: Removal of maximum_execution_frequency argument for 3 rules. #171
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.
Description
Setting
check_elb_logging_enabled = true
andcheck_s3_bucket_level_public_access_prohibited = true
results in errors like so:There may be more than 2 rules affected by this issue, but these are the ones we have been trying to enable.
Fix
Removing the
maximum_execution_frequency
argument for the two rules allows for the rules to be created.Update
3rd rule found with the same issue:
dynamodb-table-encrypted-kms