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

# aws_apigateway_integration{% #aws_apigateway_integration %}

## `account_id`{% #account_id %}

**Type**: `STRING`

## `cache_key_parameters`{% #cache_key_parameters %}

**Type**: `UNORDERED_LIST_STRING`**Provider name**: `cacheKeyParameters`**Description**: A list of request parameters whose values API Gateway caches. To be valid values for `cacheKeyParameters`, these parameters must also be specified for Method `requestParameters`.

## `cache_namespace`{% #cache_namespace %}

**Type**: `STRING`**Provider name**: `cacheNamespace`**Description**: Specifies a group of related cached parameters. By default, API Gateway uses the resource ID as the `cacheNamespace`. You can specify the same `cacheNamespace` across resources to return the same cached data for requests to different resources.

## `connection_id`{% #connection_id %}

**Type**: `STRING`**Provider name**: `connectionId`**Description**: The ID of the VpcLink used for the integration when `connectionType=VPC_LINK` and undefined, otherwise.

## `connection_type`{% #connection_type %}

**Type**: `STRING`**Provider name**: `connectionType`**Description**: The type of the network connection to the integration endpoint. The valid value is `INTERNET` for connections through the public routable internet or `VPC_LINK` for private connections between API Gateway and a network load balancer in a VPC. The default value is `INTERNET`.

## `content_handling`{% #content_handling %}

**Type**: `STRING`**Provider name**: `contentHandling`**Description**: Specifies how to handle request payload content type conversions. Supported values are `CONVERT_TO_BINARY` and `CONVERT_TO_TEXT`, with the following behaviors: If this property is not defined, the request payload will be passed through from the method request to integration request without modification, provided that the `passthroughBehavior` is configured to support payload pass-through.

## `credentials`{% #credentials %}

**Type**: `STRING`**Provider name**: `credentials`**Description**: Specifies the credentials required for the integration, if any. For AWS integrations, three options are available. To specify an IAM Role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To require that the caller's identity be passed through from the request, specify the string `arn:aws:iam::*:user/*`. To use resource-based permissions on supported Amazon Web Services services, specify null.

## `http_method`{% #http_method %}

**Type**: `STRING`**Provider name**: `httpMethod`**Description**: Specifies the integration's HTTP method type. For the Type property, if you specify `MOCK`, this property is optional. For Lambda integrations, you must set the integration method to `POST`. For all other types, you must specify this property.

## `integration_arn`{% #integration_arn %}

**Type**: `STRING`

## `integration_responses`{% #integration_responses %}

**Type**: `STRING`**Provider name**: `integrationResponses`**Description**: Specifies the integration's responses.

## `passthrough_behavior`{% #passthrough_behavior %}

**Type**: `STRING`**Provider name**: `passthroughBehavior`**Description**: Specifies how the method request body of an unmapped content type will be passed through the integration request to the back end without transformation. A content type is unmapped if no mapping template is defined in the integration or the content type does not match any of the mapped content types, as specified in `requestTemplates`. The valid value is one of the following: `WHEN_NO_MATCH`: passes the method request body through the integration request to the back end without transformation when the method request content type does not match any content type associated with the mapping templates defined in the integration request. `WHEN_NO_TEMPLATES`: passes the method request body through the integration request to the back end without transformation when no mapping template is defined in the integration request. If a template is defined when this option is selected, the method request of an unmapped content-type will be rejected with an HTTP 415 Unsupported Media Type response. `NEVER`: rejects the method request with an HTTP 415 Unsupported Media Type response when either the method request content type does not match any content type associated with the mapping templates defined in the integration request or no mapping template is defined in the integration request.

## `request_parameters`{% #request_parameters %}

**Type**: `MAP_STRING_STRING`**Provider name**: `requestParameters`**Description**: A key-value map specifying request parameters that are passed from the method request to the back end. The key is an integration request parameter name and the associated value is a method request parameter value or static value that must be enclosed within single quotes and pre-encoded as required by the back end. The method request parameter value must match the pattern of `method.request.{location}.{name}`, where `location` is `querystring`, `path`, or `header` and `name` must be a valid and unique method request parameter name.

## `request_templates`{% #request_templates %}

**Type**: `MAP_STRING_STRING`**Provider name**: `requestTemplates`**Description**: Represents a map of Velocity templates that are applied on the request payload based on the value of the Content-Type header sent by the client. The content type value is the key in this map, and the template (as a String) is the value.

## `tags`{% #tags %}

**Type**: `UNORDERED_LIST_STRING`

## `timeout_in_millis`{% #timeout_in_millis %}

**Type**: `INT32`**Provider name**: `timeoutInMillis`**Description**: Custom timeout between 50 and 29,000 milliseconds. The default value is 29,000 milliseconds or 29 seconds.

## `tls_config`{% #tls_config %}

**Type**: `STRUCT`**Provider name**: `tlsConfig`**Description**: Specifies the TLS configuration for an integration.

- `insecure_skip_verification`**Type**: `BOOLEAN`**Provider name**: `insecureSkipVerification`**Description**: Specifies whether or not API Gateway skips verification that the certificate for an integration endpoint is issued by a supported certificate authority. This isn't recommended, but it enables you to use certificates that are signed by private certificate authorities, or certificates that are self-signed. If enabled, API Gateway still performs basic certificate validation, which includes checking the certificate's expiration date, hostname, and presence of a root certificate authority. Supported only for `HTTP` and `HTTP_PROXY` integrations.Enabling `insecureSkipVerification` isn't recommended, especially for integrations with public HTTPS endpoints. If you enable `insecureSkipVerification`, you increase the risk of man-in-the-middle attacks.

## `type`{% #type %}

**Type**: `STRING`**Provider name**: `type`**Description**: Specifies an API method integration type. The valid value is one of the following: For the HTTP and HTTP proxy integrations, each integration can specify a protocol (`http/https`), port and path. Standard 80 and 443 ports are supported as well as custom ports above 1024. An HTTP or HTTP proxy integration with a `connectionType` of `VPC_LINK` is referred to as a private integration and uses a VpcLink to connect API Gateway to a network load balancer of a VPC.

## `uri`{% #uri %}

**Type**: `STRING`**Provider name**: `uri`**Description**: Specifies Uniform Resource Identifier (URI) of the integration endpoint. For `HTTP` or `HTTP_PROXY` integrations, the URI must be a fully formed, encoded HTTP(S) URL according to the RFC-3986 specification for standard integrations. If `connectionType` is `VPC_LINK` specify the Network Load Balancer DNS name. For `AWS` or `AWS_PROXY` integrations, the URI is of the form `arn:aws:apigateway:{region}:{subdomain.service|service}:path|action/{service_api}`. Here, {Region} is the API Gateway region (e.g., us-east-1); {service} is the name of the integrated Amazon Web Services service (e.g., s3); and {subdomain} is a designated subdomain supported by certain Amazon Web Services service for fast host-name lookup. action can be used for an Amazon Web Services service action-based API, using an Action={name}&{p1}={v1}&p2={v2}… query string. The ensuing {service_api} refers to a supported action {name} plus any required input parameters. Alternatively, path can be used for an Amazon Web Services service path-based API. The ensuing service_api refers to the path to an Amazon Web Services service resource, including the region of the integrated Amazon Web Services service, if applicable. For example, for integration with the S3 API of GetObject, the uri can be either `arn:aws:apigateway:us-west-2:s3:action/GetObject&Bucket={bucket}&Key={key}` or `arn:aws:apigateway:us-west-2:s3:path/{bucket}/{key}`