---
title: Getting Started with Datadog
description: Datadog, the leading service for cloud-scale monitoring.
breadcrumbs: Docs > Infrastructure > Datadog Resource Catalog
---

# aws_cloudfront_cache_policy{% #aws_cloudfront_cache_policy %}

## `account_id`{% #account_id %}

**Type**: `STRING`

## `cache_policy`{% #cache_policy %}

**Type**: `STRUCT`**Provider name**: `CachePolicy`**Description**: The cache policy.

- `cache_policy_config`**Type**: `STRUCT`**Provider name**: `CachePolicyConfig`**Description**: The cache policy configuration.
  - `comment`**Type**: `STRING`**Provider name**: `Comment`**Description**: A comment to describe the cache policy. The comment cannot be longer than 128 characters.
  - `default_ttl`**Type**: `INT64`**Provider name**: `DefaultTTL`**Description**: The default amount of time, in seconds, that you want objects to stay in the CloudFront cache before CloudFront sends another request to the origin to see if the object has been updated. CloudFront uses this value as the object's time to live (TTL) only when the origin does not send `Cache-Control` or `Expires` headers with the object. For more information, see [Managing How Long Content Stays in an Edge Cache (Expiration)](https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/Expiration.html) in the Amazon CloudFront Developer Guide. The default value for this field is 86400 seconds (one day). If the value of `MinTTL` is more than 86400 seconds, then the default value for this field is the same as the value of `MinTTL`.
  - `max_ttl`**Type**: `INT64`**Provider name**: `MaxTTL`**Description**: The maximum amount of time, in seconds, that objects stay in the CloudFront cache before CloudFront sends another request to the origin to see if the object has been updated. CloudFront uses this value only when the origin sends `Cache-Control` or `Expires` headers with the object. For more information, see [Managing How Long Content Stays in an Edge Cache (Expiration)](https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/Expiration.html) in the Amazon CloudFront Developer Guide. The default value for this field is 31536000 seconds (one year). If the value of `MinTTL` or `DefaultTTL` is more than 31536000 seconds, then the default value for this field is the same as the value of `DefaultTTL`.
  - `min_ttl`**Type**: `INT64`**Provider name**: `MinTTL`**Description**: The minimum amount of time, in seconds, that you want objects to stay in the CloudFront cache before CloudFront sends another request to the origin to see if the object has been updated. For more information, see [Managing How Long Content Stays in an Edge Cache (Expiration)](https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/Expiration.html) in the Amazon CloudFront Developer Guide.
  - `name`**Type**: `STRING`**Provider name**: `Name`**Description**: A unique name to identify the cache policy.
  - `parameters_in_cache_key_and_forwarded_to_origin`**Type**: `STRUCT`**Provider name**: `ParametersInCacheKeyAndForwardedToOrigin`**Description**: The HTTP headers, cookies, and URL query strings to include in the cache key. The values included in the cache key are also included in requests that CloudFront sends to the origin.
    - `cookies_config`**Type**: `STRUCT`**Provider name**: `CookiesConfig`**Description**: An object that determines whether any cookies in viewer requests (and if so, which cookies) are included in the cache key and in requests that CloudFront sends to the origin.
      - `cookie_behavior`**Type**: `STRING`**Provider name**: `CookieBehavior`**Description**: Determines whether any cookies in viewer requests are included in the cache key and in requests that CloudFront sends to the origin. Valid values are:
        - `none` – No cookies in viewer requests are included in the cache key or in requests that CloudFront sends to the origin. Even when this field is set to `none`, any cookies that are listed in an `OriginRequestPolicy` are included in origin requests.
        - `whitelist` – Only the cookies in viewer requests that are listed in the `CookieNames` type are included in the cache key and in requests that CloudFront sends to the origin.
        - `allExcept` – All cookies in viewer requests are included in the cache key and in requests that CloudFront sends to the origin, except for those that are listed in the `CookieNames` type, which are not included.
        - `all` – All cookies in viewer requests are included in the cache key and in requests that CloudFront sends to the origin.
      - `cookies`**Type**: `STRUCT`**Provider name**: `Cookies`
        - `items`**Type**: `UNORDERED_LIST_STRING`**Provider name**: `Items`**Description**: A list of cookie names.
        - `quantity`**Type**: `INT32`**Provider name**: `Quantity`**Description**: The number of cookie names in the `Items` list.
    - `enable_accept_encoding_brotli`**Type**: `BOOLEAN`**Provider name**: `EnableAcceptEncodingBrotli`**Description**: A flag that can affect whether the `Accept-Encoding` HTTP header is included in the cache key and included in requests that CloudFront sends to the origin. This field is related to the `EnableAcceptEncodingGzip` field. If one or both of these fields is `true` and the viewer request includes the `Accept-Encoding` header, then CloudFront does the following:
      - Normalizes the value of the viewer's `Accept-Encoding` header
      - Includes the normalized header in the cache key
      - Includes the normalized header in the request to the origin, if a request is necessary
