2 Answers
- Newest
- Most votes
- Most comments
1
Hi!
You can call update-environment, either with the new S3 version ID for your new plugins/requirements.txt or with an additional configuration override, such as custom.lastupdate = "<current time>", as part of your CI/CD pipeline that will force MWAA to restart.
Thanks!
answered 4 years ago
0
Note that, as of Airflow 2.0, you do not need to package custom operators as plugins and should simply place them somewhere in your S3 dags folder. These will be synced automatically by MWAA to each container and no restart is required. See https://airflow.apache.org/docs/apache-airflow/stable/plugins.html .
answered 2 years ago
Relevant content
- asked 2 years ago
- asked 3 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 7 months ago
- AWS OFFICIALUpdated a year ago
Not sure how to use the configuration override. I tried
aws mwaa update-environment --name dev custom.lastupdate = "<current time>"
but got an error 'Unknown options: =, <current time>, custom.lastupdate'