VPC-ENI in AWS Device Farm - AWS Device Farm

VPC-ENI in AWS Device Farm

Warning

This feature is only available on private devices. To request private device use on your AWS account, please contact us. If you already have private devices added to your AWS account, we strongly recommend using this method of VPC connectivity.

AWS Device Farm's VPC-ENI connectivity feature helps customers securely connect to their private endpoints hosted on AWS, on-premise software, or another cloud provider.

You can connect both Device Farm mobile devices and their host machines to an Amazon Virtual Private Cloud (Amazon VPC) environment in the us-west-2 Region, which enables access to isolated, non-internet-facing services and applications through an elastic network interface. For more information on VPCs, see the Amazon VPC User Guide.

If your private endpoint or VPC is not in the us-west-2 Region, you can link it with a VPC in the us-west-2 Region using solutions such as a Transit Gateway or VPC Peering. In such situations, Device Farm will create an ENI in a subnet you provide for your us-west-2 Region VPC, and you'll be responsible for ensuring that a connection can be established between the us-west-2 Region VPC and the VPC in the other Region.

For information on using AWS CloudFormation to automatically create and peer VPCs, see the VPCPeering templates in the AWS CloudFormation template repository on GitHub.

Note

Device Farm doesn't charge anything for creating ENIs in a customer's VPC in us-west-2. The cost for cross-Region or external inter-VPC connectivity isn't included in this feature.

Once you configure VPC access, the devices and host machines that you use for your tests won't be able to connect to resources outside of the VPC (e.g., public CDNs) unless there is a NAT gateway that you specify within the VPC. For more information, see NAT gateways in the Amazon VPC User Guide.