Load balancing gives your instances one address and spreads connections or requests across them, leaving out the ones that fail their health check: network load balancers in three sizes at the infrastructure provider, application load balancers with host and path rules and a web ACL on the shared fleet, and dedicated load balancers with addresses of their own, public or inside a VPC.
A load balancer gives your instances one address and spreads incoming connections or requests across them, leaving out the ones that fail their health check.
Put an application load balancer in front of an instance that serves HTTP, reach it at its own name, and delete it again.
What the network types lb11, lb21 and lb31, the application type and the dedicated type each carry, reach and cost, and which features each one has.
Create a load balancer of one of the five types in a region, public or, for the network and dedicated types, attached to a VPC.
Send a load balancer's traffic to an instance or an IP address, or stop sending it there.
Add an https service whose certificate {{product}} issues for names in your hosted zones and renews, optionally redirecting HTTP to HTTPS.
On an application load balancer, send requests for a host name or path prefix to their own target group.
Who may do what with a load balancer (IAM), what is audited, where certificate keys are kept, and how targets can tell your load balancer's traffic apart.
Watch a load balancer's live numbers, read its access log, and receive events about its certificates and its web ACL.
Where each type of load balancer runs, what the platform keeps, how a failed machine is replaced, and what was measured.
User Guide
20 pages: concepts, tasks, security, quotas, troubleshooting.
API Reference
14 operations, with their parameters and IAM actions.
CLI Command Reference
14 commands, one per API operation, with their arguments and flags.
Terraform resources
4 resources and data sources of the provider.
Document history
What changed in these docs.