Internet-facing Classic Load Balancers - Elastic Load Balancing

Internet-facing Classic Load Balancers

An internet-facing load balancer has a publicly resolvable DNS name, so it can route requests from clients over the internet to the EC2 instances that are registered with the load balancer.

An internet-facing load balancer routes traffic from the internet to your EC2 instances.

Public DNS names for your load balancer

When your load balancer is created, it receives a public DNS name that clients can use to send requests. The DNS servers resolve the DNS name of your load balancer to the public IP addresses of the load balancer nodes for your load balancer. Each load balancer node is connected to the back-end instances using private IP addresses.

The console displays a public DNS name with the following form:

Create an internet-facing load balancer

When you create a load balancer in a VPC, you can make it an internal load balancer or an internet-facing load balancer. You create an internet-facing load balancer in a public subnet.

When you create your load balancer, you configure listeners, configure health checks, and register back-end instances. You configure a listener by specifying a protocol and a port for front-end (client to load balancer) connections, and a protocol and a port for back-end (load balancer to back-end instances) connections. You can configure multiple listeners for your load balancer.

To create a basic internet-facing load balancer, see Tutorial: Create a Classic Load Balancer.

To create a load balancer with an HTTPS listener, see Create a Classic Load Balancer with an HTTPS listener.