Creating an Internet-facing Load Balancer in the Public Cloud

You can create an Internet-facing load balancer to distribute inbound network traffic coming from the Internet between several virtual machines (VMs) in the public Cloud. Instances behind a load balancer are called backend VMs, or backends.

The security group for this load balancer is automatically created and named outscale-elb-sg, owned by outscale-elb. For more information, see About Security Groups in LBU > Security Groups Configuration for Load Balancers in the Public Cloud.

You can associate a public IP with an internet-facing load balancer through the OUTSCALE API only. For more information see the OSC CLI section below.

Creating an Internet-facing Load Balancer in the Public Cloud Using Cockpit v2

Before you begin: Configure the security group of future backend VMs with the following rules:

Allow inbound flows in the TCP protocol on the port you want.
Allow the inbound flows coming from the security group of the load balancer (outscale-elb-sg), owned by outscale-elb.

For more information, see Adding Rules to a Security Group.

In the Load Balancers dashboard, click Create Load Balancer.
The CREATE LOAD BALANCER dialog box appears.

In the Name field, type a name for the load balancer.

This name must be unique for the whole Region.
It must follow domain name rules. That is, it can contain up to 32 alphanumeric characters or hyphens, but cannot start or end with a hyphen.

From the Type list, select internet-facing.
From the Subregion list, select the subregion you want to use.

By default, the Subregion A is selected.
Click Next, then review the settings you have specified for the load balancer.
Click Create.
The load balancer is created.

The load balancer is available about 1 minute after its creation.

Creating an Internet-facing Load Balancer in the Public Cloud Using OSC CLI

Before you begin: Configure the security group of future backend VMs with the following rules:

Allow inbound flows in the TCP protocol on the port you want.
Allow the inbound flows coming from the security group of the load balancer (outscale-elb-sg), owned by outscale-elb.

For more information, see Adding Rules to a Security Group.

The CreateLoadBalancer command creates a load balancer.
The load balancer is created with a unique Domain Name Service (DNS) name. It receives the incoming traffic and routes it to its registered virtual machines (VMs).
By default, this action creates an Internet-facing load balancer, resolving to public IPs. To create an internal load balancer in a Net, resolving to private IPs, use the LoadBalancerType parameter.
You must specify either the Subnets or the SubregionNames parameters.

For more information, see About Load Balancers.

Request sample: Creating an internet-facing load balancer in the public Cloud

$ osc-cli api CreateLoadBalancer --profile "default" \
    --LoadBalancerName "public-lb-example" \
    --SubregionNames '["eu-west-2a"]' \
    --Listeners '[
        {
          "BackendPort": 8080,
          "BackendProtocol": "HTTP",
          "LoadBalancerPort": 8080,
          "LoadBalancerProtocol": "HTTP",
        },
      ]'

This command contains the following attributes that you need to specify:

DryRun: (optional) If true, checks whether you have the required permissions to perform the action.
Listeners: One or more listeners to create.
LoadBalancerName: The unique name of the load balancer (32 alphanumeric or hyphen characters maximum, but cannot start or end with a hyphen).
LoadBalancerType: (optional) The type of load balancer: internet-facing or internal. Use this parameter only for load balancers in a Net.
PublicIp: (optional) (internet-facing only) The public IP you want to associate with the load balancer. If not specified, a public IP owned by 3DS OUTSCALE is associated.
SubregionNames: (optional) (public Cloud only) The Subregion in which you want to create the load balancer. Regardless of this Subregion, the load balancer can distribute traffic to all Subregions. This parameter is required in the public Cloud.
Tags: (optional) One or more tags assigned to the load balancer.

The CreateLoadBalancer command returns the following elements:

LoadBalancer: Information about the load balancer.
ResponseContext: Information about the context of the response.

Result sample: Creating an internet-facing load balancer in the public Cloud

