- Newest
- Most votes
- Most comments
There's a pretty good outline on all of this available here including the steps you'd need to take to promote your EC2 instance.
It really boils down to just these 2 options.
-
This assumes that there is network connectivity either Site-to-Site VPN or DirectConnect between your on-premises environment and AWS without overlapping CIDR ranges. For this, just stand up new EC2 instances and dc promo them as additional domain controllers in your forest. Once the new DCs are fully operational, you can set their IP into the DHCP option set for the VPC.
-
If you don't plan to connect the two environments, then you can use the AWS Application Migration Service or VM Import/Export to make block-level duplicates of the on-premise servers, even keeping the on-premise IP addresses (if the network topology allows it).
Thanks Michael. Can i demote the on premise AD after it is proven to be operational ? Does the option 1 clones all AD objects(Users,Groups,Computers) to AWS from on-premise ?
Relevant content
- asked 4 years ago
- asked 2 years ago
- asked 2 years ago
AWS OFFICIALUpdated a year ago- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 16 days ago
- AWS OFFICIALUpdated 6 months ago
Thanks.Can i demote the on premise AD after it is proven to be operational ? Does it clone all AD objects(Users,Groups,Computers) to AWS from on-premise ?
The guide covers all of that in detail -- for example, you shouldn't demote your on-prem AD unless you have connectivity to the AWS AD server from your on-prem environment.