CfnIntegrationProps
- class aws_cdk.aws_apigatewayv2.CfnIntegrationProps(*, api_id, integration_type, connection_id=None, connection_type=None, content_handling_strategy=None, credentials_arn=None, description=None, integration_method=None, integration_subtype=None, integration_uri=None, passthrough_behavior=None, payload_format_version=None, request_parameters=None, request_templates=None, response_parameters=None, template_selection_expression=None, timeout_in_millis=None, tls_config=None)
Bases:
object
Properties for defining a
CfnIntegration
.- Parameters:
api_id (
str
) – The API identifier.integration_type (
str
) – The integration type of an integration. One of the following:.AWS
: for integrating the route or method request with an AWS service action, including the Lambda function-invoking action. With the Lambda function-invoking action, this is referred to as the Lambda custom integration. With any other AWS service action, this is known as AWS integration. Supported only for WebSocket APIs.AWS_PROXY
: for integrating the route or method request with a Lambda function or other AWS service action. This integration is also referred to as a Lambda proxy integration.HTTP
: for integrating the route or method request with an HTTP endpoint. This integration is also referred to as the HTTP custom integration. Supported only for WebSocket APIs.HTTP_PROXY
: for integrating the route or method request with an HTTP endpoint, with the client request passed through as-is. This is also referred to as HTTP proxy integration. For HTTP API private integrations, use anHTTP_PROXY
integration.MOCK
: for integrating the route or method request with API Gateway as a “loopback” endpoint without invoking any backend. Supported only for WebSocket APIs.connection_id (
Optional
[str
]) – The ID of the VPC link for a private integration. Supported only for HTTP APIs.connection_type (
Optional
[str
]) – The type of the network connection to the integration endpoint. SpecifyINTERNET
for connections through the public routable internet orVPC_LINK
for private connections between API Gateway and resources in a VPC. The default value isINTERNET
.content_handling_strategy (
Optional
[str
]) – Supported only for WebSocket APIs. Specifies how to handle response payload content type conversions. Supported values areCONVERT_TO_BINARY
andCONVERT_TO_TEXT
, with the following behaviors:CONVERT_TO_BINARY
: Converts a response payload from a Base64-encoded string to the corresponding binary blob.CONVERT_TO_TEXT
: Converts a response payload from a binary blob to a Base64-encoded string. If this property is not defined, the response payload will be passed through from the integration response to the route response or method response without modification.credentials_arn (
Optional
[str
]) – 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 stringarn:aws:iam::*:user/*
. To use resource-based permissions on supported AWS services, don’t specify this parameter.description (
Optional
[str
]) – The description of the integration.integration_method (
Optional
[str
]) – Specifies the integration’s HTTP method type. For WebSocket APIs, if you use a Lambda integration, you must set the integration method toPOST
.integration_subtype (
Optional
[str
]) – Supported only for HTTP APIAWS_PROXY
integrations. Specifies the AWS service action to invoke. To learn more, see Integration subtype reference .integration_uri (
Optional
[str
]) – For a Lambda integration, specify the URI of a Lambda function. For an HTTP integration, specify a fully-qualified URL. For an HTTP API private integration, specify the ARN of an Application Load Balancer listener, Network Load Balancer listener, or AWS Cloud Map service. If you specify the ARN of an AWS Cloud Map service, API Gateway usesDiscoverInstances
to identify resources. You can use query parameters to target specific resources. To learn more, see DiscoverInstances . For private integrations, all resources must be owned by the same AWS account .passthrough_behavior (
Optional
[str
]) – Specifies the pass-through behavior for incoming requests based on theContent-Type
header in the request, and the available mapping templates specified as therequestTemplates
property on theIntegration
resource. There are three valid values:WHEN_NO_MATCH
,WHEN_NO_TEMPLATES
, andNEVER
. Supported only for WebSocket APIs.WHEN_NO_MATCH
passes the request body for unmapped content types through to the integration backend without transformation.NEVER
rejects unmapped content types with anHTTP 415 Unsupported Media Type
response.WHEN_NO_TEMPLATES
allows pass-through when the integration has no content types mapped to templates. However, if there is at least one content type defined, unmapped content types will be rejected with the sameHTTP 415 Unsupported Media Type
response.payload_format_version (
Optional
[str
]) – Specifies the format of the payload sent to an integration. Required for HTTP APIs. For HTTP APIs, supported values for Lambda proxy integrations are1.0
and2.0
. For all other integrations,1.0
is the only supported value. To learn more, see Working with AWS Lambda proxy integrations for HTTP APIs .request_parameters (
Any
) – For WebSocket APIs, a key-value map specifying request parameters that are passed from the method request to the backend. 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 backend. The method request parameter value must match the pattern ofmethod.request. {location} . {name}
, where{location}
isquerystring
,path
, orheader
; and{name}
must be a valid and unique method request parameter name. For HTTP API integrations with a specifiedintegrationSubtype
, request parameters are a key-value map specifying parameters that are passed toAWS_PROXY
integrations. You can provide static values, or map request data, stage variables, or context variables that are evaluated at runtime. To learn more, see Working with AWS service integrations for HTTP APIs . For HTTP API integrations without a specifiedintegrationSubtype
request parameters are a key-value map specifying how to transform HTTP requests before sending them to the backend. The key should follow the pattern :<header|querystring|path>. where action can beappend
,overwrite
orremove
. For values, you can provide static values, or map request data, stage variables, or context variables that are evaluated at runtime. To learn more, see Transforming API requests and responses .request_templates (
Any
) – 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. Supported only for WebSocket APIs.response_parameters (
Any
) –Supported only for HTTP APIs. You use response parameters to transform the HTTP response from a backend integration before returning the response to clients. Specify a key-value map from a selection key to response parameters. The selection key must be a valid HTTP status code within the range of 200-599. The value is of type
`ResponseParameterList
<https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-apigatewayv2-integration-responseparameterlist.html>`_ . To learn more, see Transforming API requests and responses .template_selection_expression (
Optional
[str
]) – The template selection expression for the integration. Supported only for WebSocket APIs.timeout_in_millis (
Union
[int
,float
,None
]) – Custom timeout between 50 and 29,000 milliseconds for WebSocket APIs and between 50 and 30,000 milliseconds for HTTP APIs. The default timeout is 29 seconds for WebSocket APIs and 30 seconds for HTTP APIs.tls_config (
Union
[IResolvable
,TlsConfigProperty
,Dict
[str
,Any
],None
]) – The TLS configuration for a private integration. If you specify a TLS configuration, private integration traffic uses the HTTPS protocol. Supported only for HTTP APIs.
- See:
- ExampleMetadata:
fixture=_generated
Example:
# The code below shows an example of how to instantiate this type. # The values are placeholders you should change. from aws_cdk import aws_apigatewayv2 as apigatewayv2 # request_parameters: Any # request_templates: Any # response_parameters: Any cfn_integration_props = apigatewayv2.CfnIntegrationProps( api_id="apiId", integration_type="integrationType", # the properties below are optional connection_id="connectionId", connection_type="connectionType", content_handling_strategy="contentHandlingStrategy", credentials_arn="credentialsArn", description="description", integration_method="integrationMethod", integration_subtype="integrationSubtype", integration_uri="integrationUri", passthrough_behavior="passthroughBehavior", payload_format_version="payloadFormatVersion", request_parameters=request_parameters, request_templates=request_templates, response_parameters=response_parameters, template_selection_expression="templateSelectionExpression", timeout_in_millis=123, tls_config=apigatewayv2.CfnIntegration.TlsConfigProperty( server_name_to_verify="serverNameToVerify" ) )
Attributes
- api_id
The API identifier.
- connection_id
The ID of the VPC link for a private integration.
Supported only for HTTP APIs.
- connection_type
The type of the network connection to the integration endpoint.
Specify
INTERNET
for connections through the public routable internet orVPC_LINK
for private connections between API Gateway and resources in a VPC. The default value isINTERNET
.
- content_handling_strategy
Supported only for WebSocket APIs.
Specifies how to handle response payload content type conversions. Supported values are
CONVERT_TO_BINARY
andCONVERT_TO_TEXT
, with the following behaviors:CONVERT_TO_BINARY
: Converts a response payload from a Base64-encoded string to the corresponding binary blob.CONVERT_TO_TEXT
: Converts a response payload from a binary blob to a Base64-encoded string.If this property is not defined, the response payload will be passed through from the integration response to the route response or method response without modification.
- credentials_arn
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 AWS services, don’t specify this parameter.
- description
The description of the integration.
- integration_method
Specifies the integration’s HTTP method type.
For WebSocket APIs, if you use a Lambda integration, you must set the integration method to
POST
.
- integration_subtype
Supported only for HTTP API
AWS_PROXY
integrations.Specifies the AWS service action to invoke. To learn more, see Integration subtype reference .
- integration_type
.
AWS
: for integrating the route or method request with an AWS service action, including the Lambda function-invoking action. With the Lambda function-invoking action, this is referred to as the Lambda custom integration. With any other AWS service action, this is known as AWS integration. Supported only for WebSocket APIs.AWS_PROXY
: for integrating the route or method request with a Lambda function or other AWS service action. This integration is also referred to as a Lambda proxy integration.HTTP
: for integrating the route or method request with an HTTP endpoint. This integration is also referred to as the HTTP custom integration. Supported only for WebSocket APIs.HTTP_PROXY
: for integrating the route or method request with an HTTP endpoint, with the client request passed through as-is. This is also referred to as HTTP proxy integration. For HTTP API private integrations, use anHTTP_PROXY
integration.MOCK
: for integrating the route or method request with API Gateway as a “loopback” endpoint without invoking any backend. Supported only for WebSocket APIs.- See:
- Type:
The integration type of an integration. One of the following
- integration_uri
For a Lambda integration, specify the URI of a Lambda function.
For an HTTP integration, specify a fully-qualified URL.
For an HTTP API private integration, specify the ARN of an Application Load Balancer listener, Network Load Balancer listener, or AWS Cloud Map service. If you specify the ARN of an AWS Cloud Map service, API Gateway uses
DiscoverInstances
to identify resources. You can use query parameters to target specific resources. To learn more, see DiscoverInstances . For private integrations, all resources must be owned by the same AWS account .
- passthrough_behavior
Specifies the pass-through behavior for incoming requests based on the
Content-Type
header in the request, and the available mapping templates specified as therequestTemplates
property on theIntegration
resource.There are three valid values:
WHEN_NO_MATCH
,WHEN_NO_TEMPLATES
, andNEVER
. Supported only for WebSocket APIs.WHEN_NO_MATCH
passes the request body for unmapped content types through to the integration backend without transformation.NEVER
rejects unmapped content types with anHTTP 415 Unsupported Media Type
response.WHEN_NO_TEMPLATES
allows pass-through when the integration has no content types mapped to templates. However, if there is at least one content type defined, unmapped content types will be rejected with the sameHTTP 415 Unsupported Media Type
response.
- payload_format_version
Specifies the format of the payload sent to an integration.
Required for HTTP APIs. For HTTP APIs, supported values for Lambda proxy integrations are
1.0
and2.0
. For all other integrations,1.0
is the only supported value. To learn more, see Working with AWS Lambda proxy integrations for HTTP APIs .
- request_parameters
For WebSocket APIs, a key-value map specifying request parameters that are passed from the method request to the backend.
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 backend. The method request parameter value must match the pattern of
method.request. {location} . {name}
, where{location}
isquerystring
,path
, orheader
; and{name}
must be a valid and unique method request parameter name.For HTTP API integrations with a specified
integrationSubtype
, request parameters are a key-value map specifying parameters that are passed toAWS_PROXY
integrations. You can provide static values, or map request data, stage variables, or context variables that are evaluated at runtime. To learn more, see Working with AWS service integrations for HTTP APIs .For HTTP API integrations without a specified
integrationSubtype
request parameters are a key-value map specifying how to transform HTTP requests before sending them to the backend. The key should follow the pattern :<header|querystring|path>. where action can beappend
,overwrite
orremove
. For values, you can provide static values, or map request data, stage variables, or context variables that are evaluated at runtime. To learn more, see Transforming API requests and responses .
- request_templates
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. Supported only for WebSocket APIs.
- response_parameters
Supported only for HTTP APIs.
You use response parameters to transform the HTTP response from a backend integration before returning the response to clients. Specify a key-value map from a selection key to response parameters. The selection key must be a valid HTTP status code within the range of 200-599. The value is of type
`ResponseParameterList
<https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-apigatewayv2-integration-responseparameterlist.html>`_ . To learn more, see Transforming API requests and responses .
- template_selection_expression
The template selection expression for the integration.
Supported only for WebSocket APIs.
- timeout_in_millis
Custom timeout between 50 and 29,000 milliseconds for WebSocket APIs and between 50 and 30,000 milliseconds for HTTP APIs.
The default timeout is 29 seconds for WebSocket APIs and 30 seconds for HTTP APIs.
- tls_config
The TLS configuration for a private integration.
If you specify a TLS configuration, private integration traffic uses the HTTPS protocol. Supported only for HTTP APIs.