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 WAF-as-a-Service

Understanding Deployment Locations

  • Last updated on

As described in Understanding Traffic Flow with Barracuda WAF-as-a-Service, application traffic flows from your users, through a Barracuda Cloud Scrubbing Center, to your application servers. To minimize latency and maximize performance, it is best to deploy WAF-as-a-Service protection as close to your back-end servers as possible.

Barracuda's partnership with Microsoft Azure enables you to deploy your WAF-as-a-Service protection in most Azure locations.

When selecting a deployment location, consider the following:

  • If you have specific data residency requirements, select only regions that are within the country/countries that meet your data residency requirements.
  • If your application servers are located in North America (US, Canada, Mexico) or West Europe (e.g., Austria, Belgium, France, Germany, Italy, Portugal, Spain, Switzerland, UK), select the North America and West Europe deployment location. This optimizes your deployment across multiple data centers in these regions and provides the best performance.
    Note that selecting a specific country, such as a UK location, will guarantee that data stays within that country, but the regional North America and West Europe will usually provide faster performance.
  • If the first two options do not apply to your situation, select the location closest to your application servers. 

If you do not select the North America and West Europe, you must also select a backup location, to be used if the primary location fails or requires maintenance. Select the second-closest location to your application servers. Be sure to follow data residency requirements, as described above, if they apply to your organization.

When you create your application, WAF-as-a-Service automatically selects the deployment locations that provide the best performance for your application. If you need to change the deployment location (if, for example, you moved your application servers), follow the steps described in Endpoints.

Last updated on