- Newest
- Most votes
- Most comments
While AWS does recommend using a separate VPC for your WorkSpaces deployment in some cases, the process for configuring a VPC for WorkSpaces Personal is slightly different from what you might expect.
When setting up WorkSpaces Personal, you don't create a separate VPC specifically for WorkSpaces. Instead, you select an existing VPC and subnets within that VPC when creating your WorkSpaces directory.
During the creation of a WorkSpaces Personal directory, you'll be prompted to choose a VPC and subnets. These are the VPC and subnets where your WorkSpaces will be launched. You should select the VPC that you've configured for your WorkSpaces deployment, which may be the same VPC where your managed AD is located.
It's important to note that you need to select two subnets from your VPC, and these subnets must be in different Availability Zones. This is to ensure high availability for your WorkSpaces.
If you're not seeing the subnets you expect, make sure that you've properly configured your VPC for WorkSpaces Personal. This includes setting up the correct number of subnets in the appropriate Availability Zones that are supported for WorkSpaces in your region.
Remember, WorkSpaces Personal requires specific configurations for the VPC, including considerations for internet access (either through public subnets with an internet gateway or private subnets with a NAT gateway). If you haven't set up your VPC correctly for WorkSpaces, you may need to modify your VPC configuration or create a new VPC that meets the requirements for WorkSpaces Personal.
Sources
Configure a VPC for WorkSpaces Personal - Amazon WorkSpaces
Create a dedicated Custom directory with WorkSpaces Personal - Amazon WorkSpaces
Configure a VPC for WorkSpaces Pools - Amazon WorkSpaces
Relevant content
asked 3 years ago
asked 2 years ago
asked 4 years ago
- AWS OFFICIALUpdated 2 years ago
