Recovering Cloud Assembly to Other Region

Recover Resources to Other Region Using a New VPC

Recovery creates new VPC in the DR region with same IP range (CIDR Block) as source VPC and recovers the selected resources and its dependencies to the new VPC.

The recovered EC2 instances will have the same private IPs as the source EC2 instances.

The subnets will be created with same IP ranges, but the availability zones in the DR regions are automatically chosen.

You do not have an option to manually map the availability zone from source to destination region.

Example: If the source VPC is say "Prod-VPC" with 10.0.1.0/24, the new VPC created during recovery in the DR region will also have the same CIDR block 10.0.1.0/24 and the EC2 instances will have the same private IPs as the source EC2 instances.

Recover Resources to Other Region Using an Existing VPC

Recover the resources in a Pre-Created/ Existing VPC with either same configuration as the source VPC (Same IP Ranges and CIDR Blocks) or similar configuration as source (but with different IP Ranges and CIDR Blocks) in the DR region.

Conditions

• The following resources are expected to be pre-created in a pre-existing VPC
• VPC Network
• Subnet
• Route Table
• Internet Gateway

• DHCP Option

• The source Security Group rules should be modified to have the pre-created subnet IP ranges allowed, so that the same are reflected in the recovery.

Source and destination VPC CIDR should have same capacity and same number of subnets (to support one to one mapping). Example: 172.31.0.0/16 (Source) and 10.31.0.0/16 (Destination) is acceptable whereas 172.31.0.0/16 (Source) and 10.31.0.0/20 (Destination) is not acceptable.

• It is expected to have the subnets pre-created with equivalent configuration as source in the DR/Pre-Existing VPC.
  Example, If the subnet in the source VPC are of ranges 10.0.1.0/24 and 10.0.2.0/24.

a) If the pre-existing VPC is of the same IP range as the source VPC.
-- Same subnets (IP Ranges) are expected to be Pre-created in the Pre-existing VPC -- 10.0.1.0/24 and 10.0.2.0/24

b) If the pre-existing VPC is of different IP range than that of the source VPC. -- Equivalent subnets (Number of available IPs) are expected to be pre-created in the pre-existing VPC -- 172.16.1.0/24 and 172.16.2.0/24

• The source and destination subnets can be mapped for the recovery. -- You can use tags to auto map the destination subnet to the source subnets. -- If no tags are added, you have to manually map the subnets.

Example tag format: Recovery resource tag name - ax-recovery-subnet-id & value - subnet-0297f00011dba2xx

• Routes have to be manually updated.
  For example, Nat Gateway which is created during the recovery on a pre-existing VPC has to be manually updated in the route table.