AWS Security ChangesHomeSearch

AWS AmazonRDS: Rename AWS Managed Microsoft AD to AWS Managed Active Directory in Oracle Kerberos setup

Service: AmazonRDS · 2026-11-06 · Documentation low

File: AmazonRDS/latest/UserGuide/oracle-kerberos-setting-up.md

Summary

Terminology and structural update to the RDS for Oracle Kerberos setup guide: 'AWS Managed Microsoft AD' is renamed to 'AWS Managed Active Directory' throughout, the standalone 'Step 2: Create a trust' section is removed, and the remaining steps are renumbered (8 steps down to 7). A pointer to the self-managed AD (oracle-smad) page is added for direct domain joins.

Security assessment

The diff is a product-name rename plus step renumbering and removal of the forest-trust step; the security-relevant content (IAM permissions, security group inbound rules, cross-VPC traffic, Kerberos logins) is carried over unchanged in substance. No specific vulnerability, CVE, or incident is referenced, and no new security feature or best practice is introduced, so this is a low-severity editorial change.

Evidence

+  3. Choose **AWS Managed Active Directory**. To join your DB instance directly to a self-managed AD domain instead, see [Working with self-managed Active Directory with an Amazon RDS for Oracle DB instance](./oracle-smad.html).

Diff

diff --git a/AmazonRDS/latest/UserGuide/oracle-kerberos-setting-up.md b/AmazonRDS/latest/UserGuide/oracle-kerberos-setting-up.md
index 1cae51a..8a13a36 100644
--- a//AmazonRDS/latest/UserGuide/oracle-kerberos-setting-up.md
+++ b//AmazonRDS/latest/UserGuide/oracle-kerberos-setting-up.md
@@ -7 +7 @@
-Step 1: Create a directory using the AWS Managed Microsoft ADStep 2: Create a trustStep 3: Configure IAM permissionsStep 4: Create and configure usersStep 5: Enable cross-VPC trafficStep 6: Create or modify an Oracle DB instanceStep 7: Create Kerberos authentication Oracle loginsStep 8: Configure an Oracle client
+Step 1: Create a directory using the AWS Managed Active DirectoryStep 2: Configure IAM permissionsStep 3: Create and configure usersStep 4: Enable cross-VPC trafficStep 5: Create or modify an Oracle DB instanceStep 6: Create Kerberos authentication Oracle loginsStep 7: Configure an Oracle client
@@ -9 +9 @@ Step 1: Create a directory using the AWS Managed Microsoft ADStep 2: Create a tr
-# Setting up Kerberos for Oracle DB instances
+# Setting up AWS Managed Active Directory
@@ -11 +11 @@ Step 1: Create a directory using the AWS Managed Microsoft ADStep 2: Create a tr
-Use AWS Directory Service for Microsoft Active Directory, also called AWS Managed Microsoft AD, to set up Kerberos authentication for an Oracle DB instance. To set up Kerberos authentication, complete the following steps:
+Use AWS Managed Active Directory to set up Kerberos authentication for an Oracle DB instance. To set up Kerberos authentication, complete the following steps:
@@ -13 +13 @@ Use AWS Directory Service for Microsoft Active Directory, also called AWS Manage
-  * Step 1: Create a directory using the AWS Managed Microsoft AD
+  * Step 1: Create a directory using the AWS Managed Active Directory
@@ -15 +15 @@ Use AWS Directory Service for Microsoft Active Directory, also called AWS Manage
-  * Step 2: Create a trust
+  * Step 2: Configure IAM permissions for Amazon RDS
@@ -17 +17 @@ Use AWS Directory Service for Microsoft Active Directory, also called AWS Manage
-  * Step 3: Configure IAM permissions for Amazon RDS
+  * Step 3: Create and configure users
@@ -19 +19 @@ Use AWS Directory Service for Microsoft Active Directory, also called AWS Manage
-  * Step 4: Create and configure users
+  * Step 4: Enable cross-VPC traffic between the directory and the DB instance
@@ -21 +21 @@ Use AWS Directory Service for Microsoft Active Directory, also called AWS Manage
-  * Step 5: Enable cross-VPC traffic between the directory and the DB instance
+  * Step 5: Create or modify an Oracle DB instance
@@ -23 +23 @@ Use AWS Directory Service for Microsoft Active Directory, also called AWS Manage
-  * Step 6: Create or modify an Oracle DB instance
+  * Step 6: Create Kerberos authentication Oracle logins
@@ -25,3 +25 @@ Use AWS Directory Service for Microsoft Active Directory, also called AWS Manage
-  * Step 7: Create Kerberos authentication Oracle logins
-
-  * Step 8: Configure an Oracle client
+  * Step 7: Configure an Oracle client
@@ -36 +34 @@ During the setup, RDS creates an Oracle database user named `managed_service_use
-## Step 1: Create a directory using the AWS Managed Microsoft AD
+## Step 1: Create a directory using the AWS Managed Active Directory
@@ -38 +36 @@ During the setup, RDS creates an Oracle database user named `managed_service_use
-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. 
+Directory Service creates a fully managed Active Directory in the AWS Cloud. When you create an AWS Managed Active Directory 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. 
@@ -40 +38 @@ Directory Service creates a fully managed Active Directory in the AWS Cloud. Whe
-When you create an AWS Managed Microsoft AD directory, Directory Service performs the following tasks on your behalf: 
+When you create an AWS Managed Active Directory directory, Directory Service performs the following tasks on your behalf: 
@@ -55 +53 @@ Be sure to save this password. Directory Service doesn't store it. You can reset
-When you launch an AWS Managed Microsoft AD, AWS creates an Organizational Unit (OU) that contains all of your directory's objects. This OU has the NetBIOS name that you typed when you created your directory and is located in the domain root. The domain root is owned and managed by AWS. 
+When you launch an AWS Managed Active Directory, AWS creates an Organizational Unit (OU) that contains all of your directory's objects. This OU has the NetBIOS name that you typed when you created your directory and is located in the domain root. The domain root is owned and managed by AWS. 
@@ -57 +55 @@ When you launch an AWS Managed Microsoft AD, AWS creates an Organizational Unit
-The Admin account that was created with your AWS Managed Microsoft AD directory has permissions for the most common administrative activities for your OU: 
+The Admin account that was created with your AWS Managed Active Directory directory has permissions for the most common administrative activities for your OU: 
@@ -87 +85 @@ To create the directory, use the AWS Management Console, the AWS CLI, or the Dir
-###### To create a directory with AWS Managed Microsoft AD
+###### To create a directory with AWS Managed Active Directory
@@ -93 +91 @@ To create the directory, use the AWS Management Console, the AWS CLI, or the Dir
-  3. Choose **AWS Managed Microsoft AD**. AWS Managed Microsoft AD is the only option that you can currently use with Amazon RDS. 
+  3. Choose **AWS Managed Active Directory**. To join your DB instance directly to a self-managed AD domain instead, see [Working with self-managed Active Directory with an Amazon RDS for Oracle DB instance](./oracle-smad.html).
@@ -159,7 +157 @@ To see information about your directory, choose the directory name in the direct
-## Step 2: Create a trust
-
-If you plan to use AWS Managed Microsoft AD only, move on to Step 3: Configure IAM permissions for Amazon RDS.
-
-To enable Kerberos authentication using your self-managed Active Directory, you must create a forest trust relationship between your self-managed Active Directory and the AWS Managed Microsoft AD created in the previous step. The trust can be one-way, where the AWS Managed Microsoft AD trusts the self-managed Active Directory. The trust can also be two-way, where both Active Directories trust each other. For more information about setting up forest 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 _Directory Service Administration Guide_.
-
-## Step 3: Configure IAM permissions for Amazon RDS
+## Step 2: Configure IAM permissions for Amazon RDS
@@ -286 +278 @@ JSON
-## Step 4: Create and configure users
+## Step 3: Create and configure users
@@ -290 +282 @@ You can create users with the Active Directory Users and Computers tool, which i
-To create users in an Directory Service directory, you must be connected to a Windows-based Amazon EC2 instance that is a member of the Directory Service directory. At the same time, you must be logged in as a user that has privileges to create users. For more information about creating users in your Microsoft Active Directory, see [Manage users and groups in AWS Managed Microsoft AD](https://docs.aws.amazon.com/directoryservice/latest/admin-guide/ms_ad_manage_users_groups.html) in the _Directory Service Administration Guide_.
+To create users in an Directory Service directory, you must be connected to a Windows-based Amazon EC2 instance that is a member of the Directory Service directory. At the same time, you must be logged in as a user that has privileges to create users. For more information about creating users in your Active Directory, see [Manage users and groups in AWS Managed Active Directory](https://docs.aws.amazon.com/directoryservice/latest/admin-guide/ms_ad_manage_users_groups.html) in the _Directory Service Administration Guide_.
@@ -292 +284 @@ To create users in an Directory Service directory, you must be connected to a Wi
-## Step 5: Enable cross-VPC traffic between the directory and the DB instance
+## Step 4: Enable cross-VPC traffic between the directory and the DB instance
@@ -294 +286 @@ To create users in an Directory Service directory, you must be connected to a Wi
-If you plan to locate the directory and the DB instance in the same VPC, skip this step and move on to Step 6: Create or modify an Oracle DB instance.
+If you plan to locate the directory and the DB instance in the same VPC, skip this step and move on to Step 5: Create or modify an Oracle DB instance.
@@ -302 +294 @@ If you plan to locate the directory and the DB instance in different AWS account
-  2. Ensure that the DB instance's security group can receive inbound traffic from the directory's security group. For more information, see [ Best practices for AWS Managed Microsoft AD](https://docs.aws.amazon.com/directoryservice/latest/admin-guide/ms_ad_best_practices.html) in the _Directory Service Administration Guide_.
+  2. Ensure that the DB instance's security group can receive inbound traffic from the directory's security group. For more information, see [ Best practices for AWS Managed Active Directory](https://docs.aws.amazon.com/directoryservice/latest/admin-guide/ms_ad_best_practices.html) in the _Directory Service Administration Guide_.
@@ -313 +305 @@ 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 _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 Active Directory 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_.
@@ -322 +314 @@ If a different AWS account owns the directory, you must share the directory.
-## Step 6: Create or modify an Oracle DB instance
+## Step 5: Create or modify an Oracle DB instance
@@ -406 +398 @@ Confirm that `Status` shows `joined`. If it shows `failed`, verify that the secu
-## Step 7: Create Kerberos authentication Oracle logins
+## Step 6: Create Kerberos authentication Oracle logins
@@ -408 +400 @@ Confirm that `Status` shows `joined`. If it shows `failed`, verify that the secu
-Use the Amazon RDS master user credentials to connect to the Oracle DB instance as you do any other DB instance. The DB instance is joined to the AWS Managed Microsoft AD domain. Thus, you can provision Oracle logins and users from the Microsoft Active Directory users in your domain. To manage database permissions, you grant and revoke standard Oracle permissions to these logins.
+Use the Amazon RDS master user credentials to connect to the Oracle DB instance as you do any other DB instance. The DB instance is joined to the AWS Managed Active Directory domain. Thus, you can provision Oracle logins and users from the Active Directory users in your domain. To manage database permissions, you grant and revoke standard Oracle permissions to these logins.
@@ -410 +402 @@ Use the Amazon RDS master user credentials to connect to the Oracle DB instance
-###### To allow a Microsoft Active Directory user to authenticate with Oracle
+###### To allow a Active Directory user to authenticate with Oracle
@@ -426 +418 @@ Users (both humans and applications) from your domain can now connect to the Ora
-## Step 8: Configure an Oracle client
+## Step 7: Configure an Oracle client
@@ -439 +431 @@ To configure an Oracle client, meet the following requirements:
-Following is sample content for AWS Managed Microsoft AD.
+Following is sample content for AWS Managed Active Directory.
@@ -453 +445 @@ Following is sample content for AWS Managed Microsoft AD.
-Following is sample content for on-premise Microsoft AD. In your krb5.conf or krb5.ini file, replace `on-prem-ad-server-name` with the name of your on-premises AD server.
+Following is sample content for on-premises Active Directory. In your krb5.conf or krb5.ini file, replace `on-prem-ad-server-name` with the name of your on-premises AD server.
@@ -491 +483 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please
-Region and version availability
+Region and version availability for AWS Managed Active Directory
@@ -493 +485 @@ Region and version availability
-Managing a DB instance
+Managing a DB instance for AWS Managed Active Directory