AWS Security ChangesHomeSearch

AWS AmazonRDS documentation change

Service: AmazonRDS · 2025-11-22 · Documentation low

File: AmazonRDS/latest/UserGuide/db2-kerberos.md

Summary

Updated references from 'AWS Directory Service' to 'Directory Service' throughout the document for terminology consistency

Security assessment

The changes are purely terminological updates to use the preferred service name 'Directory Service' instead of 'AWS Directory Service'. No security-related content was added, removed, or modified beyond naming conventions. The Kerberos authentication setup process and security implications remain unchanged.

Diff

diff --git a/AmazonRDS/latest/UserGuide/db2-kerberos.md b/AmazonRDS/latest/UserGuide/db2-kerberos.md
index 181c3ff81..93ad56587 100644
--- a//AmazonRDS/latest/UserGuide/db2-kerberos.md
+++ b//AmazonRDS/latest/UserGuide/db2-kerberos.md
@@ -9 +9 @@ Region and version availabilityOverview of Kerberos authentication for DB instan
-You can use Kerberos authentication to authenticate users when they connect to your Amazon RDS for Db2 DB instance. In this configuration, your DB instance works with AWS Directory Service for Microsoft Active Directory, also called AWS Managed Microsoft AD. You add the domain and other information of your AWS Managed Microsoft AD directory to your RDS for Db2 DB instance. When users authenticate with an RDS for Db2 DB instance joined to the trusting domain, authentication requests are forwarded to the AWS Managed Microsoft AD directory that you created with AWS Directory Service. 
+You can use Kerberos authentication to authenticate users when they connect to your Amazon RDS for Db2 DB instance. In this configuration, your DB instance works with AWS Directory Service for Microsoft Active Directory, also called AWS Managed Microsoft AD. You add the domain and other information of your AWS Managed Microsoft AD directory to your RDS for Db2 DB instance. When users authenticate with an RDS for Db2 DB instance joined to the trusting domain, authentication requests are forwarded to the AWS Managed Microsoft AD directory that you created with Directory Service. 
@@ -15 +15 @@ In addition, you can access credentials from your own on-premises Microsoft Acti
-For more information, see [What is AWS Directory Service?](https://docs.aws.amazon.com/directoryservice/latest/admin-guide/what_is.html) in the _AWS Directory Service Administration Guide_.
+For more information, see [What is Directory Service?](https://docs.aws.amazon.com/directoryservice/latest/admin-guide/what_is.html) in the _AWS Directory Service Administration Guide_.
@@ -40 +40 @@ To set up Kerberos authentication for an RDS for Db2 DB instance, complete the f
-  1. Use AWS Managed Microsoft AD to create an AWS Managed Microsoft AD directory. You can use the AWS Management Console, the AWS Command Line Interface (AWS CLI), or AWS Directory Service to create the directory. For more information, see [Create your AWS Managed Microsoft AD directory](https://docs.aws.amazon.com/directoryservice/latest/admin-guide/ms_ad_getting_started_create_directory.html) in the _AWS Directory Service Administration Guide_. 
+  1. Use AWS Managed Microsoft AD to create an AWS Managed Microsoft AD directory. You can use the AWS Management Console, the AWS Command Line Interface (AWS CLI), or Directory Service to create the directory. For more information, see [Create your AWS Managed Microsoft AD directory](https://docs.aws.amazon.com/directoryservice/latest/admin-guide/ms_ad_getting_started_create_directory.html) in the _AWS Directory Service Administration Guide_. 
@@ -64 +64 @@ You can locate the DB instance in the same Amazon Virtual Private Cloud (VPC) as
-  4. Configure your Db2 client, and verify that traffic can flow between the client host and AWS Directory Service for the following ports:
+  4. Configure your Db2 client, and verify that traffic can flow between the client host and Directory Service for the following ports: