Closed mo-gr closed 5 years ago
When the Appserver has a VPCZoneIdentifier configuration, like:
VPCZoneIdentifier
VPCZoneIdentifier: Fn::FindInMap: - LoadBalancerSubnets - Ref: AWS::Region - Subnets
This should be translated to the Elastigroup create argument compute.subnetIds.
compute.subnetIds
Currently, this does not happen, resulting in instances being potentially created in the wrong subnets.
A workaround is to explicitly specify the compute.subnetIds argument in the Elastigroup configuration:
Elastigroup: compute: subnetIds: Fn::FindInMap: - LoadBalancerSubnets - Ref: AWS::Region - Subnets
When the Appserver has a
VPCZoneIdentifier
configuration, like:This should be translated to the Elastigroup create argument
compute.subnetIds
.Currently, this does not happen, resulting in instances being potentially created in the wrong subnets.
A workaround is to explicitly specify the
compute.subnetIds
argument in the Elastigroup configuration: