Amazon Relational Database Service (Amazon RDS) for Db2 now allows customers to directly join their RDS for Db2 DB instances to the domains of self-managed Microsoft Active Directory (AD). Self-managed AD can be on-premises, on AWS, or in another cloud. Customers use Kerberos as the authentication protocol to enable single sign-on for their database users. Previously, to use Kerberos authentication against a self-managed AD with their RDS for Db2 instances, customers were required to deploy AWS Managed Microsoft AD and establish a trust between the AWS managed domain and the self-managed domai
This update aligns with a continuous trend of cloud providers enhancing compatibility and control for enterprise customers, especially regarding identity and access management solutions like Active Directory.
This allows enterprises with existing Db2 infrastructure to more seamlessly integrate their database instances on AWS with their current identity management systems, simplifying operations and potentially reducing costs.
Customers can now directly connect Amazon RDS for Db2 to self-managed Active Directory domains, removing the previous requirement for an AWS Managed Microsoft AD instance and a trust relationship.
- · AWS enterprise customers using Db2
- · Organizations prioritizing self-managed identity solutions
- · DB2 users migrating to AWS RDS
- · AWS Managed Microsoft AD (for this specific use case)
Increased adoption of Amazon RDS for Db2 among enterprises with complex Active Directory setups.
Reduced operational overhead for IT teams managing hybrid cloud environments with Db2.
Potential for further integration capabilities with non-AWS identity providers to empower more diverse enterprise cloud strategies.
This signal links to a primary source. Continuum Brief monitors and indexes it as part of the live intelligence stream — we do not republish source content.
Read at AWS What's New