🛡️ AWS EMR Cluster release has passed a support lifecycle deadline🟢

• Contextual name: 🛡️ Cluster release has passed a support lifecycle deadline🟢
• ID: /ce/ca/aws/emr/cluster-release-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 EMR Cluster
  • 🔌 AWS EMR Cluster - object.extracts.yaml
  • 🧪 test-data.json

Description

Open File

Description

Ensure that Amazon EMR on EC2 clusters meet the release support requirements below. This policy evaluates the cluster's actual Release Label, independently of Hadoop, Spark, and other application versions. EMR on EKS and EMR Serverless resources are outside this policy's resource scope.

Rationale

EMR releases in End of Support receive no fixes or technical support. Migrating workloads to supported releases reduces security and operational risk.

A release need not be the latest to remain supported. AWS may deliver security fixes in a newer patch, minor, or major release and does not backport Core Engine fixes to older patch or minor versions. Release support alone therefore does not establish that every available security update is installed. Customer code, Extras, custom AMI contents, and independently installed applications require separate assessment.

Impact

An EMR release migration requires a replacement cluster and compatibility testing. Preserve required HDFS data, job outputs, logs, configuration, and credentials before terminating the original cluster.

... see more

Remediation

Open File

Remediation

Migrate to a supported EMR release

Migrate workloads to a replacement EMR on EC2 cluster running a supported release. EMR does not automatically upgrade existing clusters; updating a cluster creation template does not migrate a running cluster.

1. Verify the current cluster. Confirm the cluster's release label and state in the correct AWS account and Region using aws emr describe-cluster. Refresh Cloudaware discovery if the inventory is stale.

2. Choose a supported target release. Consult the AWS support lifecycle calendar. Review compatibility with applications, Java, Python, the operating system, bootstrap actions, and cluster configuration.

3. Create and test the replacement cluster. Use the selected release and reproduce the required networking, security configuration, IAM roles, logging, applications, and job settings. Run representative workloads and validate their outputs.

4. Preserve data and prepare recovery. Back up or migrate required HDFS data and other data stored on the original cluster. Plan the transition for scheduled jobs, streaming checkpoints, and dependent clients. Retain a recovery path until the replacement produces validated results.

... see more

policy.yaml

Open File

Linked Framework Sections

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