🛡️ AWS MWAA Environment Airflow version is unsupported🟢

• Contextual name: 🛡️ Environment Airflow version is unsupported🟢
• ID: /ce/ca/aws/mwaa/environment-airflow-version-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 MWAA Environment
  • 🔌 AWS MWAA Environment - object.extracts.yaml
  • 🧪 test-data.json

Description

Open File

Description

This policy identifies AWS MWAA environments whose configured Apache Airflow version has reached its Amazon MWAA end-of-support date. It uses the AWS support schedule reviewed on October 27, 2026. A supported release does not fail merely because a newer release exists or upstream Apache Airflow support has ended.

Rationale

An environment can continue operating after MWAA ends support for its Airflow version, but AWS no longer provides technical support for that environment. Continued use increases security, privacy, and operational risks, including downtime. Upgrading to a supported release reduces these risks and restores access to technical support.

Impact

Changing Airflow versions can affect DAGs, provider packages, plugins, Python dependencies, and configuration options. Plan a maintenance window and test workflow compatibility before upgrading.

Audit

This policy marks an AWS MWAA Environment as INCOMPLIANT if its Status is AVAILABLE or

... see more

Remediation

Open File

Remediation

1. Confirm the current version and status.

   Check Status and Airflow Version in the MWAA console or run:

   aws mwaa get-environment \
     --name ENVIRONMENT_NAME \
     --region REGION \
     --query 'Environment.{Status:Status,AirflowVersion:AirflowVersion}'

   Wait for any update or rollback to finish. If the status is UPDATE_FAILED, investigate the previous failure before retrying.

2. Choose a supported target release.

   Select an exact release supported by Amazon MWAA and available in the environment's AWS Region. Review the release notes, AWS Health notices, and any required intermediate upgrade steps. The target need not be the latest release.

3. Test compatibility and prepare for recovery.

   Test DAGs, provider packages, plugins, configuration, startup scripts, and Python dependencies using the matching MWAA local runner. Update the requirements.txt constraint URL for the target Airflow and Python versions. Back up workflow resources, configuration, and metadata, and retain

... see more

policy.yaml

Open File

Linked Framework Sections

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