Elastic Load Balancing - AWS GovCloud (US)

Elastic Load Balancing

Elastic Load Balancing automatically distributes your incoming application traffic across multiple targets, such as EC2 instances. It monitors the health of registered targets and routes traffic only to the healthy targets.

Elastic Load Balancing supports the following types of load balancers: Application Load Balancers, Network Load Balancers, Gateway Load Balancers, and Classic Load Balancers. All four types of load balancers are supported in AWS GovCloud (US) Regions.


Elastic Load Balancing SSL is not FIPS 140-2 compliant. If there is a requirement for FIPS 140-2 compliance, you can use the Classic or Network Load Balancer to pass TCP traffic and terminate SSL on your web server configured to support FIPS 140-2. If you require the use of the Application Load Balancer with FIPS 140-2 mode, please contact AWS.

How Elastic Load Balancing Differs for AWS GovCloud (US)

  • Your load balancer must run in a virtual private cloud (VPC).

  • Because Elastic Load Balancing must run in a VPC, Classic Load Balancer does not provide IPV6 capability that is offered in standard AWS Regions when running outside of a VPC. Application Load Balancer supports IPv6 in VPCs in all Regions including AWS GovCloud (US) Regions.

  • Export data must be encrypted in transit outside of the export boundary. Because Elastic Load Balancing uses global DNS servers, export traffic across Elastic Load Balancing must be encrypted.

  • Cognito authentication is not available in AWS GovCloud (US) Regions.

Documentation for Elastic Load Balancing

Elastic Load Balancing documentation.

Export-Controlled Content

For AWS Services architected within the AWS GovCloud (US) Regions, the following list explains how certain components of data may leave the AWS GovCloud (US) Regions in the normal course of the service offerings. The list can be used as a guide to help meet applicable customer compliance obligations. Data not included in the following list remains within the AWS GovCloud (US) Regions.

  • All customer parameters provided as input to Elastic Load Balancing (via console, APIs, or other mechanism) are not permitted to contain export-controlled data. Examples include the names of load balancers and the names of load balancer policies.

  • Do not enter export-controlled data in the following fields:

    • Resource tags

If you are processing export-controlled data with this service, use the SSL (HTTPS) endpoint to maintain export compliance. For more information, see Service Endpoints.