Check ID:
Provider: AWS
Service:
Severity: MEDIUM
Categories:
Resource type:
redshift_cluster_multi_az_enabledProvider: AWS
Service:
redshiftSeverity: MEDIUM
Categories:
resilienceResource type:
AwsRedshiftClusterWhat this check verifies
Amazon Redshift clusters are evaluated for Multi-AZ deployment on provisionedRA3 clusters, confirming compute spans two Availability Zones and is served via a single endpoint.
Risk
Absent Multi-AZ, a single-AZ cluster is exposed to AZ or node failures, leading to dropped connections, aborted queries, and stalled ETL/BI jobs. This reduces availability, increases RTO, delays analytics, and risks SLA breaches with cascading pipeline backlogs.Recommendation
Enable Multi-AZ deployments for provisionedRA3 clusters to avoid single-AZ dependency. Align designs to fault tolerance and high availability: provision sufficient capacity, implement client/ETL retries and reconnects, validate failover periodically, and monitor performance and error rates.
Remediation
- CLI
- Terraform
- Native IaC
- Dashboard steps
aws redshift modify-cluster —cluster-identifier <cluster-id> —multi-az
References
- https://docs.aws.amazon.com/redshift/latest/mgmt/managing-cluster-multi-az.html
- https://docs.aws.amazon.com/redshift/latest/mgmt/overview-multi-az.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 = redshift_cluster_multi_az_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