Create a Basic Internal Load Balancer in Amazon VPC

1. Start the Create Load Balancer wizard:

   1. On the Amazon EC2 Getting Started page, in the EC2 Dashboard pane, under NETWORK & SECURITY, click Load Balancers.

      

   2. On the Load Balancers page, click Create Load Balancer.

2. On the DEFINE LOAD BALANCER page, enter a name for your Amazon VPC load balancer (e.g., MyVPCLoadBalancer).

3. Click the arrow in the Create LB inside box and select the Amazon VPC in which you want to create your load balancer.

4. By default, Elastic Load Balancing creates an Internet-facing load balancer with a publicly resolvable DNS name that resolves to public IP addresses. In this example, you'll create an internal load balancer with a publicly resolvable DNS name that resolves to private IP addresses.

   Click Create an internal load balancer box.

   Note

   Do not select Create an internal load balancer if you want the DNS name of your load balancer to resolve to public IP addresses.

5. Leave the Listener Configuration set to the default value.

   

6. Click Continue to configure the health check for your instances.

7. Configure the health check settings that your application requires.

   

8. Click Continue to select the subnet in which you want to launch your load balancer instance.

9. In the Available Subnets table, click the green button at the left to select the subnet in which you want to have your load balanced instances.

   

   Your selected subnets are displayed in the Selected Subnets table.

   

10. Click Continue to select security groups to assign to your load balancer.

11. If you use a pre-existing security group, ensure that it allows ingress to the ports that you configured the load balancer to use. If you create a security group in this step, the console will define these ports to be open for you. This example uses the default security group associated with your virtual private cloud.

    Select Choose one or more of your existing Security Groups and then select the default security group.

    

12. Click Continue to add running EC2 instances to your load balancer.

13. In the Manually Add Instances to LoadBalancer table, check the boxes in the Select column to add instances to your load balancer.

    

    Note

    When you register a multi-homed instance (an instance that has an elastic network interface (ENI) attached) with your load balancer, the load balancer will route traffic to the primary IP address of the instance (eth0). For more information on using ENIs, go to Elastic Network Interfaces.

14. Click Continue to review your configuration. On the REVIEW page, click Create to create your load balancer.

15. A confirmation window opens. Click Close.

16. When the confirmation window closes, the Load Balancers page opens. Your new load balancer now appears in the list. Select the check box next to your load balancer.

17. A set of tabs opens with details about your new load balancer. Check the description in the row titled Scheme. It shows that your newly created load balancer is internal.

    

To create a basic internal load balancer in EC2-VPC

1. Call CreateLoadBalancer using the following parameters:

   • Subnets = subnet-450f512c

   • [Optional] Use this parameter to create an internal load balancer. You need not specify this parameter if you're creating an Internet-facing load balancer.

     Scheme = internal

   • Listener

     • Protocol = HTTP

     • InstanceProtocol = HTTP

     • InstancePort = 80

     • LoadBalancerPort = 80

   • LoadBalancerName = MyVPCLoadBalancer

   • SecurityGroups = sg-b9ffedd5

2. The operation returns the DNS name of your load balancer. You can then map any other domain name (such as www.example.com) to your load balancer’s DNS name using CNAME or some other technique.

To register your Amazon EC2 instances with your VPC load balancer

You should only register instances that are in the Pending or Running state and are in an Amazon Virtual Private Cloud (VPC).

• Call RegisterInstancesWithLoadBalancer with the following parameters:

  • LoadBalancerName = MyVPCLoadBalancer

  • Instances = [ i-4f8cf126, i-0bb7ca62 ]

  Note

  When you register a multi-homed instance (an instance that has an elastic network interface (ENI) attached) with your load balancer, the load balancer will route traffic to the primary IP address of the instance (eth0). For more information on using ENIs, go to Elastic Network Interfaces.

To verify that an internal load balancer was created

1. Call DescribeLoadBalancers with the following parameter:

   • LoadBalancerName = MyVPCLoadBalancer

2. The operation returns the description of your load balancer. The description in the Scheme field indicates that your newly created load balancer is internal.

To create a basic internal load balancer in EC2-VPC

1. Enter the command elb-create-lb as in the following example.

   PROMPT> elb-create-lb  MyVPCLoadBalancer --subnets subnet-4e05f721  --scheme internal --security-groups sg-b9ffedd5 --listener "lb-port=80,instance-port=80,protocol=http,instance-protocol=http" 
                           

   Note

   Use --scheme option to create an internal load balancer. You need not specify this option if you're creating an Internet-facing (public) load balancer.

2. Elastic Load Balancing returns the following:

   DNS-NAME  DNS-NAME 
   DNS-NAME  internal-MyVPCLoadBalancer-2111276808.us-east-1a.elb.amazonaws.com

To register your Amazon EC2 instances with your VPC load balancer

You should only register instances that are in the Pending or Running state and are in an Amazon VPC.

1. Use the elb-register-instances-with-lb command as in the following example.

   PROMPT> elb-register-instances-with-lb  MyVPCLoadBalancer  --instances i-4f8cf126,i-0bb7ca62

2. Elastic Load Balancing returns the following:

   INSTANCE  INSTANCE-ID
   INSTANCE  i-4f8cf126
   INSTANCE  i-0bb7ca62		

   Note

   When you register a multi-homed instance (an instance that has an elastic network interface (ENI) attached) with your load balancer, the load balancer will route traffic to the primary IP address of the instance (eth0). For more information on using ENIs, go to Elastic Network Interfaces.

To verify that an internal load balancer was created

1. Use the elb-describe-lbs command as in the following example.

   PROMPT> elb-describe-lbs  MyVPCLoadBalancer

2. Elastic Load Balancing returns the following:

   LOAD_BALANCER   MyVPCLoadBalancer  internal-MyVPCLoadBalancer-2111276808.us-east-1a.elb.amazonaws.com
   2012-06-04T02:33:20 450Z internal