For more information, see [Compression support](https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/controlling-the-cache-key.html#cache-policy-compressed-objects) in the Amazon CloudFront Developer Guide. If you set this value to `true`, and this cache behavior also has an origin request policy attached, do not include the `Accept-Encoding` header in the origin request policy. CloudFront always includes the `Accept-Encoding` header in origin requests when the value of this field is `true`, so including this header in an origin request policy has no effect. If both of these fields are `false`, then CloudFront treats the `Accept-Encoding` header the same as any other HTTP header in the viewer request. By default, it's not included in the cache key and it's not included in origin requests. In this case, you can manually add `Accept-Encoding` to the headers whitelist like any other HTTP header.
    - `enable_accept_encoding_gzip`**Type**: `BOOLEAN`**Provider name**: `EnableAcceptEncodingGzip`**Description**: A flag that can affect whether the `Accept-Encoding` HTTP header is included in the cache key and included in requests that CloudFront sends to the origin. This field is related to the `EnableAcceptEncodingBrotli` field. If one or both of these fields is `true` and the viewer request includes the `Accept-Encoding` header, then CloudFront does the following:
      - Normalizes the value of the viewer's `Accept-Encoding` header
      - Includes the normalized header in the cache key
      - Includes the normalized header in the request to the origin, if a request is necessary
For more information, see [Compression support](https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/controlling-the-cache-key.html#cache-policy-compressed-objects) in the Amazon CloudFront Developer Guide. If you set this value to `true`, and this cache behavior also has an origin request policy attached, do not include the `Accept-Encoding` header in the origin request policy. CloudFront always includes the `Accept-Encoding` header in origin requests when the value of this field is `true`, so including this header in an origin request policy has no effect. If both of these fields are `false`, then CloudFront treats the `Accept-Encoding` header the same as any other HTTP header in the viewer request. By default, it's not included in the cache key and it's not included in origin requests. In this case, you can manually add `Accept-Encoding` to the headers whitelist like any other HTTP header.
    - `headers_config`**Type**: `STRUCT`**Provider name**: `HeadersConfig`**Description**: An object that determines whether any HTTP headers (and if so, which headers) are included in the cache key and in requests that CloudFront sends to the origin.
      - `header_behavior`**Type**: `STRING`**Provider name**: `HeaderBehavior`**Description**: Determines whether any HTTP headers are included in the cache key and in requests that CloudFront sends to the origin. Valid values are:
        - `none` – No HTTP headers are included in the cache key or in requests that CloudFront sends to the origin. Even when this field is set to `none`, any headers that are listed in an `OriginRequestPolicy` are included in origin requests.
        - `whitelist` – Only the HTTP headers that are listed in the `Headers` type are included in the cache key and in requests that CloudFront sends to the origin.
      - `headers`**Type**: `STRUCT`**Provider name**: `Headers`
        - `items`**Type**: `UNORDERED_LIST_STRING`**Provider name**: `Items`**Description**: A list of HTTP header names.
        - `quantity`**Type**: `INT32`**Provider name**: `Quantity`**Description**: The number of header names in the `Items` list.
    - `query_strings_config`**Type**: `STRUCT`**Provider name**: `QueryStringsConfig`**Description**: An object that determines whether any URL query strings in viewer requests (and if so, which query strings) are included in the cache key and in requests that CloudFront sends to the origin.
      - `query_string_behavior`**Type**: `STRING`**Provider name**: `QueryStringBehavior`**Description**: Determines whether any URL query strings in viewer requests are included in the cache key and in requests that CloudFront sends to the origin. Valid values are:
        - `none` – No query strings in viewer requests are included in the cache key or in requests that CloudFront sends to the origin. Even when this field is set to `none`, any query strings that are listed in an `OriginRequestPolicy` are included in origin requests.
        - `whitelist` – Only the query strings in viewer requests that are listed in the `QueryStringNames` type are included in the cache key and in requests that CloudFront sends to the origin.
        - `allExcept` – All query strings in viewer requests are included in the cache key and in requests that CloudFront sends to the origin, except those that are listed in the `QueryStringNames` type, which are not included.
        - `all` – All query strings in viewer requests are included in the cache key and in requests that CloudFront sends to the origin.
      - `query_strings`**Type**: `STRUCT`**Provider name**: `QueryStrings`**Description**: Contains the specific query strings in viewer requests that either are or are not included in the cache key and in requests that CloudFront sends to the origin. The behavior depends on whether the `QueryStringBehavior` field in the `CachePolicyQueryStringsConfig` type is set to `whitelist` (the listed query strings are included) or `allExcept` (the listed query strings are not included, but all other query strings are).
        - `items`**Type**: `UNORDERED_LIST_STRING`**Provider name**: `Items`**Description**: A list of query string names.
        - `quantity`**Type**: `INT32`**Provider name**: `Quantity`**Description**: The number of query string names in the `Items` list.
- `id`**Type**: `STRING`**Provider name**: `Id`**Description**: The unique identifier for the cache policy.
- `last_modified_time`**Type**: `TIMESTAMP`**Provider name**: `LastModifiedTime`**Description**: The date and time when the cache policy was last modified.

## `e_tag`{% #e_tag %}

**Type**: `STRING`**Provider name**: `ETag`**Description**: The current version of the cache policy.

## `tags`{% #tags %}

**Type**: `UNORDERED_LIST_STRING`