When configuring an AWS provider in Platform, the choice is to let Platform create the VPC for you or specify an existing one.
When you let Platform create the VPC for you and the dynamic name already exists, it incorrectly removes the entry for 0.0.0.0/0 to an Internet Gateway in the Route Tables and then incorrectly adds an Internet Gateway instead.
This bug prevents deploying nodes in AWS using the online option and specifying that the nodes should not have a public ip address.
It is common practice to not assign a public ip address to database nodes but still give the nodes outbound Internet access so utilities like yum work correctly.
The alternative is to specify each Region and Availability Zone. However, if you do this, you will hit another bug outlined in 8907.
Lastly, if you decide to only put in the Regions and Availability Zones needed for a single Universe, you can't go back and edit it later. This is documented in 8570.
When configuring an AWS provider in Platform, the choice is to let Platform create the VPC for you or specify an existing one.
When you let Platform create the VPC for you and the dynamic name already exists, it incorrectly removes the entry for 0.0.0.0/0 to an Internet Gateway in the Route Tables and then incorrectly adds an Internet Gateway instead.
This bug prevents deploying nodes in AWS using the online option and specifying that the nodes should not have a public ip address.
It is common practice to not assign a public ip address to database nodes but still give the nodes outbound Internet access so utilities like yum work correctly.
The alternative is to specify each Region and Availability Zone. However, if you do this, you will hit another bug outlined in 8907.
https://github.com/yugabyte/yugabyte-db/issues/8907
Lastly, if you decide to only put in the Regions and Availability Zones needed for a single Universe, you can't go back and edit it later. This is documented in 8570.
https://github.com/yugabyte/yugabyte-db/issues/8570