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
  • Last steps
  • Route your traffic to the load balancer
  • Activate Reblaze traffic filtering
  • Going Forward: Customizing Reblaze

Was this helpful?

Export as PDF
  1. Marketplace Onboarding

AWS

This section describes how to onboard and deploy Reblaze via the Amazon AWS Marketplace.

PreviousMarketplace OnboardingNextDeploy Reblaze

Last updated 2 years ago

Was this helpful?

This guide will walk you through the process from the first access of the marketplace until Reblaze is successfully deployed and protecting your website. We offer our help at any step of the process at .

Before doing your first deployment, we suggest that you watch these videos to better understand the onboarding and deployment process.

You must have an AWS account in order to use Amazon Web Services. If you do not have an Amazon account, sign up for one at:

The process for onboarding Reblaze in AWS includes the following steps:

Last steps

Route your traffic to the load balancer

At this point, your deployment and setup are complete. Now you should test if your website works correctly when routing traffic to the Reblaze deployment. Perform offline testing by modifying your hosts file to point your website to the new load balancer. If you see that you are returned to your website, routing via Reblaze is working correctly.

The last remaining step is to route your traffic to the load balancer, which will send it to your Reblaze instance(s). Reblaze will scrub the traffic and forward it on to your servers. To setup this routing, set your DNS record to the IP address that is resolved from the load balancer DNS Name.

Activate Reblaze traffic filtering

Going Forward: Customizing Reblaze

As you might notice from looking through the interface, the Reblaze web security platform is both powerful and highly customizable, with the ability to be fine-tuned for your specific needs. However, it is beyond the scope of this document to describe this customization process. Furthermore, a full and correct customization is often rather daunting for new users.

Initially, Reblaze is setup for report-only mode. Assuming that this option was not changed, then Reblaze is not yet filtering your traffic; it is merely reporting on what it would have filtered had it been set up in active mode. This gives you an opportunity to fine-tune Reblaze’s configuration before any of your traffic is actually affected. When you are comfortable with the reporting results, move the application to Active mode and publish the change, as described in .

For more information on using Reblaze, see the user manual at .

We at Reblaze Technologies want you to have the best experience possible with the platform, so that you will enjoy the full benefits of comprehensive, intelligent, and effortless web security. Therefore, please feel free to contact support at , for further one- on-one assistance in setting up your deployment. We’re available 24 hours per day to assist you.

Configure the Reblaze Platform
https://gb.docs.reblaze.com/
support@reblaze.com
support@reblaze.com
Reblaze from the AWS Marketplace: Initial Deployment
Reblaze from a Marketplace Deployment: Defining Sites and Web Applications
Reblaze from the AWS Marketplace: Routing Traffic
https://aws.amazon.com/
Deploy Reblaze
Configure the Reblaze Platform
Set Up a Load Balancer