Open kenden opened 8 years ago
@kenden probably your account (or region) was freshly set up and we need to share the Taupage AMI with you.
Thanks @hjacobs. I don't use Taupage (yet?), that's why it's not in the region, I suppose.
I found a better workaround though.
I removed
SenzaComponents:
- Configuration:
Type: Senza::StupsAutoConfiguration
from the Senza template. Without this, find_taupage_image()
is not called at all and doesn't fail.
I was only using SenzaComponents
to get Subnets with:
Fn::FindInMap: [LoadBalancerSubnets, {"Ref": "AWS::Region"}, Subnets]
I replaced that by adding a mapping and referring to it.
Mappings:
production:
Subnets:
value:
- subnet-b91e59b1
- subnet-e338181e
test:
Subnets:
value:
- subnet-e315ec95
- subnet-849d6cdc
Fn::FindInMap: ["{{Arguments.Environment}}", Subnets, value]
It would be nice to be able to get this mapping (LoadBalancerSubnets
) automatically but I understand if Taupage is required if one decides to use SenzaComponents
.
(Extra documentation could be good here).
I am running Senza to create a stack in the region eu-west-1, it is working fine. I am not using Taupage (we already have our own system to manage the AMIs). Instead, I create my own Autoscalling group, Launch Configuration and ELB in the Senza template. This looks like this:
When running this in the region eu-central-1, this fails:
This seems to be throw from here
There are indeed no AMIs with those properties in eu-central-1:
The workaround is then to create one, but this feels clumsy.