Check ID:
Provider: AWS
Service:
Severity: MEDIUM
Categories:
Resource type:
elasticache_redis_cluster_in_transit_encryption_enabledProvider: AWS
Service:
elasticacheSeverity: MEDIUM
Categories:
encryptionResource type:
OtherWhat this check verifies
ElastiCache for Redis replication groups have in-transit encryption (TLS) enabled for client and inter-node traffic (TransitEncryptionEnabled=true).
Risk
Absent in-transit encryption, traffic between apps and Redis or between nodes can be eavesdropped or tampered. This exposes keys, tokens, and cached sensitive data, enables MITM and session hijacking, and can corrupt replication, harming confidentiality and integrity.Recommendation
Enable TLS by settingTransitEncryptionEnabled=true and enforce a strict mode (require TLS 1.2+).
Ensure clients validate certificates, restrict network paths, and pair with least privilege plus Redis AUTH/RBAC for defense in depth.
Remediation
- CLI
- Terraform
- Native IaC
- Dashboard steps
aws elasticache modify-replication-group —replication-group-id <example_resource_id> —transit-encryption-enabled —transit-encryption-mode preferred —apply-immediately
References
- https://www.trendmicro.com/trendaivisiononecloudriskmanagement/knowledge-base/aws/ElastiCache/in-transit-and-at-rest-encryption.html
- https://docs.aws.amazon.com/AmazonElastiCache/latest/dg/in-transit-encryption-enable.html
- https://docs.aws.amazon.com/AmazonElastiCache/latest/dg/in-transit-encryption.html
Where this check fires
This check runs on every scheduled scan against your AWS account. Findings appear at Cloud Security → Findings filterable byCheck ID = elasticache_redis_cluster_in_transit_encryption_enabled. To re-evaluate after a fix, hit Run now on the account’s schedule under Cloud Security → Schedules — the next scan re-checks this control and marks the finding fixed or keeps it persistent.
← Back to AWS checks