Every project gets a VPC and a Default subnet automatically. Go to the VPC menu to see the overview, subnets and resources in the VPC. Services can reach each other by the name service-name.internal.
- You can add a subnet with a private IP range from /16 to /28 that sits within the VPC’s range.
- You can move the VPC to another IP range even with services in it: click VPC settings, enter the new range, check the impact shown, then click Move now (services will stop). Every service in the project stops for a while and comes back on new internal IPs.
.internalnames keep working, and data and volumes aren’t touched. (Owners and admins only; the new range must not overlap another VPC in the account or a peered VPC.) - Each VPC is completely separate from the others, until you join two with VPC peering (see Security groups and VPC peering).
If something goes wrong
I can’t delete a subnet
“ต้องลบบริการใน Subnet ก่อน” (Delete the services in the subnet first) or “Subnet นี้ใช้ NAT Gateway อยู่” (This subnet is using a NAT Gateway): move or delete the services, and remove the subnet from the NAT Gateway first. The Default subnet can be deleted like any other; the oldest subnet left then becomes the default.