{
  "ResponseContext": {
    "RequestId": "0475ca1e-d0c5-441d-712a-da55a4175157"
  },
  "LoadBalancer": {
    "Tags": [],
    "SourceSecurityGroup": {
      "SecurityGroupName": "outscale-elb-sg",
      "SecurityGroupAccountId": "outscale-elb"
    },
    "SecuredCookies": false,
    "Subnets": [],
    "BackendVmIds": [],
    "ApplicationStickyCookiePolicies": [],
    "LoadBalancerType": "internet-facing",
    "AccessLog": {
      "PublicationInterval": 60,
      "IsEnabled": false
    },
    "DnsName": "public-lb-example.123456789.eu-west-2.lbu.outscale.com",
    "HealthCheck": {
      "UnhealthyThreshold": 2,
      "Timeout": 5,
      "CheckInterval": 30,
      "Protocol": "TCP",
      "HealthyThreshold": 10,
      "Port": 8080
    },
    "LoadBalancerStickyCookiePolicies": [],
    "SubregionNames": [
      "eu-west-2a"
    ],
    "Listeners": [
      {
        "BackendPort": 8080,
        "BackendProtocol": "HTTP",
        "LoadBalancerPort": 8080,
        "LoadBalancerProtocol": "HTTP"
      }
    ],
    "LoadBalancerName": "public-lb-example"
  }
}

Creating an Internet-facing Load Balancer in the Public Cloud Using AWS CLI

Before you begin: Configure the security group of future backend instances with the following rules:

Allow inbound flows in the TCP protocol on the port you want.
Allow the inbound flows coming from the security group of the load balancer (outscale-elb-sg), owned by outscale-elb.

For more information, see Adding Rules to a Security Group.

To create an Internet-facing load balancer in the public Cloud, use the create-load-balancer command following this syntax:

Request sample

$ aws elb create-load-balancer \
    --profile YOUR_PROFILE \
    --load-balancer-name my-load-balancer \
    --listeners Protocol=TCP,LoadBalancerPort=80,InstanceProtocol=TCP,InstancePort=58 \
    --availability-zones eu-west-2a \
    --endpoint https://lbu.eu-west-2.outscale.com

This command contains the following attributes that you need to specify:

(optional) profile: The named profile you want to use, created when configuring AWS CLI. For more information, see Installing and Configuring AWS CLI.

load-balancer-name: The name of the load balancer.

This name must be unique for the whole Region.
It must follow domain name rules. That is, it can contain up to 32 alphanumeric characters or hyphens, but cannot start or end with a hyphen.

listeners: One or more listeners for the load balancer. This attribute requires the following elements for each listener:

To add several listeners, separate each of them with a space.
- Protocol: The routing protocol of the load balancer (HTTP, HTTPS, TCP or SSL).
- LoadBalancerPort: The port on which the load balancer is listening (between 1 and 65535, both included).
- InstancePort: The port on which the backend instances are listening (between 1 and 65535, both included).
- (optional) InstanceProtocol: The protocol for routing traffic to backend instances (HTTP, HTTPS, TCP or SSL).
- (optional) SSLCertificateId: The OUTSCALE Resource Name (ORN) of an SSL certificate. For more information, see Getting Information About a Server Certificate.
  
  An SSL certificate is required only if the load balancer protocol is HTTPS or SSL.
  
  For more information about how to configure your listener when using SSL certificates, see Configuring a Load Balancer for SSL Termination or SSL Passthrough.
availability-zones: The Availability Zone (AZ) in which you want to create the load balancer. Regardless of this AZ, the load balancer can distribute traffic to all AZs.
endpoint: The endpoint corresponding to the Region you want to send the request to.

The create-load-balancer command returns the following element:

DNSName: The DNS name assigned to the load balancer.

Result sample

{
    "DNSName": "my_load_balancer_1234567890.lbu.eu-west-2.outscale.com"
}

Related Pages

Corresponding API Methods

AWS™ and Amazon Web Services™ are trademarks of Amazon Technologies, Inc or its affiliates in the United States and/or other countries.