AWS AmazonRDS documentation change
Summary
Updated references from 'AWS Directory Service' to 'Directory Service' for terminology consistency. Minor console link text changes and documentation phrasing adjustments.
Security assessment
Changes are primarily branding/terminology updates (removing 'AWS' prefix from Directory Service references). No new security controls or vulnerability fixes were introduced. The existing security-related IAM policy guidance about 'ds:GetAuthorizedApplicationDetails' was preserved but not modified in substance.
Diff
diff --git a/AmazonRDS/latest/UserGuide/USER_SQLServerWinAuth.SettingUp.md b/AmazonRDS/latest/UserGuide/USER_SQLServerWinAuth.SettingUp.md index 9425fac6b..904cf2bfc 100644 --- a//AmazonRDS/latest/UserGuide/USER_SQLServerWinAuth.SettingUp.md +++ b//AmazonRDS/latest/UserGuide/USER_SQLServerWinAuth.SettingUp.md @@ -13 +13 @@ You use AWS Directory Service for Microsoft Active Directory, also called AWS Ma -AWS Directory Service creates a fully managed, Microsoft Active Directory in the AWS Cloud. When you create an AWS Managed Microsoft AD directory, AWS Directory Service creates two domain controllers and Domain Name Service (DNS) servers on your behalf. The directory servers are created in two subnets in two different Availability Zones within a VPC. This redundancy helps ensure that your directory remains accessible even if a failure occurs. +Directory Service creates a fully managed, Microsoft Active Directory in the AWS Cloud. When you create an AWS Managed Microsoft AD directory, Directory Service creates two domain controllers and Domain Name Service (DNS) servers on your behalf. The directory servers are created in two subnets in two different Availability Zones within a VPC. This redundancy helps ensure that your directory remains accessible even if a failure occurs. @@ -15 +15 @@ AWS Directory Service creates a fully managed, Microsoft Active Directory in the -When you create an AWS Managed Microsoft AD directory, AWS Directory Service performs the following tasks on your behalf: +When you create an AWS Managed Microsoft AD directory, Directory Service performs the following tasks on your behalf: @@ -60 +60 @@ The admin account also has rights to perform the following domain-wide activitie - 1. In the [AWS Directory Service console](https://console.aws.amazon.com/directoryservicev2/) navigation pane, choose **Directories** and choose **Set up directory**. + 1. In the [Directory Service console](https://console.aws.amazon.com/directoryservicev2/) navigation pane, choose **Directories** and choose **Set up directory**. @@ -143 +143 @@ To see information about your directory, choose the directory ID in the director -If you use the console to create your SQL Server DB instance, you can skip this step. If you use the CLI or RDS API to create your SQL Server DB instance, you must create an IAM role that uses the `AmazonRDSDirectoryServiceAccess` managed IAM policy. This role allows Amazon RDS to make calls to the AWS Directory Service for you. +If you use the console to create your SQL Server DB instance, you can skip this step. If you use the CLI or RDS API to create your SQL Server DB instance, you must create an IAM role that uses the `AmazonRDSDirectoryServiceAccess` managed IAM policy. This role allows Amazon RDS to make calls to the Directory Service for you. @@ -145 +145 @@ If you use the console to create your SQL Server DB instance, you can skip this -If you are using a custom policy for joining a domain, rather than using the AWS-managed `AmazonRDSDirectoryServiceAccess` policy, make sure that you allow the `ds:GetAuthorizedApplicationDetails` action. This requirement is effective starting July 2019, due to a change in the AWS Directory Service API. +If you are using a custom policy for joining a domain, rather than using the AWS-managed `AmazonRDSDirectoryServiceAccess` policy, make sure that you allow the `ds:GetAuthorizedApplicationDetails` action. This requirement is effective starting July 2019, due to a change in the Directory Service API. @@ -147 +147 @@ If you are using a custom policy for joining a domain, rather than using the AWS -The following IAM policy, `AmazonRDSDirectoryServiceAccess`, provides access to AWS Directory Service. +The following IAM policy, `AmazonRDSDirectoryServiceAccess`, provides access to Directory Service. @@ -149 +149 @@ The following IAM policy, `AmazonRDSDirectoryServiceAccess`, provides access to -###### Example IAM policy for providing access to AWS Directory Service +###### Example IAM policy for providing access to Directory Service @@ -224 +224 @@ You can create users and groups with the Active Directory Users and Computers to -To create users and groups in an AWS Directory Service directory, you must be connected to a Windows EC2 instance that is a member of the AWS Directory Service directory. You must also be logged in as a user that has privileges to create users and groups. For more information, see [Add users and groups (Simple AD and AWS Managed Microsoft AD)](https://docs.aws.amazon.com/directoryservice/latest/admin-guide/creating_ad_users_and_groups.html) in the _AWS Directory Service Administration Guide_. +To create users and groups in an Directory Service directory, you must be connected to a Windows EC2 instance that is a member of the Directory Service directory. You must also be logged in as a user that has privileges to create users and groups. For more information, see [Add users and groups (Simple AD and AWS Managed Microsoft AD)](https://docs.aws.amazon.com/directoryservice/latest/admin-guide/creating_ad_users_and_groups.html) in the _AWS Directory Service Administration Guide_. @@ -249 +249 @@ If a different AWS account owns the directory, you must share the directory. - 1. Start sharing the directory with the AWS account that the DB instance will be created in by following the instructions in [Tutorial: Sharing your AWS Managed Microsoft AD directory for seamless EC2 domain-join](https://docs.aws.amazon.com/directoryservice/latest/admin-guide/ms_ad_tutorial_directory_sharing.html) in the _AWS Directory Service Administration Guide_. + 1. Start sharing the directory with the AWS account that the DB instance will be created in by following the instructions in [Tutorial: Sharing your AWS Managed Microsoft AD directory for seamless EC2 domain-join](https://docs.aws.amazon.com/directoryservice/latest/admin-guide/ms_ad_tutorial_directory_sharing.html) in the _Directory Service Administration Guide_. @@ -251 +251 @@ If a different AWS account owns the directory, you must share the directory. - 2. Sign in to the AWS Directory Service console using the account for the DB instance, and ensure that the domain has the `SHARED` status before proceeding. + 2. Sign in to the Directory Service console using the account for the DB instance, and ensure that the domain has the `SHARED` status before proceeding. @@ -253 +253 @@ If a different AWS account owns the directory, you must share the directory. - 3. While signed into the AWS Directory Service console using the account for the DB instance, note the **Directory ID** value. You use this directory ID to join the DB instance to the domain. + 3. While signed into the Directory Service console using the account for the DB instance, note the **Directory ID** value. You use this directory ID to join the DB instance to the domain.