Do you have cross-account dependencies / shared resources?
Do you have a transit gateway, peered VPCs, etc?
Optional: Create or update a Network Diagram to describe your network setup (VPCs, subnets, routing, etc.). This is useful for exploring the questions below, and as a reference for Arpio to advise on your recovery environment. Here is an example:
Do you have external dependencies on:
Active Directory
External Firewall Appliances - Palo Alto, Fortinet, etc.
Third-party SaaS apps that require Internet connectivity
Marketplace images
Other?
Recovery Environment
What is your network architecture going to look like in the DR environment?
Will the DR environment be isolated from your production environment or connected?
How are IPs handled? Note: Arpio will replicate your IPs by default, but we do have the ability to renumber your recovery environment, if needed.
Is Arpio replicating Transit Gateways, resources shared across AWS accounts, or handling VPC peering?
Testing
When recovered, how are testers going to connect to the DR environment?
What is the plan for Application-level validation?
General Guidelines
To get complete resiliency, you will need to recover your environment in an alternate region and account. This gives you protection against both infrastructure outages, as well as ransomware and other cyber threats.
We generally recommend that you mirror your primary account structure in your DR environment – e.g. each source AWS account should have a mirror DR account.
Arpio does not support the ability to replicate one source environment into two accounts in the same region.