AWS Managed Directory Services (including AWS Microsoft AD)–Q and A
Can I use AWS Managed Microsoft AD as a primary directory?
- Yes. You can use it as a primary directory to manage users, groups, computers, and Group Policy objects (GPOs) in the cloud.
- You can manage access and provide single sign-on (SSO) to AWS applications and services, and to third-party directory-aware applications running on Amazon EC2 instances in the AWS Cloud.
- In addition, you can use Azure AD Connect and AD FS to support SSO to cloud applications, including Office 365.
Can I use AWS Managed Microsoft AD as a resource forest?
Yes. You can use AWS Managed Microsoft AD as a resource forest that contains primarily computers and groups with trust relationships to your on-premises directory. This enables your users to access AWS applications and resources with their on-premises AD credentials.
AWS SSO is also a managed Service
- To set up AWS SSO, you must first sign in to your AWS organization’s master account
- AWS Single Sign-On enables administrators to connect their on-premises Active Directory (AD) or their AWS Managed Microsoft AD directory using AWS Directory Service.
- This Microsoft AD directory defines the pool of identities that administrators can pull from when using the AWS SSO console to assign single sign-on (SSO) access.
- After connecting their corporate directory to AWS SSO, administrators can then grant their AD users or groups access to AWS accounts, cloud applications, or both.
- AWS Directory Service helps you to set up and run a standalone AWS Managed Microsoft AD directory hosted in the AWS Cloud.
- You can also use AWS Directory Service to connect your AWS resources with an existing on-premises Microsoft Active Directory.
- To configure AWS Directory Service to work with your on-premises Active Directory, you must first set up trust relationships to extend authentication from on-premises to the cloud.
Leave a Reply