VPC design

Design guidelines

Deploy WorkSpaces Applications into a dedicated VPC. When designing the WorkSpaces Applications VPC, size for forecasted growth. Reserve IP address capacity for new use cases, and additional Availability Zones (AZs) that may be added at a later time. A fundamental design point of WorkSpaces Applications is that only one user can consume a WorkSpaces Applications instance. When allocating IP space, think one user as one IP address per WorkSpaces Applications instance. With WorkSpaces Applications, it is possible for a user to consume multiple WorkSpaces Applications instances. Therefore, planning IP space must also account for use cases that require additional WorkSpaces Applications instances.

Although the maximum size of a VPC Classless Inter-Domain Routing (CIDR) is /16, AWS recommends not over-allocating private IP addresses. It is possible to extend the size of the VPC through additional CIDRs, but there is a limit to this; therefore, allocate what is needed from the onset.

If the WorkSpaces Applications deployment is joined to an Active Directory domain, the DHCP options set for the VPC must have the domain DNS configured. The domain name server should specify the DNS IP addresses that are either authoritative for the Active Directory domain, or the DNS should forward DNS requests to the authoritative DNS instances for the Active Directory domain. Also, the VPC must have enableDnsHostnames and EnableDnsSupport configured.