We use cookies on our website to ensure we provide you with the best experience on our website. By using our website, you agree to the use of cookies for analytics and personalized content.This website uses cookies. More Information
It seems like your browser didn't download the required fonts. Please revise your security settings and try again.
Barracuda Web Application Firewall

How the Barracuda CloudFormation Template Works in Bring-Your-Own-License (BYOL) instance

  • Last updated on

The following flowchart explains how the Barracuda CloudFormation Template works:

  BYOL_Auto_Scaling_July_13_2017.jpg

With regard to the flowchart, the following steps describe how a Barracuda CloudFormation Template works:

  1. A CloudFormation Template (CFT) is uploaded and a stack is created on Amazon Web Services. With this:
  2. The Barracuda CloudGen WAF instance(s) will be deployed and provisioned in the Virtual Private Cloud (VPC) specified while creating the stack.
  3. Creates “License.dat” and “License Usage History” files.
  4. After the Barracuda CloudGen WAF VM(s) is/are up and ready to serve the traffic:
  5. It checks for license availability,
    1. If the license file is available with unused licenses:
      1. The “License.dat” and “License Usage History” files gets updated with the license and instance ID information.
      2. The instance uses an unused license key and boots up.
    2. It checks the Cluster S3 bucket for any other existing VM(s) in this Auto Scaling group.
      1. If there is no VM data available in the Cluster S3 bucket, the VM is configured based on the service configuration data provided during CFT upload or from the backup file provided as the input in the CFT.
      2. If there is an existing Barracuda CloudGen WAF instance information available in the Cluster S3 bucket, the new instance clusters with the existing instance and gets all configuration synchronized to it.
    3. Adds its information to the Cluster S3 bucket specified while creating the stack. The Cluster S3 bucket stores instance data, serial number and primary IP address (i.e., WAN IP address) of the deployed Barracuda CloudGen WAF instance(s).
    4. The Barracuda CloudGen WAF is now ready to serve the traffic to the configured services.
    5. If the instance encounters high traffic flow and triggers any of the created alarms, such as high bandwidth utilization, CPU usage, etc., then:
      1. A new Barracuda CloudGen WAF instance gets initiated automatically.
      2. Looks at the Cluster S3 bucket created in step 1 (a) and clusters with it.
      3. Adds its information to the Cluster S3 bucket, and is ready to serve the traffic.
      4. Traffic gets distributed among the instances through ELB.
  6. If the license file or unused license keys are not available, the Barracuda CloudGen WAF for AWS stops in the license page until the key is manually entered.
  7. If the traffic flow returns to normal, the Scale Down alarm is triggered.
    1. The added Barracuda CloudGen WAF instance gets removed from the auto scaling group.
    2. Instance IP address and serial number details gets removed from the Cluster S3 bucket.
    3. The License.dat and License Usage History files gets updated. 
Next Step

Continue with the Importing the Barracuda CloudGen WAF for AWS BYOL CFT and Deploying the Instance  article to import the CFT and deploy the instance.

Last updated on