VPC deploy fails when deploying 2nd stack?
davidham opened this issue · 1 comments
I am using a lightly modified version of this stack in my company, and our staging environment has been using it with no trouble. Today I tried to spin up another instance of this stack, but it fails in the VPC step with the following error:
Embedded stack arn:aws:cloudformation:us-east-1:REDACTED:stack/my-environment-VPC-SOME_ID/42f61810-7b94-11e7-812e-50d5ca6e601e was not successfully created: The following resource(s) failed to create: [PrivateSubnet2RouteTableAssociation, PrivateSubnet1RouteTableAssociation, NatGateway1EIP, PublicSubnet1RouteTableAssociation, NatGateway2EIP, DefaultPublicRoute, PublicSubnet2RouteTableAssociation].
The stack name is different than the existing stack from this template.
Do I need to change the CIDR ranges in the master template if it's a new VPC?
Never mind, I think I traced it--it failed because we had reached our limit for EIPs in us-east-1. Looks like this environment needs two EIPs, one for each NAT gateway?