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. Dynamic 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 main.tf Terraform file and edit the following sections:

• Line 20: Input the DNS you want to use to access your service
• Line 25: Provide a DNS or an IP to your origin backend. Warning: the backend must be named origin
• Line 37: OPTIONAL Fastly defines a default priority of 100 for each snippet. You can add a priority field here to override this value. You can see Terraform doc here

# main.tf
provider "fastly" {}

locals {
    # We define all the snippets name that we need to include here
  datadome_snippets = toset([
    "init",
    "recv",
    "pass",
    "fetch",
    "deliver",
    "miss"
  ])
}

# Create a Service
resource "fastly_service_v1" "main" {
  name = "datadome_protected_service"

  domain {
    name    = "<URL of your service>"
    comment = "Test"
  }

  backend {
    address = "<URL to your backend>"
    name    = "origin"
    port    = 80
  }

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

    content {
      name = format("datadome_%s", dynamicsnippet.value)
      type = dynamicsnippet.value
    }
  }

  force_destroy = true
}

# Here we provide the resource that send the snippet code to Fastly
# We create a resource for each datadome snippet.
# In the snippet_id argument, we recuperate it from the
# `dynamicsnippet` attribute on the service
resource "fastly_service_dynamic_snippet_content_v1" "datadome_snippets" {
  for_each = local.datadome_snippets

  service_id = fastly_service_v1.main.id
  snippet_id = { for s in fastly_service_v1.main.dynamicsnippet : s.name => s.snippet_id }[format("datadome_%s", each.value)]

  content = file("${path.module}/${each.value}.vcl")

  depends_on = [fastly_service_v1.main]
}

🚧

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

6. Go to Origin -> Hosts
7. Confirm that another upstream has the name origin
8. Go to Custom VCL and click Upload your first VCL file

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

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

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

Settings

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

Shielding

If you use shielding you should update the shield backend name and the region name at the if condition. 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

FAQ

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