Ensure ElastiCache clusters are not publicly accessible
ElastiCache clusters should only be accessible from within VPC, not from the internet. Public accessibility increases attack surface significantly.
Security Impact
Publicly accessible cache clusters expose sensitive data to internet-based attacks and unauthorized access attempts.
How to Remediate
Deploy clusters in private subnets without internet gateway routes. Use security groups to restrict access to application tier only.
Affected Resources
Compliance Frameworks
How TigerGate Helps
TigerGate continuously monitors your AWS environment to detect and alert on this misconfiguration. Here's what our platform does for this specific check:
- Continuous Scanning
Automatically scans all Amazon ElastiCache resources across your AWS accounts every hour
- Instant Alerts
Get notified via Slack, email, or webhooks when this misconfiguration is detected
- One-Click Remediation
Fix this issue directly from the TigerGate dashboard with our guided remediation
- Compliance Evidence
Automatically collect audit evidence for SOC 2, PCI-DSS, HIPAA compliance
- Drift Detection
Get alerted if this configuration drifts back to an insecure state after remediation
Check Details
- Check ID
- aws-elasticache-4
- Service
- Amazon ElastiCache
- Category
- Network Security
- Severity
- CRITICAL
Automate This Check
TigerGate automatically scans your AWS environment for this and 575+ other security checks.
Start Free TrialRelated Amazon ElastiCache Checks
View all checksEnsure ElastiCache Redis clusters have encryption at rest enabled
Ensure ElastiCache Redis clusters have encryption in transit enabled
Ensure ElastiCache Redis clusters have AUTH enabled
Ensure ElastiCache Redis has automatic backups enabled
Ensure ElastiCache Redis uses Multi-AZ with automatic failover