Apache Airflow versions on Amazon Managed Workflows for Apache Airflow
This topic describes the Apache Airflow versions Amazon Managed Workflows for Apache Airflow supports, and best-practices for upgrading to the latest version.
Topics
About Amazon MWAA versions
Amazon MWAA builds container images that bundle Apache Airflow releases with other common binaries and Python libraries. The image uses the Apache Airflow base install for the version you specify. When you create an environment, you specify an image version to use. Once an environment is created, it keeps using the specified image version until you upgrade it to a later version.
Latest version
Amazon MWAA supports more than one Apache Airflow version. If you don't specify an image version when you create an environment, Amazon MWAA creates an environment using the latest supported version of Apache Airflow.
Apache Airflow versions
The following Apache Airflow versions are supported on Amazon Managed Workflows for Apache Airflow.
Note
-
Effective December 30, 2025, Amazon MWAA will end support for Apache Airflow versions v2.4.3, v2.5.1, and v2.6.3. For more information, refer to End-of-support versions.
-
Beginning with Apache Airflow v2.2.2, Amazon MWAA supports installing Python requirements, provider packages, and custom plugins directly on the Apache Airflow webserver.
-
Beginning with Apache Airflow v2.7.2, your requirements file must include a
--constraintstatement. If you don't provide a constraint, Amazon MWAA will specify one for you to ensure the packages listed in your requirements are compatible with the version of Apache Airflow you're using.For more information about setting up constraints in your requirements file, refer to Installing Python dependencies.
| Apache Airflow version | Apache Airflow release date | Amazon MWAA availability date | Apache Airflow constraints | Python version |
|---|---|---|---|---|
|
May 19, 2026 |
||||
|
July 23, 2026 |
||||
|
January 7, 2026 |
||||
|
October 1, 2025 |
||||
|
December 18, 2024 |
||||
|
September 26, 2024 |
||||
|
July 9, 2024 |
||||
|
February 23, 2024 |
||||
|
November 6, 2023 |
For more information about migrating your self-managed Apache Airflow deployments, or migrating an existing Amazon MWAA environment, including instructions for backing up your metadata database, refer to the Amazon MWAA Migration Guide.
Apache Airflow components
This section describes the number of Apache Airflow schedulers and workers available for each Apache Airflow version on Amazon MWAA, and provides a list of key Apache Airflow features, indicating the version that supports each feature.
Schedulers
Schedulers for Apache Airflow v2 and later:
| Scheduler (default) | Scheduler (min) | Scheduler (max) |
|---|---|---|
|
2 |
2 |
5 |
Workers
Workers for Apache Airflow v2 and later:
| Workers (default) | Workers (min) | Workers (max) |
|---|---|---|
|
10 |
1 |
25 |
Upgrading the Apache Airflow version
Amazon MWAA supports minor version upgrades. This means you can upgrade your environment from version x.1.z to x.2.z, but not to a new major version, for example, from 1.y.z to 2.y.z.
For more information, and detailed instructions on updating your workflow resources, and upgrading the environment to a new version, refer to Changing the Apache Airflow version.
Downgrading the Apache Airflow version
Amazon MWAA supports minor version downgrades to an earlier version that is still supported at the time of downgrade. This means you can downgrade your environment from version x.2.z to x.1.z, but not to a previous major version, for example, from 2.y.z to 1.y.z.
For more information, and detailed instructions on updating your workflow resources, and upgrading the environment to a new version, refer to Changing the Apache Airflow version.
Apache Airflow deprecated versions
The following table lists the deprecated versions of Apache Airflow in Amazon MWAA, along with initial release and end-of-support dates for each version. For more information about migrating to a newer version, refer to the Amazon MWAA Migration Guide.
| Apache Airflow version | Apache Airflow release date | Amazon MWAA availability date | Amazon MWAA end-of-support date |
|---|---|---|---|
| v1.10.12 | August 25, 2020 | November 24, 2020 | February 21, 2024 |
| v2.0.2 | April 19, 2021 | May 25, 2021 | April 29, 2024 |
| v2.2.2 | November 15, 2021 | January 27,2022 | June 27, 2024 |
| v2.4.3 | November 14, 2022 | January 05, 2023 | December 30, 2025 |
| v2.5.1 | January 20, 2023 | April 11, 2023 | December 30, 2025 |
| v2.6.3 | July 10, 2023 | August 09, 2023 | December 30, 2025 |
End-of-support versions
We follow the Apache Airflow community release process and version policy
We are committed to supporting an Apache Airflow version for at least 12 months after it first becomes available.
If any Amazon MWAA environments in your account run the version nearing the end of support, we send a notice through the Health Dashboard with the end of support date.
On the end of support date:
You can no longer use a deprecated version to create new Amazon MWAA environments.
You can no longer upgrade or downgrade existing environments to deprecated versions.
You can still use your existing environments on deprecated versions and perform in-place updates.
You can no longer receive technical support for environments running on deprecated versions.
You can continue to access your existing Amazon MWAA environments that run the associated, deprecated version of Apache Airflow at your own risk. For instructions on upgrading to a newer version of Apache Airflow, see the Amazon MWAA Migration Guide.
Important
You are responsible for keeping your Amazon MWAA versions current. We urge you to upgrade to the latest version for current security, privacy, and availability safeguards. Operating past the deprecation date (on a "legacy version") increases security, privacy, and operational risks, including downtime. By continuing on a legacy version, you acknowledge these risks and agree to upgrade as soon as possible.
Legacy versions are not generally available and we no longer support them. We might restrict access to any legacy version at any time if it poses a security or liability risk. Continuing on a legacy version might result in your content becoming unavailable, corrupted, or unrecoverable. SLA exceptions apply.
Legacy environments and related software might contain bugs, errors, defects, and harmful components. We provide the legacy version as is, notwithstanding any contrary terms in your agreement.
For more information about shared responsibility, see Shared responsibility in the AWS Well-Architected Framework.
