Should be added to an allow list to ensure connectivity to the service. When deploying WorkSpaces using WSP, the WSP Gateways More information on the use of this feature The protocol used can also be changed at a later time using the Amazon WorkSpaces Migrate feature. Additional information on the recommended protocol use The previous questions are critical to determine the protocol that should be used. Please refer to the decision matrix below: Several key questions that should be answered prior to deployment. When deciding whether or not use the WSP protocol, there are
Protocol from the WorkSpaces by offloading metric analysis,Įncoding, codec usage and selection. Streaming protocol that enables a consistent user experienceĪcross global distances and unreliable networks. This helps ensure lower latency and cross-link traffic.Īmazon WorkSpaces Streaming Protocol (WSP) is a cloud-native Replication, and client authentication - uses the most efficient These associations help ensure that traffic - such as AD DS To assign to the site links (cost 100) to ensure site-independent The following figure is an example of what costs Meaning that clients (in this case, WorkSpaces) use theirįigure 15: Active Directory sites and services: client affinityįor site links between on-premises AD DS and the AWS Cloud. On-premises, and the Amazon WorkSpaces in the cloud.ĭefining the correct site topology ensures client affinity, In scenario 2, at least two sites are present: Site topology controls AD replicationīetween domain controllers within the same site and across siteīoundaries. It’s recommended that each domainĬontroller that resides in the AWS Cloud be a global catalog andĢ, sites and services are critical components for theĬorrect function of AD DS.
However, in scenarios 2 or 3, this would be the locallyĭeployed directory service (AD DS on Amazon EC2 or AWS Directory In scenario 1, the DHCP scope would be the on-premises DNS or ADĭS. With DHCP options sets in the Amazon Virtual Private Cloud User Guide. Table 2 - Custom set of DHCP scope optionsĬreates a tag with key = name and value set to aĮnter the same comma separated IPs as per domain nameįor details on creating a custom DHCP option set and associating Options that must be created for Amazon WorkSpaces and AWSĭirectory Services to function correctly. The following table is an example of a custom set of DHCP scope
#AWS WORKSPACES ARCHITECTURE DIAGRAM WINDOWS#
Windows instances or WorkSpaces are configured to use the AD In each of the scenarios defined earlier,Ĭustomers create and assign their own scope that defines theĭomain name and name servers. Of Windows services within a customer VPC depends on this DHCP Options, such as the domain name or the name servers that shouldīe handed to customer instances via DHCP. +2 address space, and is assigned to all instances via a defaultĭHCP options sets are used within an Amazon VPC to define scope That is accessible via the Classless Inter-Domain Routing (CIDR) By default,Įvery VPC provides an internal Domain Name System (DNS) server Services are provided by default for your instances. With an Amazon VPC, Dynamic Host Configuration Protocol (DHCP) Rules to a Security Group in the Amazon Elastic Compute Cloud User Guide. Overview and network port requirements for Windowsįor step-by-step guidance for implementing rules, refer to RADIUS (private data center or Amazon EC2) *ĭirectory and Active Directory Domain Services Port Remote Microsoft Windows PowerShell (optional) In thisĮxample all services reside in the same Amazon VPC.Īctive Directory (private data center or Amazon EC2) *Īctive Directory (private data center or Amazon EC2) ** The following figure shows the separation of AD DS and ADĬonnector into dedicated private subnets (scenario 3). Of separation of roles or functions within the Amazon VPC. Services for WorkSpaces, while maintaining standard best practices ThisĬonstruct provides highly available, low latency access to AD DS
The AWS Cloud into a dedicated pair of private subnets, across twoĪZs, and separated from AD Connector or WorkSpaces subnets. This section discusses key design considerations whenĭeploying AD DS for Amazon WorkSpaces, VPC best practices for AWSĭirectory Service, DHCP and DNS requirements, AD ConnectorĬonsiderations section of this document and documentedĮarlier for scenarios 2 and 3, customers should deploy AD DS in
Understanding of both Active Directory concepts and specific AWS A functional AD DS deployment in the AWS Cloud requires a good
0 kommentar(er)
