Behaviors are instructions for Akamai edge servers that manage client requests based on set criteria. The availability of behaviors depends on your Akamai product and services.

Behaviors also belong to a specific rule format version. To use behaviors, you must use a rule format no earlier than v2023-01-05.

As newer behaviors are not backward compatible, check your rule format against the date located at the top of a behavior's reference page and update your rule format as needed.



The Terraform VS Code Extension includes a dynamic edit feature that pulls in Property documentation and provides a list of available behaviors and match criteria.

Add behaviors

A list of all behaviors and criteria can be found in the reference section.

  1. Get your rule tree. You can use an existing one or create a new property and use the default set of rules.

  2. Choose behaviors to add, paying attention to any parent/child relationships mentioned on a reference page as some behaviors are dependent on others or on specific rules being present in your tree.

  3. Add your new behavior to your new rule tree as described on its reference page. The example here adds the downstreamCache behavior and cacheability criteria to the Dynamic Content rule.

      "name": "Dynamic Content",
      "children": [],
      "behaviors": [
          "name": "downstreamCache",
          "options": {
              "behavior": "TUNNEL_ORIGIN"
    "criteria": [
          "name": "cacheability",
          "options": {
              "matchOperator": "IS_NOT",
              "value": "CACHEABLE"
      "criteriaMustSatisfy": "all"
  4. Add your changes to your configuration with the property resource.

    resource "akamai_property" "my-property-behaviors" {
      name        = "My new property rule behaviors"
      product_id  = "prd_SPM"
      contract_id = var.contractid
      group_id    = var.groupid
      rule_format = "v2023-01-05"
      rules       = file("${path.root}/property-snippets/main.json") 
  5. Run terraform plan to check your syntax and then terraform apply to push your changes to the network. We recommend doing this in staging first, applying changes for the production environment after you've tested.


Pushing changes to your rule tree automatically revises the version of your property configuration to the next major version.