Link11 WAAP
v2.18
v2.18
  • Link11 WAAP v2.18 Portal
  • Introduction
  • Getting Started
  • Setup Checklists
  • Marketplace Onboarding
    • AWS
      • Deploy Reblaze
      • Configure the Reblaze Platform
      • Set Up a Load Balancer for Traffic Routing
      • AWS Version Upgrade
    • GCP
      • Deploy Reblaze
      • Configure the Reblaze Platform
      • Set Up GCP Health Checks
      • Set Up GCP Load Balancer
      • GCP BYOL Upgrade
  • Console UI Walkthrough
    • General UI flow
    • Traffic
      • Traffic Concepts
      • Dashboard
      • View Log
    • Security
      • Security Section Concepts
      • Dynamic Rules
      • Quarantined
      • Profiles
        • Profile Concepts
        • Profiles
        • ACL Policies
        • WAF/IPS Policies
        • Custom Signature
      • Args Analysis
      • Tag Rules
      • Rate Limiting
      • Cloud Functions
    • Settings
      • Web Proxy
      • Backend Services
      • Error Pages
      • SSL
      • DNS
      • CDN
      • Planet Overview
      • Global
      • Account
  • Using the product
    • Best Practices
      • Saving and Publishing Your Changes
      • Enabling Passive Challenges
      • Using the Reblaze Query Box
      • Understanding and Diagnosing Traffic Issues
    • How Do I...
      • Ban, Unban, and Whitelist Traffic Sources
      • Bypass Rate Limits for Loadtesting
      • Control Caching Behavior
      • Filter by Content
      • Quickly Block an Attacker
      • Secure Traffic from a Third-Party Page
      • Set Rate Limits and Exemptions
      • Set up SIEM/SOC integration
      • Video Tutorials
        • DNS Training
    • API
      • Reblaze REST API
      • Mobile SDK
  • Reference Information
    • Access log-structure
    • Acronyms
    • Deployment Terminology
    • Hostile Bot Detection / RCSI
      • Environmental detection and browser verification
      • Client authentication
      • Biometric behavioral verification
    • HTTP Response Codes
    • Pattern Matching Syntax
    • Signatures
    • Tags
    • TTL Expression Syntax
  • Support
Powered by GitBook
On this page
  • ​Configure a Load Balancer
  • Configure Security Settings
  • Configure Security Groups
  • Configure Routing and Create the Load Balancer
  • Update Listeners

Was this helpful?

Export as PDF
  1. Marketplace Onboarding
  2. AWS

Set Up a Load Balancer for Traffic Routing

During initial deployment, an autoscale group for Reblaze was created. In this section, you will attach this group to an AWS Application Load Balancer.

PreviousConfigure the Reblaze PlatformNextAWS Version Upgrade

Last updated 2 years ago

Was this helpful?

Related video:

​Configure a Load Balancer

  1. Go to the AWS Management console at .

  2. In AWS Services, go to EC2 > Load Balancers and click Create Load Balancer.

3. Click Create for Application Load Balancer.

4. Set the Load Balancer parameters:

1. Enter a name for the Load Balancer.

2. Under Load Balancer Protocol, select HTTP and HTTPS.

3. Under Availability Zones, select at least 2 zones.

These should be the same zones as you selected when specifying CloudFormation parameters in Specify Stack Details.

5. Click Next: Configure Security Settings.

Configure Security Settings

On the HTTPS listener, attach the correct certificate and select the Security policy.

  1. Select a certificate name.

  2. Select a security policy.

  3. Click Next: Configure Security Groups.

Configure Security Groups

Allow access to the Load Balancer. Typically you will add a new security group for this, or you can select an existing one.

  1. Select Create a new security group.

  2. Enter a name for the security group.

  3. For TYPE, click and select HTTP for the first row and HTTPS for the second row.

  4. Click Next: Configure Routing.

Configure Routing and Create the Load Balancer

  1. For Target Group, select Existing target group.

  2. For Target type, select Reblaze-80. This is already available from the Marketplace deployment.

  3. Click Next: Register Targets.

  4. Click Next: Review.

  5. Click Create.

  6. Once the load balancer is created, click Close.

Update Listeners

The Load Balancer has been created and will appear on the Load Balancer page. Since you created an HTTPS listener earlier, the target group will require an update.

  1. Select the Listeners tab for the load balancer.

  2. You can see that both Listeners are being forwarded to Reblaze-80. Click View/edit rules for HTTPS 443. The Rules page for HTTPS:443 appears.

  3. Click the edit icon (the pencil icon) on the Rules toolbar to edit the rules, then click the edit icon for HTTP:443. The Edit Rule box appears.

  4. Click the edit icon under THEN.

  5. For Target group, select Reblaze-443.

  6. Click Update on the Rules toolbar. A message that "Default rule was successfully updated" appears.

  7. Click the back arrow on the Rules toolbar to return to the Load Balancer page.

  8. To confirm that the load balancer is configured correctly:

    1. Select the Description tab for the load balancer.

    2. Highlight the DNS name and click the copy icon next to it.

    3. Paste the DNS into a browser window. The browser should return a "403 Forbidden" page from "rhino-core-shield".

Now, return to for the final steps needed to get Reblaze running on your website.

AWS
Reblaze from AWS Marketplace: Routing Traffic
https://console.aws.amazon.com/