3 ms·
I am pretty sure that the default VPC assigns public IPs (and a default route to the IGW) so if you grew organically without some kind of plan I can see many st
by Bluecobra 3y ago
I am pretty sure that the default VPC assigns public IPs (and a default route to the IGW) so if you grew organically without some kind of plan I can see many startups having tons of ephemeral addresses or EIPs.
Also I just did a cleanup recently myself of this and migrated an account to a hub/spoke security VPC with transit gateway. AWS makes it real pain for running instances to migrate to private IP only. You have to play games with adding a second NIC/EIP to workaround this.
- hnlmorg 3y agoAWS really need to deprecate the default VPC. Experienced engineers know to avoid it and novices are encouraged to design things badly because of it. There should be a “wizard” type walkthrough to guide novices through creating their first VPC (they’d generally be managing AWS via “clickops” so a wizard type UI would work here).
- coredog64 3y agoYou should try the latest VPC creation wizard. It collects all the required information and then creates what you need. The biggest complaint I have with it is that it doesn’t write ID values to well known SSM parameters within the region.
- cyberax 3y agoI disagree. AWS should make it easier to just use routed IPv6, which makes the default VPC much more usable. And then just use one of the zero-trust overlays to secure communications between nodes.