Ensure Redshift clusters have cross-region snapshots for disaster recovery
Cross-region snapshot copies provide disaster recovery capability in case of regional failures or data corruption.
Security Impact
Without cross-region copies, regional disasters or data corruption cannot be recovered, causing permanent data loss.
How to Remediate
Enable cross-region snapshot copy to a different AWS region. Configure retention period based on RTO/RPO requirements.
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 Redshift 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, Business Continuity, Disaster Recovery compliance
- Drift Detection
Get alerted if this configuration drifts back to an insecure state after remediation
Check Details
- Check ID
- aws-redshift-16
- Service
- Amazon Redshift
- Category
- Disaster Recovery
- Severity
- MEDIUM
Automate This Check
TigerGate automatically scans your AWS environment for this and 575+ other security checks.
Start Free TrialRelated Amazon Redshift Checks
View all checksEnsure Redshift clusters are not publicly accessible
Ensure Redshift clusters have encryption at rest enabled
Ensure Redshift clusters have encryption in transit enabled
Ensure Redshift clusters have audit logging enabled
Ensure Redshift clusters have automated snapshots configured