Working with Microsoft Active Directory with RDS Custom for SQL Server
RDS Custom for SQL Server allows to join your instances to a Self-Managed Active Directory (AD) or AWS Managed Microsoft AD. This is regardless of where your AD is hosted, like an On-premises data center, Amazon EC2 or with any other cloud service providers.
For authentication of users and services, you can use NTLM or Kerberos authentication on your RDS Custom for SQL Server DB instance without using intermediary domains and forest trusts. When a user tries to authenticate on your RDS Custom for SQL Server DB instance with a self joined Active Directory, requests for authentication are forwarded to a self-managed AD or AWS Managed Microsoft AD that you specify.
In the following sections, you can find information about working with Self Managed Active Directory and AWS Managed Active Directory for RDS Custom for SQL Server.
Topics
- Region and version availability
- Configure Self-Managed or On-premise AD
- Configure Microsoft Active Directory using AWS Directory Service
- Network configuration port rules
- Network Validation
- Setting up Windows Authentication for RDS Custom for SQL Server instances
- Managing a DB instance in a Domain
- Understanding Domain membership
- Troubleshooting Active Directory
Region and version availability
RDS Custom for SQL Server supports both Self Managed AD and AWS Managed Microsoft AD using NTLM or Kerberos in all Regions where RDS Custom for SQL Server is supported. For more information, see Supported Regions and DB engines for RDS Custom.
