The limit of 0 environments has been reached.(MWAA)
While deploying MWAA in AWS ASIA PACIFIC(SEOUL) REGION, the following error occurred.
The limit of 0 environments has been reached.
I never deployed MWAA in that region, so why am I getting this error? Also, the community says to request a service quota increase, but I can't check the Seoul region on that page.
- Newest
- Most votes
- Most comments
Hello, could you mind change the region to Seoul and go to the Service Quotas console? You can see AWS services and you can find the MWAA quota there. Also you can make the request to increase quota if necessary. Thanks.
Hello, The mentioned error generally happens if your AWS account is relatively new or hasn't had enough activity in the past. Until the Service Quotas shows this information for limit increase, you may want to open a Support Case with AWS Customer Service to review the issue in your account.
I hope this helps. Feel free to update here if you have any question.
Relevant content
- asked a year ago
- asked 3 years ago
- asked 3 years ago
AWS OFFICIALUpdated a year ago- AWS OFFICIALUpdated 10 months ago
- AWS OFFICIALUpdated 10 months ago
- AWS OFFICIALUpdated 3 years ago
Hello, Thank you for your response. On the service quota page, only global is checked, and you cannot select other regions. In the case of S3, I can check the Seoul region, but when I select MWAA, Seoul disappears from the regions I can select. I don't know why this is happening, as MWAA is currently rolled out to the Seoul region as well, and it's not like it's difficult to create MWAA, so I don't know why the error I was getting earlier is happening.