How to Fix MWAA Environment Stuck 'Unavailable' During AWS Outage

Select Language:

If your Managed Workflows for Apache Airflow (MWAA) environment has been stuck in an “Unavailable” state following an AWS outage, here’s a step-by-step guide to help you resolve the issue.

First, understand that even if your production environment seems to be running fine, the “Unavailable” status prevents you from making configuration changes. This can be frustrating, especially if you need to update settings like autoscaling or concurrency.

To fix this, start by checking your current environment setup. For example, if you’ve recently tried to increase the autoscale from 10,1 to 20,1, and it causes the environment to roll back to “Unavailable,” it indicates a problem with applying such updates. Sometimes, the configuration changes work in a different environment with similar setups, but issues remain in the affected one.

The key step is to contact AWS Support. They can often help recover environments stuck in a bad state or even force the environment into a “Healthy” condition. Explain your situation clearly, including the specific changes you attempted and your current environment configuration. Be sure to mention details like your current parameters:

– Autoscale: 20,1
– DAG concurrency: 20
– Parallelism: 20
– Maximum worker count: 10
– Minimum worker count: 1
– Web server count: 2 (both min and max)
– Scheduler count: 2
– Environment class: mw1.medium

If you’re comfortable with some troubleshooting, try deleting and recreating the environment. This can sometimes reset the state, though it might involve downtime.

Another thing to consider is verifying that your AWS account has the appropriate permissions and that no resource limits are being hit.

In summary, when experiencing an “Unavailable” environment in MWAA, your best course of action is to reach out to AWS Support for assistance. They can help force your environment into a healthy state, allowing you to make and apply new configuration updates smoothly.

Always keep detailed notes of your environment’s current settings and recent changes when contacting support—this helps speed up the troubleshooting process.