Moving CIDRs between scopes allows you to optimize IP address allocation, organize by Region, separate concerns, enforce compliance, and adapt to infrastructure changes. This flexibility helps manage your IP address space efficiently as your workloads evolve.
Follow the steps in this section to move a VPC CIDR from one scope to another.
Important
-
You can only move VPC CIDRs. When you move a VPC CIDR, the VPC's subnet CIDRs are moved automatically as well.
-
You can only move VPC CIDRs from one private scope to another. You cannot move VPC CIDRs out of a public scope to a private scope or from a private scope to a public scope.
-
The same AWS account must own both scopes.
-
If a VPC CIDR is currently allocated from a pool in a private scope, the move request succeeds, but the VPC CIDR will not be moved until you release the VPC CIDR allocation from the current pool. For information on releasing an allocation, see Release an allocation.
To move a CIDR allocated to a VPC
Open the IPAM console at https://console.aws.amazon.com/ipam/
. -
In the navigation pane, choose Resources.
-
From the dropdown menu at the top of the content pane, choose the scope you want to use.
-
In the content pane, choose a VPC and view the details of the VPC.
-
Under VPC CIDRs, select one of the CIDRs allocated to the resource and choose Actions > Move CIDR to different scope.
-
Select the scope you want to move the VPC CIDR to.
-
Choose Move CIDR to different scope.
