Target groups provide a flexible way to manage load balancing nodes or targets.
Provider | Notes |
|---|
AWS | An Application load balancer sends traffic to a target group by default. You can create multiple target groups for each load balancer. |
OCI | Each target group belongs exclusively to a single load balancer. You must create at least one target group per load balancer |
GCP | You can create multiple target groups that can belong to multiple load balancers |
| Panel |
|---|
Privileges: Manage load balancers, Assign load balancers |
Before you begin:
Create targets, which may include subnets and IP addresses, or VMs
To create an target group:
Go to myCloud → Virtual datacenters → select a virtual datacenter in AWS → Network → Load balancing → Target groups
Click the + add button
Enter the target group details and assign targets as described below
Click Save
Target group general info
...
| Expand |
|---|
| title | Click here to display details of create target group general info |
|---|
|
Field | Value |
|---|
Name | The name of the target group Amazon will only accept the following characters: A-Z, a-z, 0-9 and "-", and you cannot modify the name
| Type | Select the target type of Private IP for a subnet address, or Virtual machine | Protocol | Load balancers will use the Protocol to route traffic to the target group (See https://docs.aws.amazon.com/elasticloadbalancing/latest/application/load-balancer-target-groups.html#target-group-routing-configuration) | Port | Load balancers will use the Port to route traffic to the target group | Protocol version | For HTTP and HTTPS protocols only, select a compatible version of the protocol | Algorithm | For HTTP and HTTPS protocols only, for example, round robin or least_outstanding_requests |
|
| Expand |
|---|
| title | Click here to display details of create target group general info GCP |
|---|
|
As there are many types of target groups in Google Cloud, this page provides examples of two examples of target group types: instance groups and network endpoint groups. | Note |
|---|
In the platform, you cannot create target groups of these types: But Abiquo onboards all target groups from GCP |
Unmanaged |
...
instance group example  Image ModifiedField | Value |
|---|
Name | The Name of the target group. Google Cloud Platform will only accept the following characters: a-z, 0-9 and "-", and you cannot modify the name | Type | For a typical load balancer with VMs attached, create an UNMANAGED_INSTANCE_GROUP. | Named ports | Enter a port Name to identify each Port in the target group. Keep the names to enter them in load balancers | Global network | The network that the VMs in the unmanaged instance group will use | Subnet | A subnet of the global network that the VMs in the unmanaged instance group will belong to | Location | The public cloud region that the VMs will belong to in the global network | Availability zone | The availability zone to use in the global network |
GCE IP port target group example |
...
 Abiquo recommends GCE_IP_PORT target groups. This screenshot shows an INTERNET_IP_PORT target group. The INTERNET_IP_PORT target group is only available with classic load balancers.
Image ModifiedField | Value |
|---|
Name | The Name of the target group. GCP will only accept the following characters: a-z, 0-9 and "-", and you cannot modify the name | Type | GCE_IP_PORT represents a Network Endpoint Group in GCP. It will load balance GCE IP addresses at the given port | Port | The Port for communicating with the load balanced nodes |
|
| Expand |
|---|
| title | Click here to display details of create target group general info OCI |
|---|
|
In OCI, when you create a target group, it must belong to a load balancer. Each load balancer must have at least one target group. Abiquo target groups are OCI backend sets. Image ModifiedName | The Name of the target group | Type | The DEFAULT type is for load balancers with nodes and the NETWORKING type is for network load balancers | Algorithm | Select the algorithm for traffic distribution. The default is ROUND_ROBIN |
|
Target group health check
...
Screenshot: Create target group health check OCI. In OCI each target group must have its own health check.
...
| Expand |
|---|
| title | Click here to display details of create target group health check (for AWS and OCI) |
|---|
|
Field | Value |
|---|
Name | Name of the health check | Common protocols | Select one of the most common protocols to load presets | Protocol | The protocol with which the health check will be performed | Port | The port to which the health check will be performed | Path | The server path to check. | Status code | | Response body | | Interval (sec) | The interval in seconds between health checks | Timeout (sec) | The timeout in seconds after which an attempted health check will be considered unsuccessful | Attempts | The number of attempts before the health check will be considered unsuccessful |
|
Target group targets
In AWS, when you create the target group you can add targets.
...
| Expand |
|---|
| title | Click here to display details of edit target group targets OCI GCP |
|---|
|
Screenshot: Edit target group Targets OCI Image ModifiedScreenshot: Edit target group Targets GCP VMs Image ModifiedScreenshot: Edit target group Targets GCP IP addresses and ports Image ModifiedTo add a target: Select or enter a target and click Add When you have finished adding all of your targets, click Save
|