AWS cloud environments

这篇文章walks you through setting up your Amazon Web Services (AWS) account as a resource location you can use with Citrix DaaS (formerly Citrix Virtual Apps and Desktops service). The resource location includes a basic set of components, ideal for a proof-of-concept, or other deployment that does not require resources spread over multiple availability zones. After you complete these tasks, you can install VDAs, provision machines, create machine catalogs, and create Delivery Groups.

When you complete the tasks in this article, your resource location includes the following components:

• A virtual private cloud (VPC) with public and private subnets inside a single availability zone.
• An instance that runs as both an Active Directory domain controller and DNS server, located in the private subnet of the VPC.
• Two domain-joined instances on which the Citrix Cloud Connector is installed, located in the private subnet of the VPC.
• An instance that acts as a bastion host, located in the public subnet of your VPC. This instance is used to initiate RDP connections to the instances in the private subnet for administration purposes. After you finish setting up your resource location, you can shut down this instance so it is no longer readily accessible. When you must manage other instances in the private subnet, such as VDA instances, you can restart the bastion host instance.

Task overview

Set up a virtual private cloud (VPC) with public and private subnets.When you complete this task, AWS deploys NAT gateway(s) with an Elastic IP address in the public subnet. This enables instances in the private subnet to access the Internet. Instances in the public subnet are accessible to inbound public traffic while instances in the private subnet are not.

Configure security groups. Security groups act as virtual firewalls that control traffic for the instances in your VPC. You add rules to your security groups that allow instances in your public subnet to communicate with instances in your private subnet. You will also associate these security groups with each instance in your VPC.

Create a DHCP options set. With an Amazon VPC, DHCP and DNS services are provided by default, which affects how you configure DNS on your Active Directory domain controller. Amazon’s DHCP cannot be disabled and Amazon’s DNS can be used only for public DNS resolution, not Active Directory name resolution. To specify the domain and name servers handed to instances through DHCP, create a DHCP options set. The set assigns the Active Directory domain suffix and specifies the DNS server for all instances in your VPC. To ensure Host (A) and Reverse Lookup (PTR) records are automatically registered when instances join the domain, you configure the network adapter properties for each instance you add to the private subnet.

Add a bastion host, domain controller, and Citrix Cloud Connectors to the VPC. Through the bastion host, you can log on to instances in the private subnet to set up the domain, join instances to the domain, and install the Citrix Cloud Connector.

Task 1: Set up the VPC

1. From the AWS management console, selectVPC.
2. From the VPC Dashboard, select Create VPC.
3. Select VPC and more.
4. Under NAT gateways ($) select either In 1 AZ or 1 per AZ.
5. For the NAT instance, specify the instance type and the key pair you want to use. The key pair enables you to securely connect to the instance later.
6. Under DNS options, leaveEnable DNS hostnamesselected.
7. SelectCreate VPC. AWS creates the public and private subnets, Internet gateway, route tables, and default security group.

Note:

Changing the name of an AWS Virtual Private Cloud (VPC) in the AWS console breaks the existing hosting unit in Citrix Cloud. When the hosting unit is broken, you cannot create catalogs or add machines to existing catalogs. From Known Issue: PMCS-7701

Task 2: Configure security groups

This task creates and configures the following security groups for your VPC:

• A public security group, with which instances in your Public subnet will be associated.
• A private security group, with which instances in your Private subnet will be associated.

To create the security groups

1. From the VPC Dashboard, selectSecurity Groups.
2. 为公安gr创建一个安全组oup. SelectCreate Security Groupand enter a name tag and description for the group. In VPC, select the VPC you created earlier. SelectYes, Create.

Configure the Public security group

1. From the security group list, select the Public security group.

2. Select theInbound Rulestab and select Edit to create the following rules:

   Type	Source
   ALL Traffic	Select the Private security group.
   ALL Traffic	Select the Public security group.
   ICMP	0.0.0.0/0
   22 (SSH)	0.0.0.0/0
   80 (HTTP)	0.0.0.0/0
   443 (HTTPS)	0.0.0.0/0
   1494 (ICA/HDX)	0.0.0.0/0
   2598 (Session Reliability)	0.0.0.0/0
   3389 (RDP)	0.0.0.0/0

3. When finished, selectSave.

4. Select theOutbound Rulestab and selectEditto create the following rules:

   Type	Destination
   ALL Traffic	Select the Private security group.
   ALL Traffic	0.0.0.0/0
   ICMP	0.0.0.0/0

5. When finished, selectSave.

Configure the private security group

1. 从安全组列表中,选择私人的年代ecurity group.

2. If you have not yet setup traffic from the public security group, you must set TCP ports to include; select theInbound Rulestab and selectEditto create the following rules:

   Type	Source
   ALL Traffic	Select the NAT security group.
   ALL Traffic	Select the Private security group.
   ALL Traffic	Select the Public security group.
   ICMP	Select the Public security group.
   TCP 53 (DNS)	Select the Public security group.
   UDP 53 (DNS)	Select the Public security group.
   80 (HTTP)	Select the Public security group.
   TCP 135	Select the Public security group.
   TCP 389	Select the Public security group.
   UDP 389	Select the Public security group.
   443 (HTTPS)	Select the Public security group.
   TCP 1494 (ICA/HDX)	Select the Public security group.
   TCP 2598 (Session Reliability)	Select the Public security group.
   3389 (RDP)	Select the Public security group.
   TCP 49152–65535	Select the Public security group.

