Uploaded image for project: 'Solution Center'
  1. Solution Center
  2. SOL-521

AWS how to create a classic Load Balancer for EXASOL using AWS tools

    XMLWordPrintable

    Details

    • Type: How To
    • Status: Published
    • Affects Version/s: EXASolution 5.0.15, EXASolution 5.0.17, EXASOL 6.0.rc1
    • Fix Version/s: None
    • Component/s: EXASolution Cluster
    • Labels:
      None
    • Solution:
      Hide

      Internet-Facing Classic Load Balancers

      An Internet-facing load balancer has a publicly resolvable DNS name, so it can route requests from clients over the Internet to the EC2 instances that are registered with the load balancer. We use this approach make your EXASOL DB connectable from the internet using a single DNS name. An alternative approach using HAproxy and Keepalived (Floating IP) is described in SOL-522.

      Charges that may apply for the load balancer can be found here: https://aws.amazon.com/elasticloadbalancing/classicloadbalancer/pricing.

      When your load balancer is created, it receives a public DNS name that clients can use to send requests. The DNS servers resolve the DNS name of your load balancer to the public IP addresses of the load balancer nodes for your load balancer. Each load balancer node is connected to the back-end instances using private IP addresses.

      In this how to we're using a simple 2+1 cluster in a private subnet (2 active node + 1 spare node). As this how to makes the database connectable from the internet, we recommend to enforce protocol encryption for all database connections (Database parameter "-forceProtocolEncryption=1"). EXA2EXA export and import is not supported.

      Create a Classic Load Balancer

      1. Go to the EC2 console>Load Balancing>Load Balancers
      2. Click on "Create Load Balancer"
      3. Choose "Classic Load Balancer", click "Continue"
      4. Choose a Load Balancer Name, this name will also be used in the public DNS name
        1. Choose the corresponding EXASOL VPC
        2. Load Balancer Protocol: TCP
        3. Load Balancer Port: 8563 (TCP Port for the clients to connect)
        4. Instance Protocol: TCP
        5. Instance Port: 8563 (EXASOL DB Port)
        6. Add EXASOL Subnet
        7. Click "Next"
      5. Assign or Create a Security Group
      6. Allow Incoming Traffic on the Listener Port
      7. Click "Next" to configure the instances Health Check
        1. Ping Protocol: HTTPS This does not check if the database is connectable, please use the XML-RPC interface for this task. Please do not use the database TCP port as the AWS check keeps a TCP socket open and blocks the database
        2. Port: 443
        3. Click "Next"
      8. Add EXASOL DB instances
        1. Select All database nodes (active + spare)
        2. Disable Cross-Zone Load Balancing and Connection Draining
        3. Click "Next"
      9. Add Tags (optional)
      10. Review and Create Classic Load Balancer (it will take some time for DNS entries to be propagated)
      Show
      Internet-Facing Classic Load Balancers An Internet-facing load balancer has a publicly resolvable DNS name, so it can route requests from clients over the Internet to the EC2 instances that are registered with the load balancer. We use this approach make your EXASOL DB connectable from the internet using a single DNS name. An alternative approach using HAproxy and Keepalived (Floating IP) is described in SOL-522 . Charges that may apply for the load balancer can be found here: https://aws.amazon.com/elasticloadbalancing/classicloadbalancer/pricing . When your load balancer is created, it receives a public DNS name that clients can use to send requests. The DNS servers resolve the DNS name of your load balancer to the public IP addresses of the load balancer nodes for your load balancer. Each load balancer node is connected to the back-end instances using private IP addresses. In this how to we're using a simple 2+1 cluster in a private subnet (2 active node + 1 spare node). As this how to makes the database connectable from the internet, we recommend to enforce protocol encryption for all database connections (Database parameter "-forceProtocolEncryption=1"). EXA2EXA export and import is not supported. Create a Classic Load Balancer Go to the EC2 console>Load Balancing>Load Balancers Click on "Create Load Balancer" Choose "Classic Load Balancer", click "Continue" Choose a Load Balancer Name, this name will also be used in the public DNS name Choose the corresponding EXASOL VPC Load Balancer Protocol: TCP Load Balancer Port: 8563 (TCP Port for the clients to connect) Instance Protocol: TCP Instance Port: 8563 (EXASOL DB Port) Add EXASOL Subnet Click "Next" Assign or Create a Security Group Allow Incoming Traffic on the Listener Port Click "Next" to configure the instances Health Check Ping Protocol: HTTPS This does not check if the database is connectable, please use the XML-RPC interface for this task. Please do not use the database TCP port as the AWS check keeps a TCP socket open and blocks the database Port: 443 Click "Next" Add EXASOL DB instances Select All database nodes (active + spare) Disable Cross-Zone Load Balancing and Connection Draining Click "Next" Add Tags (optional) Review and Create Classic Load Balancer (it will take some time for DNS entries to be propagated)
    • Category 1:
      Cluster Administration - Network
    • Category 2:
      Plattform Support - EXASOL on AWS

      Attachments

        Activity

          People

          • Assignee:
            CaptainEXA Captain EXASOL
            Reporter:
            CaptainEXA Captain EXASOL
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated: