Open stavro opened 8 years ago
Output of my "safezones" command:
$ aws ec2 describe-availability-zones --query 'AvailabilityZones[*].ZoneName' --output text | awk '{print $1, $2}'
us-east-1a us-east-1b
Looks like this isn't really fixable.
Workaround: export ZONES="us-east-1a us-east-1c"
We should consider adding this to the quickstart docs.
I think I've run into this before as well. The problem was because I accidentally deleted the default subnets that a new AWS account creates by default.
From http://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/default-vpc.html#deleting-default-vpc
If you delete your default VPC and need a new one, you can contact AWS Support to create a new default VPC in that region for you. You cannot mark an existing VPC as a default VPC.
So I just contacted AWS support and had them fix it for me.
Didn't find any open issues discussing this.
Examining the Aws console:
Looks like the root cause: