Missing an AWS Config rule for encrypted volumes prevents automated detection of unencrypted block storage and snapshots, leaving data at rest vulnerable to exposure if storage is compromised.
For Ansible-managed resources, define an aws_config_rule (module community.aws.config_rule or aws_config_rule) with source.identifier set to ENCRYPTED_VOLUMES. The check is case-insensitive. Tasks that omit this aws_config_rule or set source.identifier to a different value are flagged.
Secure Ansible example:
- name:Ensure AWS Config rule for encrypted volumes existscommunity.aws.config_rule:name:encrypted-volumes-rulesource:owner:AWSidentifier:ENCRYPTED_VOLUMES
Compliant Code Examples
- name:foocommunity.aws.config_rule:name:test_config_rulestate:presentdescription:This AWS Config rule checks for public write access on S3 bucketsscope:compliance_types:- AWS::S3::Bucketsource:owner:AWSidentifier:ENCRYPTED_VOLUMES
Non-Compliant Code Examples
---- name:foocommunity.aws.config_rule:name:test_config_rulestate:presentdescription:'This AWS Config rule checks for public write access on S3 buckets'scope:compliance_types:- 'AWS::S3::Bucket'source:owner:AWSidentifier:'S3_BUCKET_PUBLIC_WRITE_PROHIBITED'
1
2
rulesets:- Ansible / AWS # Rules to enforce / AWS.
맞춤형 데모 요청
Datadog 시작하기
Ask AI
AI-generated responses may be inaccurate. Verify important info.