fix(query): ecs_cluster_not_encrypted_at_rest initial implementation #7636
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.
Closes #7093
Reason for Proposed Changes
Proposed Changes
LaunchTemplateData
.BlockDeviceMappings
.Ebs
field of the "AWS::EC2::LaunchTemplate" resource's "Properties" block (doc); alternatively theBlockDeviceMappings
field set in anAWS::EC2::Instance
can overwrite the values set in the template and so is also checked. This should ensure any EC2 instance that is declared is encrypted and account for most "ECS clusters" use cases but , as suggested per the linked documentation, could require improvements for scenarios not accounted for. The query will flag in case the path to the "Encrypted" field is incomplete or in case the field is set to false.I submit this contribution under the Apache-2.0 license.