GCP
This section describes how to onboard and deploy Reblaze via the Google Cloud Platform (GCP) Marketplace.
Before carrying out your first deployment, we suggest that you watch these videos to better understand the onboarding and deployment process.
The process for onboarding Reblaze in GCP includes the following steps:
Last Steps
Route your traffic to the load balancer
Now test to check whether 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 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.
Last updated