Hybrid directory prerequisites
Hybrid directory extends your self-managed Active Directory to the Amazon Web Services Cloud. Before creating a hybrid directory, ensure your environment meets these requirements:
Microsoft Active Directory domain requirements
Before creating a hybrid directory, ensure your self-managed AD environment and infrastructure meet the following requirements, and gather the necessary information.
Domain requirements
Your self-managed AD environment must meet the following requirements:
-
Uses a Windows Server 2012 R2 or 2016 functional level.
-
Uses standard domain controllers to be assessed for hybrid directory creation. Read-only domain controllers (RODC) can not be used for hybrid directory creation.
-
Has two domain controllers with all Active Directory services running.
-
The Primary Domain Controller (PDC) must be routable at all times.
Specifically, the PDC Emulator and RID Master IPs of your self-managed AD must be in one of these categories:
-
Part of RFC1918 private IP address ranges (10.0.0.0/8, 172.16.0.0/12, or 192.168.0.0/16)
-
Within your VPC CIDR range
-
Match the DNS IPs of your self-managed instances for the directory
You can add additional IP routes for the directory after the hybrid directory is created.
-
Required information
Gather the following information about your self-managed AD:
-
Directory DNS name
-
Directory DNS IPs
-
Service account credentials with Administrator permissions to your self-managed AD
-
Amazon Secret ARN for storing your service account credentials (see Amazon Secret ARN for hybrid directory)
Amazon Secret ARN for hybrid directory
To configure a hybrid directory with your self-managed AD, you need to create a KMS key to encrypt your Amazon secret and then create the secret itself. Both resources must be created in the same Amazon Web Services account that contains the hybrid directory.
Create a KMS key
The KMS key is used to encrypt your Amazon secret.
Important
For Encryption Key, don't use the Amazon default KMS key. Be sure to create the Amazon KMS key in the same Amazon Web Services account that contains the hybrid directory you want to create to join with your self-managed AD.
To create an Amazon KMS key
-
In the Amazon KMS console, choose Create key.
-
For Key Type, choose Symmetric.
-
For Key Usage, choose Encrypt and decrypt.
-
For Advanced options:
-
For Key material origin, choose KMS.
-
For Regionality, choose Single-Region key and choose Next.
-
-
For Alias, provide a name for the KMS key.
-
(Optional) For Description, provide a description of the KMS key.
-
(Optional) For Tags, add tags for the KMS key and choose Next.
-
For Key administrators, select an IAM user.
-
For Key deletion, keep the default selection for Allow key administrators to delete this key and choose Next.
-
For Key users, select the same IAM user from the previous step and choose Next.
-
Review the configuration.
-
For Key policy, add the following statement to the policy:
{ "Version": "2012-10-17", "Statement": [ { "Sid": "Enable IAM User Permissions", "Effect": "Allow", "Principal": { "AWS": "arn:aws:iam::
caller-account
:role/role_used_to_create_directory
" }, "Action": "kms:*", "Resource": "*" }, { "Sid": "Allow use of the KMS key on behalf of Directory Service", "Effect": "Allow", "Principal": { "Service": "ds.amazonaws.com" }, "Action": "kms:Decrypt", "Resource": "*" } ] } -
Choose Finish.
Create an Amazon secret
Create a secret in Secrets Manager to store the credentials for your self-managed AD user account.
Important
Create the secret in the same Amazon Web Services account that contains the hybrid directory you want to join with your self-managed AD.
To create a secret
In Secrets Manager, choose Store a new secret
For Secret type, choose Other type of secret
For Key/value pairs, add your two keys:
-
Add the username key
-
For the first key, enter
customerAdAdminDomainUsername
. -
For the value of the first key, enter only the username (without the domain prefix) of the AD user. Do not include the domain name as this causes instance creation to fail.
-
-
Add the password key
-
For the second key, enter
customerAdAdminDomainPassword
. -
For the value of the second key, enter the password that you created for the AD user on your domain.
-
Complete the secret configuration
-
For Encryption key, select the KMS key that you created in Create a KMS key and choose Next.
-
For Secret name, enter a description for the secret.
-
(Optional) For Description, enter a description for the secret.
-
Choose Next.
-
For Configure rotation settings, keep the default values and choose Next.
-
Review the settings for the secret and choose Store.
-
Choose the secret you created and copy the value for the Secret ARN. You will use this ARN in the next step to set up your self-managed Active Directory.
Infrastructure requirements
Prepare the following infrastructure components:
-
Two Amazon Systems Manager nodes with administrator privileges for SSM agents
-
If your Active Directory is self-managed outside of the Amazon Web Services Cloud, you will need two Systems Manager node for a hybrid and multicloud environment. For more information on how to provision these nodes, see Setting up Systems Manager for hybrid and multicloud environments
. -
If your Active Directory is self-managed within the Amazon Web Services Cloud, you will need two Systems Manager managed EC2 instances. For more information on how to provision these instances, see Managing EC2 instances with Systems Manager
.
-
Required Active Directory services
Ensure the following services are running on your self-managed AD:
-
Active Directory Domain Services
-
Active Directory Web Service (ADWS)
-
COM+ Event System
-
Distributed File System Replication (DFSR)
-
Domain Name System (DNS)
-
DNS Server
-
Group Policy Client
-
Intersite Messaging
-
Remote Procedure Call (RPC)
-
Security Accounts Manager
-
Windows Time Server
Note
Hybrid directory requires both the UDP port 123 to be open and the Windows Time Server to be enabled and functional. We synchronize time with your domain controller to ensure hybrid directory replication works properly.
Kerberos authentication requirements
Your user accounts must have Kerberos preauthentication enabled. For detailed
instructions on how to enable this setting, see Ensure that Kerberos pre-authentication is enabled
Supported encryption types
hybrid directory supports the following encryption types when authenticating via Kerberos to your Active Directory domain controllers:
-
AES-256-HMAC
Network port requirements
For Amazon to extend your self-managed Active Directory domain controllers, the firewall for your existing network must have the following ports open to the CIDRs for both subnets in your Amazon VPC:
-
TCP/UDP 53 - DNS
-
TCP/UDP 88 - Kerberos authentication
-
UDP 123 - Time server
-
TCP 135 - Remote Procedure Call
-
TCP/UDP 389 - LDAP
-
TCP 445 - SMB
-
TCP 636 - Only needed for environments with Lightweight Directory Access Protocol Secure (LDAPS)
-
TCP 49152-65535 - RPC randomly allocated high TCP ports
-
TCP 3268 and 3269 - Global Catalog
-
TCP 9389 Active Directory Web Services (ADWS)
These are the minimum ports needed to create a hybrid directory. Your specific configuration may require additional ports be open.
Note
The DNS IPs provided for your Domain Controllers and FSMO Role holders must have the above ports open to the CIDRs for both subnets in the Amazon VPC.
Note
Hybrid directory requires both the UDP port 123 to be open and the Windows Time Server to be enabled and functional. We synchronize time with your domain controller to ensure hybrid directory replication works properly.
Amazon Web Services account permissions
You will need permissions to the following actions in your Amazon Web Services account:
-
ec2:AuthorizeSecurityGroupEgress
-
ec2:AuthorizeSecurityGroupIngress
-
ec2:CreateNetworkInterface
-
ec2:CreateSecurityGroup
-
ec2:DescribeNetworkInterfaces
-
ec2:DescribeSubnets
-
ec2:DescribeVpcs
-
ec2:CreateTags
-
ec2:CreateNetworkInterfacePermission
-
ssm:ListCommands
-
ssm:GetCommandInvocation
-
ssm:GetConnectionStatus
-
ssm:SendCommand
-
secretsmanager:DescribeSecret
-
secretsmanager:GetSecretValue
-
iam:GetRole
-
iam:CreateServiceLinkedRole
Amazon VPC network requirements
A VPC with the following:
-
At least two subnets. Each of the subnets must be in a different Availability Zone
-
The VPC must have default tenancy
You cannot create a hybrid directory in a VPC using addresses in the 198.18.0.0/15 address space.
Amazon Directory Service uses a two VPC structure. The EC2 instances which make up your directory run
outside of your Amazon Web Services account, and are managed by Amazon. They have two network adapters,
ETH0
and ETH1
. ETH0
is the management
adapter, and exists outside of your account. ETH1
is created within your
account.
The management IP range of the ETH0 network for your directory is 198.18.0.0/15
.
For more information, see the following topics in the Amazon VPC User Guide:
For more information about Amazon Direct Connect, see the What
is Amazon Direct Connect?
Amazon security group configuration
By default, Amazon attaches a security group to allow network access to the Amazon Systems Manager managed nodes in your VPC. You can optionally supply your own security group that allows network traffic to and from your self-managed domain controllers outside of your VPC.
You can optionally supply your own security group that allows network traffic to and from your self-managed domain controllers outside of your VPC. If you are supply your own security group, then you need to:
-
Allowlist your VPC CIDR ranges and self-managed ranges.
-
Ensure these ranges don't overlap with Amazon reserved IP ranges
Directory assessments considerations
The following are considerations when creating directory assessments and the number of assessments you can have in your Amazon Web Services account:
-
A directory assessment is automatically created when you create a hybrid directory. There are two types of assessments:
CUSTOMER
andSYSTEM
. Your Amazon Web Services account has a limit of 100CUSTOMER
directory assessments. -
If you attempt to create a hybrid directory and you already have 100
CUSTOMER
directory assessments, you will encounter an error. Delete assessments to free up capacity before trying again. -
You can request an increase to your
CUSTOMER
directory assessment quota by contacting Amazon Web Services Support or delete existing CUSTOMER directory assessments to free up capacity.