Using service-linked roles for Amazon Directory Service - Amazon Directory Service
Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China (PDF).

Using service-linked roles for Amazon Directory Service

Amazon Directory Service uses Amazon Identity and Access Management (IAM) service-linked roles. A service-linked role is a unique type of IAM role that is linked directly to Amazon Directory Service. Service-linked roles are predefined by Amazon Directory Service and include all the permissions that the service requires to call other Amazon services on your behalf.

A service-linked role makes setting up Amazon Directory Service easier because you don't have to manually add the necessary permissions. Amazon Directory Service defines the permissions of its service-linked roles, and unless defined otherwise, only Amazon Directory Service can assume its roles. The defined permissions include the trust policy and the permissions policy, which cannot be attached to any other IAM entity.

You can delete a service-linked role only after first deleting its related resources. This prevents you from losing access to your Amazon Directory Service resources because you can't inadvertently remove the permissions to access the resources.

For information about other services that support service-linked roles, see Amazon services that work with IAM.

Service-linked role permissions for Amazon Directory Service

Amazon Directory Service uses the service-linked role named AWSServiceRoleForDirectoryService – Allows Amazon to monitor customer's self-managed domain controllers.

The AWSServiceRoleForDirectoryService service-linked role trusts the following services to assume the role:

  • ds.amazonaws.com

The role permissions policy named AWSDirectoryServiceServiceRolePolicy allows Amazon Directory Service to complete the following actions on the specified resources. For the complete policy permissions, see AWSDirectoryServiceServiceRolePolicy in the Amazon Managed Policy Reference.

  • ec2 – Allows the service to describe network resources such as VPCs, subnets, security groups, and network interfaces to validate hybrid connectivity configurations:

    • ec2:DescribeAvailabilityZones

    • ec2:DescribeDhcpOptions

    • ec2:DescribeNetworkInterfaces

    • ec2:DescribeRouteTables

    • ec2:DescribeSecurityGroups

    • ec2:DescribeSubnets

    • ec2:DescribeVpcs

  • ssm – Allows the service to send and monitor PowerShell guilabels to on-premises domain controllers for monitoring and assessment purposes:

    • ssm:Sendguilabel

    • ssm:Listguilabels

    • ssm:GetguilabelInvocation

    • ssm:DescribeInstanceInformation

    • ssm:GetConnectionStatus

You must configure permissions to allow your users, groups, or roles to create, edit, or delete a service-linked role. For more information, see Service-linked role permissions in the IAM User Guide.

Creating a service-linked role for Amazon Directory Service

You don't need to manually create a service-linked role. When you allows Amazon to monitor customer's self-managed domain controllers in the Amazon Web Services Management Console, the Amazon CLI, or the Amazon API, Amazon Directory Service creates the service-linked role for you. For more information about this change, see Policy updates.

Important

This service-linked role can appear in your account if you completed an action in another service that uses the features supported by this role. Also, if you were using the Amazon Directory Service service before January 1, 2017, when it began supporting service-linked roles, then Amazon Directory Service created the AWSServiceRoleForDirectoryService role in your account. To learn more, see A new role appeared in my Amazon Web Services account.

Editing a service-linked role for Amazon Directory Service

Amazon Directory Service does not allow you to edit the AWSServiceRoleForDirectoryService service-linked role. After you create a service-linked role, you cannot change the name of the role because various entities might reference the role. However, you can edit the description of the role using IAM. For more information, see Editing a service-linked role in the IAM User Guide.

Deleting a service-linked role for Amazon Directory Service

If you no longer need to use a feature or service that requires a service-linked role, we recommend that you delete that role. That way you don't have an unused entity that is not actively monitored or maintained. However, you must clean up the resources for your service-linked role before you can manually delete it.

Note

If the Amazon Directory Service service is using the role at the time that you try to delete the resources, then the deletion might fail. If that happens, wait for a few minutes and try the operation again.

To delete Amazon Directory Service resources used by the AWSServiceRoleForDirectoryService

To manually delete the service-linked role using IAM

Use the IAM console, the Amazon CLI, or the Amazon API to delete the AWSServiceRoleForDirectoryService service-linked role. For more information, see Deleting a service-linked role in the IAM User Guide.

Supported Regions for Amazon Directory Service service-linked roles

Amazon Directory Service does not support using service-linked roles in every Region where the service is available. However, Amazon Directory Service uses the AWSServiceRoleForDirectoryService role only in Amazon Web Services Regions where you can opt-in to hybrid directories.

Hybrid directory opt-in Region support
Region name Region identity opt-in support
US East (N. Virginia) us-east-1 Yes
US East (Ohio) us-east-2 Yes
US West (N. California) us-west-1 Yes
US West (Oregon) us-west-2 Yes
Europe (Stockholm) eu-north-1 Yes
Middle East (Bahrain) me-south-1 Yes
Asia Pacific (Mumbai) ap-south-1 Yes
Europe (Paris) eu-west-3 Yes
Asia Pacific (Jakarta) ap-southeast-3 Yes
Africa (Cape Town) af-south-1 Yes
Europe (Ireland) eu-west-1 Yes
Middle East (UAE) me-central-1 Yes
Europe (Frankfurt) eu-central-1 Yes
South America (São Paulo) sa-east-1 Yes
Asia Pacific (Hong Kong) ap-east-1 Yes
Asia Pacific (Hyderabad) ap-south-2 Yes
Asia Pacific (Seoul) ap-northeast-2 Yes
Asia Pacific (Osaka) ap-northeast-3 Yes
Europe (London) eu-west-2 Yes
Asia Pacific (Melbourne) ap-southeast-4 Yes
Europe (Milan) eu-south-1 Yes
Asia Pacific (Tokyo) ap-northeast-1 Yes
Asia Pacific (Singapore) ap-southeast-1 Yes
Asia Pacific (Sydney) ap-southeast-2 Yes
Canada (Central) ca-central-1 Yes
Europe (Spain) eu-south-2 Yes
Europe (Zurich) eu-central-2 Yes
China (Beijing) cn-north-1 No
China (Ningxia) cn-northwest-1 No