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 instances in the public Cloud. Instances behind a load balancer are called backend instances, 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 an External IP (EIP) 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

Before you begin: Configure the security group of back-end 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.

  1. Click Services > Load Balancers.

  2. Click Create .
    The CREATE LOAD BALANCER dialog box appears.

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

    • This name must be unique for the whole Region and follow the domain names rules.

    • 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.

  4. In the VPC list, leave the None box checked.

    Selecting None in the VPC list makes the Scheme, Subnet and Security Group(s) lists unavailable.

  5. From the Availability Zone list, select the Availability Zone you want to use.

    By default, the Availability Zone A is selected.

  6. Click Create to validate.
    The load balancer is created and appears on the Load Balancers page.
    You can modify the attributes of a load balancer after its creation. For more information see Modifying an Instance Attribute.

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

Before you begin: Configure the security group of back-end 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 and follow the domain names rules.

    • 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 ou SSL).

    • LoadBalancerPort: The port on which the load balancer is listening (between 1 and 65535, both included).

    • InstancePort: The port on which the back-end instances are listening (between 1 and 65535, both included).

    • (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"
}

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

Before you begin: Configure the security group of back-end 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.

See the CreateLoadBalancer command sample in the documentation of the OUTSCALE API.

Related Pages

Corresponding API Method

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