You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Our rack is Private=Yes and we're using InstanceType=t3.medium, which is a problem with AvailabilityZones=us-east-1a,us-east-1b,us-east-1c, because t3.medium isn't available in us-east-1a.
CloudFormation error message:
CIDR Block must change if Availability Zone is changed and VPC ID is not changed
So, we've tried to set AvailabilityZones to:
us-east-1b,us-east-1c,us-east-1d
OR us-east-1d,us-east-1e,us-east-1f
However, later we've noticed, in order to change the AvailabilityZones we also needed to change CIDR blocks for all the subnets (including private ones.) So this is what we tried in the end:
So, previously here@ddollar suggests this should work, however in both of our attempts CloudFormation failed with the following error message:
NatGateway nat-0d5e9c2f963ab7d1c is in state failed and hence failed to stabilize. Detailed failure message: Elastic IP address [eipalloc-025cc22bfe58bce88] is already associated
I am not sure at this point how to proceed.
Can anyone please jump in and help us out? Thanks!
Latest Update
Dated: 9 Mar 2022
The text was updated successfully, but these errors were encountered:
Issue Description
Re-posting https://community.convox.com/t/trying-to-change-availabilityzones-of-a-private-rack/863
Our rack is
Private=Yes
and we're usingInstanceType=t3.medium
, which is a problem withAvailabilityZones=us-east-1a,us-east-1b,us-east-1c
, becauset3.medium
isn't available inus-east-1a
.CloudFormation error message:
So, we've tried to set
AvailabilityZones
to:us-east-1b,us-east-1c,us-east-1d
us-east-1d,us-east-1e,us-east-1f
However, later we've noticed, in order to change the
AvailabilityZones
we also needed to change CIDR blocks for all the subnets (including private ones.) So this is what we tried in the end:Before:
Attempt no. 1:
(Uses
us-east-1b,us-east-1c,us-east-1d
AZs and10.2.1*.0
IPs.)Attempt no. 2:
(Uses
us-east-1d,us-east-1e,us-east-1f
AZs and10.2.2*.0
IPs.)So, previously here @ddollar suggests this should work, however in both of our attempts CloudFormation failed with the following error message:
I am not sure at this point how to proceed.
Can anyone please jump in and help us out? Thanks!
Latest Update
Dated: 9 Mar 2022
The text was updated successfully, but these errors were encountered: