AWS AmazonRDS documentation change
Summary
Updated terminology from 'AWS Directory Service' to 'Directory Service' throughout the document, including console references and service interactions.
Security assessment
Changes are purely terminological updates (branding simplification) without modifying security configurations, Kerberos setup procedures, trust relationships, or IAM permissions. No vulnerabilities or security improvements are addressed.
Diff
diff --git a/AmazonRDS/latest/AuroraUserGuide/aurora-mysql-kerberos-setting-up.md b/AmazonRDS/latest/AuroraUserGuide/aurora-mysql-kerberos-setting-up.md index 7a7af0f81..f7c9bf6ac 100644 --- a//AmazonRDS/latest/AuroraUserGuide/aurora-mysql-kerberos-setting-up.md +++ b//AmazonRDS/latest/AuroraUserGuide/aurora-mysql-kerberos-setting-up.md @@ -34 +34 @@ Use AWS Managed Microsoft AD to set up Kerberos authentication for an Aurora MyS -AWS Directory Service creates a fully managed 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 System (DNS) servers on your behalf. The directory servers are created in different subnets in a VPC. This redundancy helps make sure that your directory remains accessible even if a failure occurs. +Directory Service creates a fully managed Active Directory in the AWS Cloud. When you create an AWS Managed Microsoft AD directory, Directory Service creates two domain controllers and Domain Name System (DNS) servers on your behalf. The directory servers are created in different subnets in a VPC. This redundancy helps make sure that your directory remains accessible even if a failure occurs. @@ -36 +36 @@ AWS Directory Service creates a fully managed Active Directory in the AWS Cloud. -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: @@ -44 +44 @@ When you create an AWS Managed Microsoft AD directory, AWS Directory Service per -Be sure to save this password. AWS Directory Service doesn't store it. You can reset it, but you can't retrieve it. +Be sure to save this password. Directory Service doesn't store it. You can reset it, but you can't retrieve it. @@ -83 +83 @@ The `Admin` account also has rights to perform the following domain-wide activit - 1. Sign in to the AWS Management Console and open the AWS Directory Service console at [https://console.aws.amazon.com/directoryservicev2/](https://console.aws.amazon.com/directoryservicev2/). + 1. Sign in to the AWS Management Console and open the Directory Service console at [https://console.aws.amazon.com/directoryservicev2/](https://console.aws.amazon.com/directoryservicev2/). @@ -157 +157 @@ If you don't plan to use your own on-premises Microsoft Active Directory, skip t -To use Kerberos authentication with your on-premises Active Directory, you need to create a trusting domain relationship using a forest trust between your on-premises Microsoft Active Directory and the AWS Managed Microsoft AD directory (created in Step 1: Create a directory using AWS Managed Microsoft AD). The trust can be one-way, where the AWS Managed Microsoft AD directory trusts the on-premises Microsoft Active Directory. The trust can also be two-way, where both Active Directories trust each other. For more information about setting up trusts using AWS Directory Service, see [When to create a trust relationship](https://docs.aws.amazon.com/directoryservice/latest/admin-guide/ms_ad_setup_trust.html) in the _AWS Directory Service Administration Guide_. +To use Kerberos authentication with your on-premises Active Directory, you need to create a trusting domain relationship using a forest trust between your on-premises Microsoft Active Directory and the AWS Managed Microsoft AD directory (created in Step 1: Create a directory using AWS Managed Microsoft AD). The trust can be one-way, where the AWS Managed Microsoft AD directory trusts the on-premises Microsoft Active Directory. The trust can also be two-way, where both Active Directories trust each other. For more information about setting up trusts using Directory Service, see [When to create a trust relationship](https://docs.aws.amazon.com/directoryservice/latest/admin-guide/ms_ad_setup_trust.html) in the _AWS Directory Service Administration Guide_. @@ -180 +180 @@ Make sure that your on-premises Microsoft Active Directory domain name includes -For Amazon Aurora to call AWS Directory Service for you, you need an AWS Identity and Access Management (IAM) role that uses the managed IAM policy `AmazonRDSDirectoryServiceAccess`. This role allows Aurora to make calls to the AWS Directory Service. +For Amazon Aurora to call Directory Service for you, you need an AWS Identity and Access Management (IAM) role that uses the managed IAM policy `AmazonRDSDirectoryServiceAccess`. This role allows Aurora to make calls to the Directory Service. @@ -243 +243 @@ You can create users with the Active Directory Users and Computers tool. This to -To create users in an AWS Directory Service directory, you use an on-premises or Amazon EC2 instance based on Microsoft Windows that is joined to your AWS Directory Service directory. You must be logged in to the instance as a user that has privileges to create users. For more information, see [Manage users and groups in 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 in an Directory Service directory, you use an on-premises or Amazon EC2 instance based on Microsoft Windows that is joined to your Directory Service directory. You must be logged in to the instance as a user that has privileges to create users. For more information, see [Manage users and groups in 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_. @@ -343 +343 @@ To configure a MySQL client, take the following steps: - 2. Verify that traffic can flow between the client host and AWS Directory Service. Use a network utility such as Netcat, for the following: + 2. Verify that traffic can flow between the client host and Directory Service. Use a network utility such as Netcat, for the following: @@ -347 +347 @@ To configure a MySQL client, take the following steps: - * Verify traffic over TCP/UDP for port 53 and for Kerberos, which includes ports 88 and 464 for AWS Directory Service. + * Verify traffic over TCP/UDP for port 53 and for Kerberos, which includes ports 88 and 464 for Directory Service.