π‘οΈ AWS ElastiCache Replication Group is not encrypted at restπ’
- Contextual name: π‘οΈ Replication Group is not encrypted at restπ’
- ID:
/ce/ca/aws/elasticache/replication-group-encryption-at-rest - Tags:
- π’ Policy with categories
- π’ Policy with type
- π’ Production policy
- Policy Type:
COMPLIANCE_POLICY - Policy Categories:
SECURITY
Logicβ
- π§ prod.logic.yamlπ’
Similar Policiesβ
Descriptionβ
Descriptionβ
This policy identifies AWS ElastiCache Replication Groups that are not configured with encryption at rest. Encryption at rest protects data stored on disk by encrypting it with a key managed through AWS Key Management Service (KMS).
Rationaleβ
Enabling encryption at rest is a critical security control that protects sensitive data in ElastiCache for Redis clusters. It ensures that if the underlying storage media is accessed or compromised, the data remains unreadable without the appropriate decryption key.
Auditβ
This policy flags an AWS ElastiCache Replication Group as
INCOMPLIANTif theAt Rest Encryption Enabledcheckbox is set to false.The Replication Group is marked as
INAPPLICABLEif itsStatusis not available.
Remediationβ
Remediationβ
Enable At-Rest Encryptionβ
Encryption at rest cannot be enabled on an existing ElastiCache replication group directly. You must create a new replication group from a backup with encryption enabled.
From Command Lineβ
Create a manual backup of your existing replication group:
aws elasticache create-snapshot \
--replication-group-id {{replication-group-id}} \
--snapshot-name {{snapshot-name}}Create a new replication group from the snapshot with encryption at rest enabled:
aws elasticache create-replication-group \
--replication-group-id {{new-replication-group-id}} \
--replication-group-description "Replication group with at-rest encryption enabled" \
--engine redis \
--snapshot-name {{snapshot-name}} \
--at-rest-encryption-enabled \
--transit-encryption-enabled \
--auth-token {{auth-token}} \
--cache-node-type {{cache-node-type}} \
--engine-version {{engine-version}} \
--cache-subnet-group-name {{subnet-group}} \... see more