- Newest
- Most votes
- Most comments
Hello...I have confirmed that--constraint
is being detected as expected in Airflow 2.5.1 on Amazon MWAA. Please double-check your requirements.txt and access to the constraint file from all MWAA containers (noting that private web servers do not have Internet access) and perform an environment update. For private web servers, you may need to provide a local constraints file as described in https://docs.aws.amazon.com/mwaa/latest/userguide/connections-packages.html#connections-packages-newer-packages.
If not already, you should also test your requirements and constraints using https://github.com/aws/aws-mwaa-local-runner.
Thank you for your reply; I appreciate it.
Please note that this was a previously working setup that stopped working (not a new setup).
Due to a timely release of 2.6.3 on MWAA, I have since upgraded my environment and am back to a working setup.
Thanks again. A
Relevant content
- asked 3 years ago
- Accepted Answerasked 3 years ago
- asked a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 16 days ago
- AWS OFFICIALUpdated a month ago
- AWS OFFICIALUpdated a month ago
We're having the same issue as described above (first occurrence on Aug 7 19:00 UTC), though we're using a local constraints file and packaged WHL files due to private webserver config.