1 Answer
- Newest
- Most votes
- Most comments
1
I believe you don't need to set up additional EC2 AD DS instances if you use AWS Managed AD. Follow these steps to set up AD using AWS Managed AD: https://fitdevops.in/how-to-setup-aws-managed-microsoft-active-directory/ Once you have that in place you can install MS Exchange and connect it to your AWS Managed AD deployment.
However, if this is a new setup, why not just use managed services for both AD and Exchange? Look at the instructions in this video starting with Architecture #3 - https://youtu.be/14BTX5gCs38 With this setup, you can provide the same service, but you won't have to manage the Exchange configuration.
answered a year ago
Relevant content
- asked 2 months ago
- asked 2 years ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 8 months ago
- AWS OFFICIALUpdated 10 months ago
- AWS OFFICIALUpdated 7 months ago
Managed services for both seems like a solid way to go. Would you happen to know which pieces I need to bring from my current, third-party vendor in order to get these managed services looking and operating "the same" when I turn them on Day 1? EG, all my current users, groups (AD), and O365 applications and their content (Outlook, etc)? I have done a small AD migration in the past just for the developers in my org, and all that was really needed was the SAML config from the third party; but I have not done onboarded an email server and its contents before.
There is actually a document to walk you through the migration of both Active Directory and Exchange:
Hope this helps and good luck!