🛡️ AWS ElastiCache Cluster engine is outside standard support🟢

• Contextual name: 🛡️ Cluster engine is outside standard support🟢
• ID: /ce/ca/aws/elasticache/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 ElastiCache Cluster
  • 🔌 AWS ElastiCache Cluster - object.extracts.yaml
  • 🧪 test-data.json

Description

Open File

Description

Ensure that AWS ElastiCache node-based clusters use engine versions within AWS standard support. This policy assesses the current Engine and Engine Version, independently of automatic minor upgrades or a pending upgrade. It includes standalone clusters and replication-group members; ElastiCache Serverless caches are a separate resource type and are outside its scope.

Rationale

Remaining within standard support avoids paid Extended Support and reduces reliance on limited maintenance coverage and eventual forced upgrades. Owners can resolve findings by testing and scheduling a supported engine upgrade. Community EOL does not establish the end of AWS service support, and a version does not fail this policy merely because a newer version exists.

Impact

Upgrades can affect compatibility, connections, and availability. Test applications and plan a maintenance window. Extended Support findings indicate an upgrade requirement under this policy, not an assertion that AWS provides no support.

Audit

... see more

Remediation

Open File

Remediation

Upgrade to an Engine Version Within Standard Support

From Console

1. Confirm the current configuration. Confirm the cluster's current engine, version, status, and replication group in the ElastiCache console in the correct AWS account and Region. Compare these with Cloudaware; refresh collection if they differ. For replication-group members, plan one change for the replication group rather than changing individual nodes independently.

2. Choose a supported target version. Choose a compatible version within AWS standard support using the AWS engine upgrade guidance. Confirm availability in the cluster's Region and compatibility with its node type and deployment configuration. Consider Valkey for Redis OSS migrations where supported; the newest release is not required. Redis OSS 6 leaves standard support on January 31, 2027, so consider the target's remaining support window.

3. Test the upgrade and prepare recovery. Test client libraries, authentication, parameter groups, scripts, commands, replication, and application behavior against the target engine. Check the supported upgrade path and any intermediate upgrades. Plan rollback and a recoverable backup where supported; do not assume an engine downgrade is available.

... see more

policy.yaml

Open File

Linked Framework Sections

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