AWS announced on November 5, 2026 that Amazon RDS for Oracle DB instances can now join a customer's own Microsoft Active Directory domain directly. Domain users can then sign in to the database with Kerberos tickets, and the directory can live in your own data center, on Amazon EC2 instances or at another cloud vendor.
Until now, teams that wanted Kerberos logins on RDS for Oracle with their existing directory had to run AWS Managed Microsoft AD as a middle layer and build a trust between that domain and their own. Removing that extra directory cuts cost, setup time and one more system to patch and monitor.
What Changed
The new option, labelled Self-managed Microsoft Active Directory in the console, lets an RDS for Oracle instance register a service identity in your own domain. When a user presents a Kerberos ticket from your domain controllers, the database checks it against that registered service key.
- No AWS Managed Microsoft AD and no forest trust are required.
- Setup works through the AWS Management Console, the AWS CLI or the AWS SDKs.
- AWS charges nothing extra for the self-managed directory option.
- It is available in every commercial AWS Region that offers RDS for Oracle.
Kerberos is added on top of password logins rather than replacing them. The master user and any account created with a password keep working as before, which gives you a safe path for a gradual rollout.
Key Details and Limits
Authorization stays per user. Every directory account that needs access must have its own Oracle user created as externally identified, and directory groups are not translated into Oracle roles or schemas. Teams with many users will want a script to keep the database accounts in sync with the directory.
The domain controllers must accept AES128 or AES256 Kerberos encryption, since RC4 and DES are not supported. The directory needs a Windows Server 2008 R2 functional level at minimum, and the domain's fully qualified name cannot exceed 64 characters.
Domain membership is not carried over to copies. An instance built from a snapshot, a point-in-time restore or a read replica request must be given the domain settings again. If a replica sits in a different domain from its primary, logins after a switchover are checked against the replica's realm.
How the Setup Works
The AWS user guide describes a one-time preparation that you can reuse for every instance in the same account and Region. You create a dedicated organizational unit in AD and a service account allowed to manage user objects inside it.
That service account also needs read and write access to the servicePrincipalName and encryption-type attributes, which AWS grants with a short PowerShell script.
Next, you create a customer managed AWS KMS key and store the service account's user name and password in AWS Secrets Manager, encrypted with that key. The secret's resource policy must let the RDS service read it, and AWS recommends source account and source ARN conditions to block confused deputy abuse.
Finally, you launch a new DB instance or change an existing one with four domain values: the domain name, the OU path, the secret ARN and two DNS server addresses. The network must allow DNS, Kerberos, password change and LDAP traffic between your VPC and the domain controllers.
What It Means for Developers and DBAs
For shops that already run Oracle with central Windows logins on premises, this removes one of the bigger blockers to moving those databases to RDS. People and services can keep their single sign-on habits, and password sprawl in connection strings drops.
On the database side, each AD user maps to an Oracle account named after the full principal, in quotes, with the realm included. That account is marked as identified externally and then given the create session privilege.
If you are new to this, our guide on creating users and profiles in Oracle SQL covers the basics, and the article on ORA-01045 and the create session privilege explains the most common first-login error.
Plan for failure cases too. If the instance loses its route to the domain controllers, Kerberos logins stop until the link returns, and the status field can still show kerberos-enabled. Subscribe to RDS event notifications, and keep at least one admin account on password login so you are never locked out.
How to Get Started
Start by checking your domain's encryption settings and network routes between the VPC and the domain controllers, since those cause most join failures. Then follow the AWS setup steps for the OU, service account, KMS key and secret.
Test the join on a non-production instance first. If the join fails, the database stays online with password logins and RDS reports the reason in an event, so you can fix the configuration and retry. Clients need a krb5.conf or krb5.ini file pointing to your realm before they can connect.
Conclusion
Amazon RDS for Oracle can now join a self-managed Active Directory domain directly, so Kerberos sign-in no longer depends on AWS Managed Microsoft AD or a trust relationship. The feature is free and available in all commercial Regions.
The main trade-offs are per-user mapping with no group support and the need for a reliable network path to your domain controllers. For teams with an existing AD estate, it is a simpler way to bring central identity to Oracle on AWS.
Sources
- AWS What's New: Amazon RDS for Oracle now supports Kerberos authentication with self-managed Active Directory
- Amazon RDS User Guide: Working with self-managed Active Directory with an RDS for Oracle DB instance
- Amazon RDS User Guide: Requirements for self-managed Active Directory
- Amazon RDS User Guide: Setting up self-managed Active Directory
- Amazon RDS User Guide: Configuring a Kerberos client and connecting to your DB instance
See my articles more often when you search Google.
