Network Settings for Fleet and Image Builder Instances
The following sections contain information about configuring your AppStream 2.0 fleets and image builders to access network resources and the Internet.
When creating an AppStream 2.0 fleet or image builder, you can provide Amazon VPC subnets. AppStream 2.0 sets up elastic network interfaces (ENI) to the subnets provided so that AppStream 2.0 instances have access to your network resources or have access to public Internet through your VPC. For more information about Amazon VPC, see VPC and Subnet Basics.
- Network Setup Guidelines
- Enabling Internet Access Using a Public Subnet
- Enabling Internet Access Using a NAT Gateway
Network Setup Guidelines
There are some network setup guidelines to consider for fleets and image builders. If your fleets and image builders require Internet access, you can use either the Default Internet Access feature, or manually control Internet access using an advanced networking configuration such as a VPC with NAT gateways. For more information, see Enabling Internet Access Using a Public Subnet and Enabling Internet Access Using a NAT Gateway.
You can provide subnets to establish network connections from your fleet instances to your VPC. We recommend that you specify two private subnets from different Availability Zones for high availability and fault tolerance. Also, ensure that the network resources for your applications are accessible through both of the specified private subnets.
AppStream 2.0 creates as many elastic network interfaces as the maximum desired capacity of your fleet. The following guidelines will help you set up a VPC to support scaling behavior for your fleet.
Make sure that your AWS account has sufficient elastic network interface capacity to support the scaling requirements of your fleet. If you are planning to launch a large fleet of streaming instances, contact AWS Support and request a higher ENI limit to match the maximum number of instances that you plan to launch.
Specify subnets with a sufficient number of elastic IP addresses to match the maximum desired capacity of your fleet.
You can choose one subnet while launching an image builder. Ensure the subnet accessibility of the network resources,with which your applications may interact. The typical resources required for successful execution of your apps may include licensing servers, database servers, file servers, and so on.