Extend on-premises Active Directory to an existing VPC - AWS Launch Wizard

Extend on-premises Active Directory to an existing VPC

The following steps guide you through an Active Directory deployment with AWS Launch Wizard after you have launched it from the console for an existing VPC.

  1. On the Launch Wizard console's landing page, use the Choose application button. This opens the Choose application wizard where you are prompted to select the type of application that you want to deploy.

  2. Select Active Directory, select Extend on-premises AD into an existing VPC, then select Create deployment.

  3. Review and acknowledge that the required IAM permissions are met before proceeding. For more information, see Identity and Access Management for AWS Launch Wizard.

  4. When prompted, enter the specifications for the new deployment. The following tabs provide information about the specification fields of the deployment model.

    General settings

    • Deployment name. Enter a unique application name for your deployment.

    • Amazon Simple Notification Service (Amazon SNS) topic ARN — optional. Specify an Amazon SNS topic where Launch Wizard can send notifications and alerts. For more information, see the Amazon Simple Notification Service Developer Guide.

    • Deactivate rollback on failed deployment. By default, if a deployment fails, your provisioned resources will be deleted. You can enable this setting during deployment to prevent this behavior.

    • Tags - optional. Enter a key and value to assign metadata to your deployment. For help with tagging, see Tagging Your Amazon EC2 Resources.

    Network configuration
    Parameter label (name) Default value Description
    Parameter label (name) Default value Description
    VPC CIDR (VPCCIDR) 10.0.0.0/16 CIDR Block for the VPC.
    VPC ID (VPCID) Requires input ID of the VPC (for example, vpc-abcd0123).
    Subnet 1 ID (Subnet1ID) Requires input ID of subnet 1 in Availability Zone 1 (for example, subnet-abcd0123).
    Subnet 2 ID (Subnet2ID) Requires input ID of subnet 2 in Availability Zone 2 (for example, subnet-01234abcd).
    Exiting domain controllers Security Group ID (ExistingDomainControllersSG) sg-1234567890abcdef0 Security Group ID for existing domain controllers Security Group. (Used only when JoinAndPromote equals Yes).
    Amazon EC2 configuration
    Parameter label (name) Default value Description
    Domain controller 1 NetBIOS name (ADServer1NetBIOSName) DC3 NetBIOS name of the first additional Active Directory domain controller (between 1-15 characters).
    Domain controller 1 private IP address (ADServer1PrivateIP) 10.0.0.11 Fixed private IP for the first additional Active Directory domain controller located in subnet 1.
    Domain controller 2 NetBIOS name (ADServer2NetBIOSName) DC4 NetBIOS name of the second additional Active Directory domain controller (between 1-15 characters).
    Domain controller 2 private IP address (ADServer2PrivateIP) 10.0.32.11 Fixed private IP for the second additional Active Directory domain controller located in subnet 2.
    SYSVOL and NTDS Data Drive Size (DataDriveSizeGiB) 10 Size of SYSVOL and NTDS data drive in GiB.
    KMS key for EBS Encryption (EbsEncryptionKmsKeyId) alias/aws/ebs The identifier of the KMS key to use for Amazon EBS encryption. You can specify the KMS key using any of the following; key ID, key alias, key ARN, alias ARN.
    Key pair name (KeyPairName) Requires input Public/private key pairs allow you to securely connect to your instance after it launches.
    AMI ID (LatestAmiId) /aws/service/ami-windows-latest/Windows_Server-2022-English-Full-Base AWS Systems Manager parameter value for latest Windows Server AMI.
    Microsoft Active Directory Domain Services configuration
    Parameter label (name) Default value Description
    Join and Promote to domain controllers (JoinAndPromote) No Do you want to join and promote these instances to be Active Directory domain controllers.
    DNS Server 1 IP address (ExistingDomainController1IP) 10.0.0.10

    The IP address of the first DNS server that can resolve the domain. You must have connectivity from the VPC to the DNS server.
    DNS Server 2 IP address (ExistingDomainController2IP) 10.0.32.10

    The IP address of the second DNS server that can resolve the domain. You must have connectivity from the VPC to the DNS server.
    Domain DNS name (DomainDNSName) example.com Fully qualified domain name (FQDN) of the domain you would like to join and promote to. For example, example.com.
    Domain NetBIOS name (DomainNetBIOSName) example NetBIOS name of the domain (between 1 to 15 characters) you would like to join and promote to for users of earlier versions of Windows. For example, EXAMPLE.

  5. When you are satisfied with your application settings, choose Next. If you don't want to complete the configuration, choose Cancel. When you choose Cancel, all of the selections on the specification page are lost and you are returned to the landing page. To return to the previous screen, choose Previous.

  6. On the Configure infrastructure settings page, you are prompted to define the infrastructure settings for the new deployment. The following tab provides information about the input fields.

    Storage and compute

    You can choose to select your instances, or to use AWS recommended resources. If you choose to use AWS recommended resources, you have the option of defining your performance needs. If you don't select either option, default values are assigned. Launch Wizard will display the estimated charges incurred to deploy the application based on suggested infrastructure and also based on static values.

    • Based on infrastructure suggestion. Launch Wizard displays the suggested resources for the deployment. You can specify your performance requirements of the resources to update the recommendation.

      • Number of instance cores. Choose the number of CPU cores for your infrastructure. The default value assigned is 4.

      • Network performance. Choose your preferred network performance in Gbps.

      • Memory (GB). Choose the amount of RAM that you want to attach to your EC2 instances. The default value assigned is 4 GB.

      • Recommended resources. Launch Wizard displays the system-recommended resources based on your infrastructure selections. If you want to change the recommended resources, select different infrastructure settings.

      • Estimated on-demand cost to deploy additional resources. Launch Wizard displays the estimated charges incurred to deploy the resources.

    • Based on static values. You can specify specific instance types for the resources used in your deployment. If you don't select either option, default values are assigned.

      • Instance type. You can choose your instance type from the dropdown list, or you can use AWS recommended resources.

      • Estimated on-demand cost to deploy additional resources. Launch Wizard displays the estimated charges incurred to deploy the resources.

  7. When you are satisfied with your infrastructure settings, select Next. If you don't want to complete the configuration, select Cancel. When you select Cancel, all of the selections on the specification page are lost and you are returned to the landing page. To go to the previous screen, select Previous.

  8. On the Review and deploy page, review your configuration details. If you want to make changes, select Previous. To stop, select Cancel. When you select Cancel, all of the selections on the specification page are lost and you are returned to the landing page. When you choose Deploy, you agree to the terms of the Acknowledgment. Launch Wizard validates the inputs and notifies you if you need to address any issues.

  9. When validation is complete, Launch Wizard deploys your AWS resources and configures your application. Launch Wizard provides you with status updates about the progress of the deployment on the Deployments page. From the Deployments page, you can view the list of current and previous deployments.

  10. When your deployment is ready, a notification informs you that your application is successfully deployed. If you have set up an Amazon SNS notification, you are also alerted through Amazon SNS. You can manage and access all of the resources related to your application by selecting the deployment, and then selecting Manage from the Actions dropdown list.

  11. When the application is deployed, you can access your EC2 instances through the Amazon EC2 console.