Menu
Amazon WorkSpaces
Administration Guide

Launch a WorkSpace Using AD Connector

Amazon WorkSpaces enables you to provision virtual, cloud-based Microsoft Windows desktops for your users, known as WorkSpaces.

Amazon WorkSpaces uses directories to store and manage information for your WorkSpaces and users. For your directory, you can choose from Simple AD, AD Connector, or AWS Directory Service for Microsoft Active Directory (Enterprise Edition), also known as Microsoft AD. In addition, you can establish a trust relationship between your Microsoft AD directory and your on-premises domain.

In this tutorial, we launch a WorkSpace that uses AD Connector. For tutorials that use the other options, see Launch a Virtual Desktop Using Amazon WorkSpaces.

Before You Begin

  • Amazon WorkSpaces is not available in every region. Verify the supported regions and select a region for your WorkSpaces. For more information about the supported regions, see Amazon WorkSpaces Pricing by AWS Region.

  • When you launch a WorkSpace, you must select a WorkSpace bundle. A bundle is a combination of storage, compute, and software resources. For more information, see Amazon WorkSpaces Bundles.

  • Create a virtual private cloud with at least two private subnets. The VPC must be connected to your on-premises network through a virtual private network (VPN) connection or AWS Direct Connect. For more information, see AD Connector Prerequisites in the AWS Directory Service Administration Guide.

  • Provide access to the Internet from the WorkSpace. For more information, see Provide Internet Access from Your WorkSpace.

Step 1: Create an AD Connector

To create an AD connector

  1. Open the Amazon WorkSpaces console at https://console.aws.amazon.com/workspaces/.

  2. In the navigation pane, choose Directories.

  3. Choose Set up Directory, Create AD Connector.

  4. For Organization name, type a unique organization name for your directory (for example, my-example-directory). This name must be at least four characters in length, consist of only alphanumeric characters and hyphens (-), and begin or end with a character other than a hyphen.

  5. For Connected directory DNS, type the fully-qualified name of your on-premises directory (for example, example.com).

  6. For Connected directory NetBIOS name, type the short name of your on-premises directory (for example, example).

  7. For Connector account username, type the user name of a user in your on-premises directory. The user must have permissions to read users and groups, create computer objects, and join computers to the domain.

  8. For Connector account password and Confirm password, type the password for the on-premises user account.

  9. For DNS address, type the IP address of at least one DNS server in your on-premises directory.

  10. (Optional) For Description, type a description for the directory.

  11. Keep Size as Small.

  12. For VPC, select your VPC.

  13. For Subnets, select your subnets. The DNS servers that you specified must be accessible from each subnet.

  14. Choose Next Step.

  15. Choose Create AD Connector. It takes several minutes for your directory to be connected. The initial status of the directory is Requested and then Creating. When directory creation is complete, the status is Active.

Step 2: Create a WorkSpace

Now you are ready to launch WorkSpaces for one or more users in your on-premises directory.

To launch a WorkSpace for an existing user

  1. Open the Amazon WorkSpaces console at https://console.aws.amazon.com/workspaces/.

  2. In the navigation pane, choose WorkSpaces.

  3. Choose Launch WorkSpaces.

  4. For Directory, choose the directory that you created.

  5. (Optional) If this is the first time you have launched a WorkSpace in this directory, and Amazon WorkDocs is supported in the region, you can enable or disable Amazon WorkDocs for all users in the directory. For more information, see Amazon WorkDocs Sync Client Help in the Amazon WorkDocs Administration Guide.

  6. Choose Next. Amazon WorkSpaces registers your AD Connector.

  7. Select one or more existing users from your on-premises directory. Do not add new users to an on-premises directory through the Amazon WorkSpaces console.

    To find users to select, you can type all or part of the user's name and choose Search or choose Show All Users. Note that you cannot select a user that does not have an email address.

    After you select the users, choose Add Selected and then choose Next Step.

  8. Under Select Bundle, choose the default WorkSpace bundle to be used for the WorkSpaces. Under Assign WorkSpace Bundles, you can choose a different the bundle for an individual WorkSpace if needed. When you have finished, choose Next Step.

  9. Choose a running mode for your WorkSpaces and then choose Next Step. For more information, see Manage the WorkSpace Running Mode.

  10. Choose Launch WorkSpaces. The initial status of the WorkSpace is PENDING. When the launch is complete, the status is AVAILABLE.

  11. Send invitations to the email address for each user. For more information, see Send an Invitation Email.

Step 3: Connect to the WorkSpace

You can connect to your WorkSpace using the client of your choice. After you sign in, the client displays the WorkSpace desktop.

To connect to the WorkSpace

  1. Open the link in the invitation email.

  2. When prompted, download one of the client applications or launch Web Access.

    If you aren't prompted and you haven't installed a client application already, open http://clients.amazonworkspaces.com/ and follow the directions.

  3. Start the client, enter the registration code from the invitation email, and choose Register.

  4. When prompted to sign in, type the username and password for the user, and then choose Sign In.

  5. (Optional) When prompted to save your credentials, choose Yes.

Next Steps

You can continue to customize the WorkSpace that you just created. For example, you can install software and then create a custom bundle from your WorkSpace. If you are finished with your WorkSpace, you can delete it. For more information, see the following documentation.