3. When finished, selectSave.

4. Select theOutbound Rulestab and selectEditto create the following rules:

   Type	Destination
   ALL Traffic	Select the Private security group.
   ALL Traffic	0.0.0.0/0
   ICMP	0.0.0.0/0
   UDP 53 (DNS)	0.0.0.0/0

5. When finished, selectSave.

Task 3: Launch instances

The following steps create four EC2 instances and decrypt the default Administrator password that Amazon generates.

1. From the AWS management console, selectEC2.

2. From the EC2 Dashboard, selectLaunch Instance.

3. Select a Windows Server machine image and instance type.

4. On the Configure Instance Details page, enter a name for the instance and select the VPC you set up earlier.

5. InSubnet, make the following selections for each instance:

   • Bastion host: Select the Public subnet.
   • Domain controller and Connectors: Select the Private subnet.

6. InAuto-assign Public IP address, make the following selections for each instance:

   • Bastion host: SelectEnable.
   • Domain controller and Connectors: SelectUse default settingorDisable.

7. InNetwork Interfaces, enter a primary IP address within the IP range of your private subnet for the domain controller and Cloud Connector instances.

8. On the Add Storage page, modify the disk size, if necessary.

9. On the Tag Instance page, enter a friendly name for each instance.

10. On the Configure Security Groups page, selectSelect an existing security groupand then make the following selections for each instance:

    • Bastion host: Select the Public security group.
    • Domain controller and Cloud Connectors: Select the Private security group.

11. Review your selections and then selectLaunch.

12. Create a new key pair or select an existing one. If you create a new key pair, download your private key (.pem) file and keep it in safe place. You must supply your private key when you acquire the default Administrator password for the instance.

13. SelectLaunch Instances. selectView Instancesto display a list of your instances. Wait until the newly launched instance has passed all status checks before accessing it.

14. Acquire the default Administrator password for each instance:

    1. From the instance list, select the instance and then selectConnect.
    2. SelectGet Passwordand supply your private key (.pem) file when prompted.
    3. SelectDecrypt Password. AWS displays the default password.

15. Repeat Steps 2–14 until you have created four instances: a bastion host instance in your public subnet and three instances in your private subnet that for use as a domain controller and two Cloud Connectors.

Task 4: Create a DHCP options set

1. From the VPC Dashboard, selectDHCP Options Sets.

2. Enter the following information:

   • Name tag: Enter a friendly name for the set.
   • Domain name: Enter the fully qualified domain name you use when you configure the domain controller instance.
   • Domain name servers: Enter the private IP address you assigned to the domain controller instance and the stringAmazonProvidedDNS, separated by commas.
   • NTP servers: Leave this field blank.
   • NetBIOS name servers: Enter the private IP address of the domain controller instance.
   • NetBIOS node type: Enter2.

3. SelectYes, Create.

4. Associate the new set with your VPC:

   1. From the VPC Dashboard, selectYour VPCsand then select the VPC you set up earlier.
   2. SelectActions > Edit DHCP Options Set.
   3. When prompted, select the new set you created and then selectSave.

Task 5: Configure the instances

1. Using an RDP client, connect to the public IP address of the bastion host instance. When prompted, enter the credentials for the Administrator account.

2. From the bastion host instance, launch Remote Desktop Connection and connect to the private IP address of the instance you want to configure. When prompted, enter the Administrator credentials for the instance.

3. For all instances in the private subnet, configure the DNS settings:

   1. SelectStart > Control Panel > Network and Internet > Network and Sharing Center > Change adapter settings. Double-click the network connection displayed.
   2. SelectProperties > Internet Protocol Version 4 (TCP/IPv4) > Properties.

   3. SelectAdvanced > DNS. Ensure that the following settings are enabled and selectOK:

      • Register this connection’s addresses in DNS
      • Use this connection’s DNS suffix in DNS registration

4. To configure the domain controller:

   1. Using Server Manager, add the Active Directory Domain Services role with all default features.
   2. Promote the instance to a domain controller. During promotion, enable DNS and use the domain name you specified when you created the DHCP options set. Restart the instance when prompted.

5. To configure the first Cloud Connector:

   1. Join the instance to the domain and restart when prompted. From the bastion host instance, reconnect to the instance using RDP.
   2. Sign in to Citrix Cloud. SelectResource Locationsfrom the upper left menu.
   3. Download the Cloud Connector.
   4. When prompted, run thecwcconnector.exefile and supply your Citrix Cloud credentials. Follow the wizard.
   5. When finished, selectRefreshto display the Resource Locations page. When the Cloud Connector is registered, the instance appears on the page.

6. Repeat Step 5 to configure the second Cloud Connector.

Where to go next

• For a simple proof-of-concept deployment,install a VDAon a machine that will deliver apps or a desktop to your users.
• For creating and managing a connection, seeConnection to AWS.
• Review all the steps in the installation and configuration process

更多的信息

• Connections and resources
• Create machine catalogs