Skip to content

fix(vpc): fix number of available IPs #4728

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Mar 31, 2025
Merged

fix(vpc): fix number of available IPs #4728

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion pages/vpc/how-to/create-private-network.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -70,7 +70,7 @@ The IPv4 CIDR block is defined at the time of creating the Private Network. You

Automatically generating a CIDR block is the default (and recommended) setting when creating a Private Network. Simply follow the steps [above](#how-to-create-a-private-network) to create a Private Network, leave **Advanced Settings** at default values, and a `/22` CIDR block will be automatically generated for the Private Network.

This block is guaranteed to be unique within the VPC, and will not overlap with any of your other Private Networks. It gives 1024 private IPv4 addresses, of which 1022 are available to be allocated to resources attached to the Private Network. The first two and last two addresses in the block are not available.
This block is guaranteed to be unique within the VPC, and will not overlap with any of your other Private Networks. It gives 1024 private IPv4 addresses, of which 1020 are available to be allocated to resources attached to the Private Network. The first two and last two addresses in the block are not available.

#### Defining a custom CIDR block

Expand Down