This page describes AWS application load balancers and links to how to create target groups for load balancers in all providers (AWS, OCI, GCP)
Introduction to application load balancers
Abiquo supports AWS Application load balancers. Application load balancers can send traffic to target groups, which contain IP addresses or VMs. Abiquo also continues to support Classic load balancers. See Manage load balancers
For a full description of Application load balancers, see the Amazon documentation at: https://docs.aws.amazon.com/elasticloadbalancing/latest/application/introduction.html .
An application load balancer requires:
At least one target group, which will receive traffic from the default conditional action
At least two public subnets (with an Internet gateway) in different availability zones. See Create a private network.
You should create these elements before you create an application load balancer.
Create a target group
Create an application load balancer in AWS
Before you begin:
Synchronize your virtual datacenters (including VMs, networks, firewalls, firewall rules, and load balancers)
Create firewall policies for your VMs that allow your load balancers to access the VMs
Create a target group with VMs or IP addresses
Create subnets in at least two different availability zones
Privileges: Manage load balancers, Assign load balancers
To create an application load balancer:
Go to Virtual datacenters → select a virtual datacenter → Network → Load balancing → Target groups
Click the + add button to create a target group and complete the dialogs following the AWS documentation
Go to Load balancing → Load balancers
Click the + add button and complete the dialogs following the AWS documentation
Application load balancer general information
Field | Value |
|---|---|
Name | The name of the load balancer.
|
Type | For the Type select Application |
Addresses |
|
Subnets | Select at least two public subnets (with internet gateways) in different availability zones. |
Application load balancer routing rules
Field | Value |
|---|---|
Common protocols | Select one of the common protocols to load presets |
Protocols | The incoming protocol to the load balancer. See AWS documentation for accepted values. |
Ports | The incoming port to the load balancer. See AWS documentation for accepted values. |
Target group | Select a target group |
SSL Certificate | For secure connections (e.g. HTTPS), you can add an SSL certificate.
Select an existing certificate or add a new one. Cannot be used in platform-only load balancers |
Add | Click Add to include the routing rule for the load balancer |
To delete a routing rule, click the delete button beside the name of the routing rule in the list.
After you create the load balancer, you can edit it, and edit the conditional actions for routing rules.
Application load balancer SSL certificate
Field | Value |
|---|---|
Name | Name of the certificate |
Certificate | The certificate contents |
Intermediate certificate | An intermediate certificate can be issued by a provider to support older browsers that may not have all of the trusted root certificates for that provider, so that users will not receive invalid TLS warnings. If you have an intermediate certificate, add it at the same time as the certificate to ensure that a trusted-chain certificate is configured. |
Private key | The RSA private key for the certificate |
Application load balancer firewalls
To add a firewall to your load balancer, select your firewall from the list of Firewalls available in your VDC for this provider.
If a firewall is not on the list, it may not have been properly synchronized. In this case, click Cancel, synchronize firewalls, then start again to create a new load balancer.