Check ID:
Provider: AWS
Service:
Severity: MEDIUM
Categories:
Resource type:
redshift_cluster_automatic_upgradesProvider: AWS
Service:
redshiftSeverity: MEDIUM
Categories:
vulnerabilitiesResource type:
AwsRedshiftClusterWhat this check verifies
Amazon Redshift clusters have automatic major engine upgrades allowed viaAllowVersionUpgrade so updates are applied during the maintenance window.
Risk
Without automatic upgrades, clusters can run vulnerable engine versions, enabling exploits against known flaws. Attackers may read or tamper data (confidentiality/integrity), and unresolved bugs can cause downtime (availability). Delayed patching increases exposure window and operational risk.Recommendation
EnableAllowVersionUpgrade to keep clusters patched. Use a controlled maintenance window and an appropriate maintenance track; validate upgrades in staging before production.
Align with secure-by-default and defense in depth; keep tested backups and rollback plans. Document justified exceptions and review regularly.
Remediation
- CLI
- Terraform
- Native IaC
- Dashboard steps
aws redshift modify-cluster —cluster-identifier <cluster_id> —allow-version-upgrade
References
- https://docs.aws.amazon.com/systems-manager-automation-runbooks/latest/userguide/automation-aws-modify-redshift-maintenance.html
- https://docs.aws.amazon.com/redshift/latest/mgmt/managing-cluster-operations.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_automatic_upgrades. 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