Setting up a Load Balancer is a two step process: creating the Load Balancer and then adding backend Droplets.
You can create a Load Balancer using the Create menu at any time or use the Create Load Balancer button on the Load Balancers overview page.
On the creation page, you will:
Choose a datacenter region. Your Load Balancer and Droplets need to be in the same datacenter, so choose the one where your Droplets are or will be located.
Add forwarding rules. You need at least one rule to create a Load Balancer. You can either create new rules now by clicking the New Rule drop down, or accept the default route (HTTP port 80 on the Load Balancer to HTTP port 80 on the backend Droplets) and configure the rules you want after the Load Balancer has been created.
The left side of each rule defines the listening port and protocol on the Load Balancer itself, and the right side defines where and how the requests will be routed to the backends. You can change the protocols using the drop down menus. If you use HTTPS or HTTP2, you will also be asked to choose an existing SSL certificate, create a free certificate using Let’s Encrypt, provide custom certificate files, or use SSL passthrough.
Set advanced settings. Advanced settings allow you to modify some additional parameters for the Load Balancer. The defaults work well for most cases, but the options are:
Choose a name and create. Load Balancer names must be unique and contain alphanumeric characters, dashes, and periods only. Once created, you can change the name at any time by clicking on the existing name on the Load Balancer page.
Your choice of Droplets will be limited to the region where the Load Balancer was created. You can add individual Droplets or select by using a tag. When you use a tag, only the tagged Droplets in the same region as the Load Balancer will be part of its pool. Only one tag can be used per Load Balancer.
When you’ve selected the tag or the Droplets, click Add Droplets. The Load Balancer will check the health of the backend Droplets. Once the backends have passed the health check the required number of times, they will be marked healthy and the Load Balancer will begin forwarding requests to them.