This repository has been archived by the owner on Oct 11, 2021. It is now read-only.
Airflow installation doesn’t work in the latest AMIs #46
Labels
Milestone
Comments
tomfaulhaber
added a commit
to tomfaulhaber/aws-airflow-stack
that referenced
this issue
Nov 12, 2018
1. Parameterize the AMI so the template can be used in different regions (villasv#44) 2. Don't hardcode the region, use the one where the template is running (villasv#44) 3. Change the Airflow setup process so that it works on new AMIs (villasv#46) 4. Add the /efs filesystem to /etc/fstab so the system can be rebooted (villasv#45) 5. Change the name "SpotInstanceType" to "WorkerInstanceType" since we're not using spot yet and we don't want to confuse users.
|
It seems that the Amazon Linux pip won't concede an update: PR #48 indeed seems to fix it by leaving |
villasv
added a commit
that referenced
this issue
Nov 13, 2018
Parameterize the AMI so the template can be used in different regions (#44) Don't hardcode the region, use the one where the template is running (#44) Change the Airflow setup process so that it works on new AMIs (#46) Add the /efs filesystem to /etc/fstab so the system can be rebooted (#45) Change the name "SpotInstanceType" to "WorkerInstanceType" since we're not using spot yet and we don't want to confuse users.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Reported by @tomfaulhaber, didn't reproduce yet.
Still need to decide on #34, because providing baked AMIs adds a lot more complexity to the template, although it greatly simplifies the actual resource creation during autoscaling.
But again, autoscaling is not the main feature of the stack anymore. The installation is not that expensive and as long as it consistently works on the newer official Amazon Linux AMIs it should be fine.
The text was updated successfully, but these errors were encountered: