Deploy Bot Defense on any Edge with F5 Distributed Cloud (SaaS Console, Automation)
Introduction
This guide, along with the provided scripts and sample app and services, is designed to help explore and demonstrate the use cases of the F5 Distributed Cloud (XC) Bot Defense in a variety of different cloud environments including AWS, Azure, GCP, and within the Distributed Cloud (XC) Regional Edge.
XC Bot Defense Connector Strategy
F5 Distributed Cloud Bot Defense meets you where you’re at when it comes to deployment flexibility. We make it ridiculously easy for you to deploy XC Bot Defense either in the cloud, on-prem, or as a hybrid configuration with pre-built connecters in leading application platforms and CDNs to make deployment easy and fast.
Choose Your Path
Within each deployment scenario, you can choose your path with the following options to deploy the specified Bot Defense environment using either the console deployment link or automation with terraform.
Module 1 | Deploy Bot Defense on Regional Edges with F5 Distributed Cloud |
Module 2 | Deploy F5 XC Bot Defense for AWS Cloudfront with F5 Distributed Cloud |
Module 3 | Deploy Bot Defense in Azure with BIG-IP Connector for F5 Distributed Cloud |
Module 4 | Deploy Bot Defense in GCP Using BIG-IP Connector for F5 Distributed Cloud |
XC Bot Defense Scenarios
The modules below lay out a framework for connecting and managing distributed app services for this scenario, with a focus on the three core use cases.
MODULE 1: Deploy Bot Defense on Regional Edges with F5 Distributed Cloud
In this scenario, we will be deploying our fictitious airline application into a Regional Edge location of our choosing via the VK8's service in XC. We'll walk through all of the required steps, provide the vk8's manifest file and front end this application with an XC HTTP Load Balancer. In addition, the HTTP Load Balancer will be used to front-end our application and enable our XC Bot Defense Service.
Choose your path:
- Console Steps for XC Bot Defense on Regional Edges
- Coming Soon*** Automated Deployment of XC Bot Defense on Regional Edge via Terraform
MODULE 2: Deploy F5 XC Bot Defense for AWS Cloudfront with F5 Distributed Cloud
In this scenario, we will be deploying our fictitious application in AWS with the XC Bot Defense Connector for AWS Cloudfront Distributions.
Choose your path:
- Console Steps to Deploy F5 XC Bot Defense for AWS Cloudfront
- Coming Soon*** Automated Deployment of XC Bot Defense for AWS Cloudfront
MODULE 3: Deploy Bot Defense in Azure with BIG-IP Connector for F5 Distributed Cloud
In this scenario, we will be deploying our fictitious application into Azure with the XC Bot Defense Connector for BIG-IP.
Choose your path:
- Console Steps to Deploy F5 XC Bot Defense in Azure with BIG-IP Connector
- Coming Soon*** Automated Deployment of XC Bot Defense in Azure with BIG-IP Connector
MODULE 4: Deploy Bot Defense in GCP Using BIG-IP Connector for F5 Distributed Cloud
In this scenario, we will be deploying our fictitious application into GCP with the XC Bot Defense Connector for BIG-IP.
Choose your path:
- Console Steps to Deploy F5 XC Bot Defense in GCP Using BIG-IP Connector
- Coming Soon*** Automated Deployment of XC Bot Defense in GCP with BIG-IP Connector
For additional information, refer to these resources:
- Deploy Bot Defense on any Edge with F5 Distributed Cloud (SaaS Console, Automation)
- GitHub repository with the walk-through of the deployment steps & demo
- YouTube video series discussing the different aspects of this configuration
- DevCentral Learning Series: Edge Compute
- Get Started with F5 Distributed Cloud Services
Nice post. Can I ask if for customer edge (CE) based HTTP LB is the Bot Defense deployment the same as for the XC RE?
- Dave_PotterEmployee
CE and RE (regional edge) bot defense works the same, traffic is processed directly at the edge and doesn't need to be back-hauled or sent to a regional or central location.