Airflow 3.0.6 on MWAA, but AWS Local Runner still on 2.10.3

[sridharkdw]

I’ve upgraded my MWAA environment to Airflow 3.0.6, which is now available and running successfully in Production/Sandbox. However, when testing locally with the AWS Local Runner, it is still pinned to Airflow 2.10.3.

1. Is there a timeline for when the AWS Local Runner will be updated to support Airflow 3.0.6?

2. Is there a recommended workaround until the local runner is aligned with the latest MWAA release?

Sridhar

[trozzelle]

Seconding this request.

[vishalvijay18]

Please use this repository instead: https://github.com/aws/amazon-mwaa-docker-images

MWAA environments use amazon-mwaa-docker-images, and is also actively managed by the service team. If there is any feature gap between local runner and above repository, please let us know.

[trozzelle]

Thank you! Should we expect mwaa-local-runner to be deprecated for Airflow 3+? Not a problem, we just have some custom tooling built on top of the local runner and I want to know if we should migrate to amazon-mwaa-docker-images.

[vishalvijay18]

Yes, support for 3.x on mwaa-local-runner will likely not be provided.

[sridharkdw]

Vishal, "support for 3.x on mwaa-local-runner will likely not be provided" which refers to this repo will no longer support migration of future airflow versions?

[vishalvijay18]

which refers to this repo will no longer support migration of future airflow versions?

yes