This message was deleted.
# general
s
This message was deleted.
s
Usually you specify a subnet or az where you want your ec2 to be placed. Which it sounds like you have and at that time t2.micros were not available. Maybe create an array of instance sizes that are acceptable and catch the error and iterate through the list until one is aval otherwise kill the program with specified error?
n
Thanks. Like I said I solved the problem as a prototype by just hard-coding the AZ (it's not an HA or fault-tolerant setup).
g
Pulumi does not distribute across zones automatically. If you omit the zone or subnet, AWS will assign one.
n
That makes that error particularly weird, then.
But apparently, not pulumi's fault, at least