🛡️ AWS RDS Cluster engine is outside standard support🟢

• Contextual name: 🛡️ Cluster engine is outside standard support🟢
• ID: /ce/ca/aws/rds/cluster-engine-support
• Tags:
  • 🟢 Policy with categories
  • 🟢 Policy with type
  • 🟢 Production policy
• Policy Type: COMPLIANCE_POLICY
• Policy Categories: RELIABILITY

Stats

not available

Logic

• 🧠 prod.logic.yaml🟢
  • 📗 AWS RDS Cluster
  • 🔌 AWS RDS Cluster - cluster-engine-support.extracts.yaml
  • 🔌 AWS RDS Cluster - object.extracts.yaml
  • 🧪 test-data.json

Description

Open File

Description

This policy identifies Amazon RDS and Aurora DB clusters whose actual engine major version is outside AWS standard support. It evaluates Aurora MySQL, Aurora PostgreSQL, and RDS for MySQL/PostgreSQL Multi-AZ DB clusters once per cluster, using the AWS lifecycle calendar collected for the cluster's Engine and Engine Version Name.

Rationale

Remaining within standard support provides normal AWS engine maintenance and avoids dependence on paid RDS Extended Support. The actionable finding is to plan a tested major-version upgrade or approve a temporary exception with verified support coverage and costs. A version in Extended Support fails this standard-support requirement but can still receive critical security and bug fixes; it must not be described as entirely unsupported.

This is a major-version lifecycle check. A version does not fail merely because a newer major or minor version exists. Minor-version retirement, patch eligibility, and automatic minor upgrades require separate checks.

Impact

... see more

Remediation

Open File

Remediation

Plan and test a cluster engine upgrade to a major version within AWS standard support. Automatic minor version upgrades alone do not resolve an expired major-version support period.

Plan and perform the upgrade

1. Confirm the current configuration. Check the cluster's actual engine, major version, AWS support dates, and available upgrade targets in its Region. Reconcile stale CMDB data with the live AWS cluster before making changes.

2. Review compatibility and the upgrade path. Read the engine's AWS upgrade documentation and release notes. Check application SQL, drivers, extensions, parameter groups, readers, replicas, and global database dependencies. Follow supported intermediate upgrades when a direct upgrade is unavailable.

3. Test and prepare for recovery. Test the upgrade and application behavior on a restored copy or in a staging environment. Take and verify suitable backups, define recovery procedures, and schedule the production change within an agreed maintenance window.

4. Upgrade the cluster. Use the Amazon RDS console or your normal infrastructure deployment process, following the procedure for Aurora or a Multi-AZ DB cluster as appropriate. Coordinate global database members and verify Serverless capacity compatibility where applicable.

... see more

policy.yaml

Open File

Linked Framework Sections

Section	Sub Sections	Internal Rules	Policies	Flags	Compliance
💼 Cloudaware Framework → 💼 Infrastructure Modernization			39		no data