Access Amazon WorkSpaces Thin Client by using an interface endpoint (AWS PrivateLink)

You can use AWS PrivateLink to create a private connection between your VPC and Amazon WorkSpaces Thin Client. You can access WorkSpaces Thin Client as a VPC, without the use of an internet gateway, NAT device, VPN connection, or AWS Direct Connect connection. Instances in your VPC don't require public IP addresses to access WorkSpaces Thin Client.

You establish this private connection by creating an interface endpoint that's powered by AWS PrivateLink. We create an endpoint network interface in each subnet that you enable for the interface endpoint. These are requester-managed network interfaces that serve as the entry point for traffic destined for WorkSpaces Thin Client.

For more information, see Access AWS services through AWS PrivateLink in the AWS PrivateLink Guide.

Considerations for WorkSpaces Thin Client

Before you set up an interface endpoint for WorkSpaces Thin Client, review Considerations in the AWS PrivateLink Guide.

WorkSpaces Thin Client supports making calls to all of its API actions through the interface endpoint.

Create an interface endpoint for WorkSpaces Thin Client

You can create an interface endpoint for WorkSpaces Thin Client by using either the Amazon VPC console or the AWS Command Line Interface (AWS CLI). For more information, see Create an interface endpoint in the AWS PrivateLink Guide.

Create an interface endpoint for WorkSpaces Thin Client by using the following service name:

com.amazonaws.region.thinclient.api

If you enable private DNS for the interface endpoint, you can make API requests to WorkSpaces Thin Client by using its default Regional DNS name. For example, api.thinclient.us-east-1.amazonaws.com.

Create an endpoint policy for your interface endpoint

An endpoint policy is an IAM resource that you can attach to an interface endpoint. The default endpoint policy gives you full access to WorkSpaces Thin Client through the interface endpoint. To control the access granted to WorkSpaces Thin Client from your VPC, attach a custom endpoint policy to the interface endpoint.

For more information, see Control access to services using endpoint policies in the AWS PrivateLink Guide.

Example: VPC endpoint policy for WorkSpaces Thin Client actions

The following is an example of a custom endpoint policy. When you attach this policy to your interface endpoint, it grants access to the listed WorkSpaces Thin Client actions for all principals on all resources.

{
   "Statement": [
      {
         "Principal": "*",
         "Effect": "Allow",
         "Action": [
            "thinclient:ListEnvironments",
            "thinclient:ListDevices",
            "thinclient:ListSoftwareSets"
         ],
         "Resource":"*"
      }
   ]
}