DataDome Fastly module detects and protects against bot activity.

DataDome Bot protection can be integrated directly inside Fastly.

Before the regular Fastly process starts, a preflight request is performed on the closest DataDome endpoint. Depending on the API response, the module either blocks the request or lets Fastly proceed with the regular process.

The module has been implemented to ensure the best user experience: if any errors were to occur during the preflight, or if the timeout is reached, the module will automatically disable its blocking mechanism and allow the regular Fastly process to proceed.

DataDome provides 3 integration options:

  • A. Regular VCL snippets through the Fastly dashboard
  • B. Dynamic snippets through the Fastly API
  • C. Custom VCL through the Fastly dashboard

You can find the code here

A. Regular VCL snippets on web UI


Before integrating DataDome, you should ask Fastly Support to enable DataDome support for your Fastly service as described here.

Create a Fastly service or use an existing one, then create a new version of your service by cloning the actual one.
Go to the VCL snippets category, and upload each VCL snippet there.
Start with the init one.


Do not forget to put your API key on line 5

Upload all the other snippets one by one, making sure to select the proper snippet type from the dropdown menu (recv, pass, deliver, etc..).

Once done, click the activate button to deploy your changes.

B. Regular VCL snippets with Terraform


Before integrating DataDome, you should ask Fastly Support to enable DataDome support for your Fastly service as described here.

You need to provide Terraform with your Fastly API key.
Follow the Fastly documentation to create it.

When you have your key, you must export a FASTLY_API_KEY environment variable in the shell from where you will launch Terraform commands
export FASTLY_API_KEY=<your API key>.

Next, you can open the Terraform file and edit the following sections:

  • Line 21: Input the DNS you want to use to access your service
  • Line 26: Provide a DNS or an IP to your origin backend. Warning: the backend must be named origin
provider "fastly" {}

locals {
  # Define all the datadome snippet names needed here
  datadome_snippets = toset([

# Create fastly service
resource "fastly_service_v1" "main" {
  name = "datadome_protected_service"

  domain {
    name    = ""
    comment = "Test"

  backend {
    address = ""
    name    = "origin"
    port    = 80

  # This dynamic block create a `snippet` block
  # for each datadome snippet defined in the locals
  dynamic "snippet" {
    for_each = local.datadome_snippets

    content {
      type    = snippet.value
      name    = format("datadome_%s", snippet.value)
      content = file(format("%s/%s.vcl", path.module, snippet.value))


Deploying the service for the first time

If you deploy this code for the first time, Terraform will fail on the plan stage, since the service needs to be created before we can provision the snippets code.
To deploy it for the first time you should first deploy the service and then the remaining code:

  • terraform apply -target fastly_service_v1.demo
  • terraform apply

C. Custom VCL


Before integrating DataDome VCL you should ask Fastly Support to enable DataDome support for your Fastly service as described here.

  1. Download the latest version of the module
  2. Connect to your Fastly console, and go to the Configuration tab
  3. Switch to Required Services
  4. Click configuration -> clone active

  1. Go to Origin -> Hosts
  2. Confirm that another upstream has the name origin
  3. Go to Custom VCL and click Upload your first VCL file

  1. Input name, for example datadome, and upload datadome.vcl from the distribution

  1. Click Create
  2. Go into the file and update the code at the Edit VCL block. Here you should input your API key near line 48

  1. Update Shield Backend Name with the actual name near line 460. If you don't use it, feel free to comment this line
  2. Click the Activate button on the top-right side


The Fastly module doesn't have a dedicated block for settings and you should update them in a different location in the file.

SettingLine numberComments
License key~48Your license key
TimeoutBackend configurationFastly uses standard varnish timeouts. You can find the details here
Regex~381Regex that should be matched or not matched to process the request in DataDome


This only applies to custom VCL.
If you use shielding you should update the shield backend name and the region name inside the FASTLY recv. This is region specific, and the backend name depends on your use of SSL/TLS to connect to your upstream. All theses values are actual for 2020-03-04T12:12:44Z

NameConditionBackendSSL Backend
Ashburn - BWI-BWIshield_bwi_va_usssl_shield_bwi_va_us
Ashburn - DCA-DCAshield_dca_dc_usssl_shield_dca_dc_us
Atlanta - FTY-FTYshield_fty_ga_usssl_shield_fty_ga_us
Atlanta - PDK-PDKshield_pdk_ga_usssl_shield_pdk_ga_us
Cape Town-CPTshield_cpt_capetown_zassl_shield_cpt_capetown_za
Chicago - CHI-CHIshield_chi_il_usssl_shield_chi_il_us
Chicago - MDW-MDWshield_mdw_il_usssl_shield_mdw_il_us
Chicago - PWK-PWKshield_pwk_il_usssl_shield_pwk_il_us
Dallas - DAL-DALshield_dal_tx_usssl_shield_dal_tx_us
Frankfurt - Interxion-HHNshield_hhn_frankfurt_dessl_shield_hhn_frankfurt_de
Fujairah Al Mahta-FJRshield_fjr_aessl_shield_fjr_ae
Hong Kong-HKGshield_hongkong_hkssl_shield_hongkong_hk
London - LCY-LCYshield_london_city_ukssl_shield_london_city_uk
London - LON-LONshield_lon_london_ukssl_shield_lon_london_uk
London - Slough-LHRshield_london_ukssl_shield_london_uk
Los Angeles - BUR-BURshield_bur_ca_usssl_shield_bur_ca_us
Los Angeles - LAX-LAXshield_lax_ca_usssl_shield_lax_ca_us
New York City-JFKshield_jfk_ny_usssl_shield_jfk_ny_us
New York City - LGA-LGAshield_lga_ny_usssl_shield_lga_ny_us
Palo Alto-PAOshield_pao_ca_usssl_shield_pao_ca_us
San Jose-SJCshield_sjc_ca_usssl_shield_sjc_ca_us
Sao Paulo-GRUshield_gru_br_sassl_shield_gru_br_sa
Tokyo - HND-HNDshield_hnd_tokyo_jpssl_shield_hnd_tokyo_jp


How to request Fastly to enable DataDome support?

Send an email as follows:

  • To: [email protected]
  • Subject: Pragmas needed on Service XXXXXXXXXX for DataDome support
Dear Fastly Support:

In order to enable DataDome support please set these pragmas:
• fix_unsent_body_drain
• no_body_if_bereq_is_get_or_head

on the following service:


How to log the enriched headers?

Before any setup, please read carefully our requirements about the enriched headers.

  1. Setup a real-time logging providers
  2. Edit the log format. DataDome's headers are available in the req.http object. For example req.http.x-datadome-isbot.

Please, find below an example with Loggly:

    "fastly_is_edge":%{if(fastly.ff.visits_this_service == 0, "true", "false")}V,
    "response_reason":%{if(resp.response, "%22"+json.escape(resp.response)+"%22", "null")}V,
    "host":"%{if(req.http.Fastly-Orig-Host, req.http.Fastly-Orig-Host, req.http.Host)}V",

POST requests with a body are broken

You should ask Fastly Support to enable DataDome support for your Fastly service as described here.