Download to read offline
Uploaded bySubramanyam Vemala
Migration architecture on_prem
This document discusses architectures for deploying Microsoft Active Directory (SAFE) on AWS across multiple regions and VPCs. It describes deploying Active Directory on EC2 instances in a single region and VPC, in a single region with multiple VPCs using VPC Peering, and in multiple regions with multiple VPCs using VPC Peering. A multi-region, multi-VPC approach can provide benefits like resolving latency issues for globally distributed users, withstanding regional failures through failover, and complying with regional data hosting requirements.
More Related Content
Similar to Migration architecture on_prem
Migration architecture on_prem
- 1. SAFE AWS MigrationArchitecture with multiple regions and multiple VPC’s.
- 2. VPC AWS Cloud –SAFE Availability Zone 1 Availability Zone 2 Seamless Domain Join Instance Amazon EC2 Auto Scaling SAFE Users Private subnet Corporate data center AWS Direct Connect Elastic Load Balancing Private subnet On-Premises ADEC2 InstancesEC2 Instances EC2 Instances Internet gateway Internet SAFE AWS Architecture in a VPC in a Region – with AWS Directory Service. AWS Directory Service
- 3. Deploying Active Directoryon EC2 instances in a single region for single VPC:
- 4. Deploying Active Directoryon EC2 instances in a single region with multiple VPC’s using VPC Peering:
- 5. Deploying SAFE inmultiple regions with multiple VPC’s using VPC Peering:
- 6. Another view -Deploying SAFE in multiple regions with multiple VPC’s using VPC Peering.
- 7. Multiple Region Multi-VPCConnectivity: 1. To extend the SAFE to the global reach, considering the users geographic footprint in the multiple locations like US, UK and others, we can create multiple VPCs in different regions. 2. Multi-Region SaaS - approach can be used to resolve the latency issues that are often associated with geographic distribution of the users.
- 8. Other features ofMulti-Region SaaS deployment: • Failover: The ability to withstand regional system failures, enabling part or all of a system to effectively transition load to an alternate region. • Latency: The need to process and serve non-static data without incurring the overhead of long network hops. • Compliance: Variations in regional compliance requirements means data and services must be regionally hosted.