🛡️ AWS DMS Replication Instance engine version has reached end of life🟢

• Contextual name: 🛡️ Replication Instance engine version has reached end of life🟢
• ID: /ce/ca/aws/dms/replication-instance-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 DMS Replication Instance
  • 🔌 AWS DMS Replication Instance - object.extracts.yaml
  • 🧪 test-data.json

Description

Open File

Description

Ensure that AWS Database Migration Service (DMS) replication instances use an engine version before its published end-of-life (EOL) date.

Rationale

AWS schedules automatic upgrades at a version's EOL. A retained instance reporting that version after the deadline warrants investigation and a tested upgrade, or reconciliation of stale inventory. This is an actionable operational lifecycle check, not a requirement to run the newest release or evidence of a specific vulnerability.

Impact

An engine upgrade interrupts replication. Verify endpoint compatibility and task behavior before scheduling maintenance, including source-log retention for change data capture (CDC). Multi-AZ deployment does not exempt an instance from engine lifecycle assessment or eliminate the need to plan the upgrade interruption.

Audit

This policy marks an AWS DMS Replication Instance as INCOMPLIANT if it is not in an excluded Status listed below and its current Engine Version is 3.4.6, 3.4.7, 3.5.1, 3.5.2, 3.5.3, or 3.6.0. These releases have already reached EOL and are matched directly, without checking the evaluation date. Version 3.5.4 is INCOMPLIANT on or after March 31, 2027, its future EOL date. The earlier no-new-instance restriction does not make an existing instance noncompliant.

... see more

Remediation

Open File

Remediation

Select an engine version that is available for the instance class and Region and has not reached its published AWS DMS EOL date. Review its release notes and test migration tasks, source and target compatibility, validation, and change data capture behavior.

First compare the live instance with the finding. If the current version has already been upgraded, refresh Cloudaware inventory instead of scheduling another upgrade. Use the current AWS DMS lifecycle calendar; availability for new instances and EOL are different milestones. Check valid upgrade targets with describe-engine-versions as well as the class and Region offerings.

Using the AWS Console

1. Open AWS DMS, select the instance's Region, and choose Replication instances.
2. Select the instance and review its current version, pending changes, and maintenance window.
3. Record instance configuration, task settings, table mappings, and recovery checkpoints. Schedule an interruption and ensure source logs remain available throughout the CDC outage. Stop active tasks immediately before the agreed upgrade window and verify they have stopped.

... see more

policy.yaml

Open File

Linked Framework Sections

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