# AWS

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 <support@reblaze.com>.&#x20;

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

* [Reblaze from the AWS Marketplace: Initial Deployment](https://www.youtube.com/watch?v=njOiMUw0Ojs\&list=PL6cxA-Fe3c445X7NyjZSK3Rk8fE9RLKpo\&index=1\&t=7s)
* [Reblaze from a Marketplace Deployment: Defining Sites and Web Applications](https://www.youtube.com/watch?v=Lypl7rbzF3A\&list=PL6cxA-Fe3c445X7NyjZSK3Rk8fE9RLKpo\&index=2)
* [Reblaze from the AWS Marketplace: Routing Traffic](https://www.youtube.com/watch?v=ZcManqA_m44\&list=PL6cxA-Fe3c445X7NyjZSK3Rk8fE9RLKpo\&index=3)

{% hint style="info" %}
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: <https://aws.amazon.com/>
{% endhint %}

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

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

1. [Deploy Reblaze](https://waap.docs.link11.com/v2.20.4/marketplace-onboarding/aws/deploy-reblaze)
2. [Configure the Reblaze Platform](https://waap.docs.link11.com/v2.20.4/marketplace-onboarding/aws/configure-the-reblaze-platform)
3. [Set Up a Load Balancer](https://waap.docs.link11.com/v2.20.4/marketplace-onboarding/aws/set-up-a-load-balancer-for-traffic-routing)

## 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. &#x20;

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.

<figure><img src="https://content.gitbook.com/content/CWgVjpGHfzXGmM9HfqF3/blobs/Ogpr00jGqzD7SaD7SiJ1/image.png" alt=""><figcaption></figcaption></figure>

### Activate Reblaze traffic filtering

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 [Configure the Reblaze Platform](https://waap.docs.link11.com/v2.20.4/marketplace-onboarding/aws/configure-the-reblaze-platform).

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

For more information on using Reblaze, see the user manual at <https://gb.docs.reblaze.com/>.

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 <support@reblaze.com>, for further one- on-one assistance in setting up your deployment. We’re available 24 hours per day to assist you.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://waap.docs.link11.com/v2.20.4/marketplace-onboarding/aws.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
