GSP
Quick Navigator

Search Site

Unix VPS
A - Starter
B - Basic
C - Preferred
D - Commercial
MPS - Dedicated
Previous VPSs
* Sign Up! *

Support
Contact Us
Online Help
Handbooks
Domain Status
Man Pages

FAQ
Virtual Servers
Pricing
Billing
Technical

Network
Facilities
Connectivity
Topology Map

Miscellaneous
Server Agreement
Year 2038
Credits
 

USA Flag

 

 

Man Pages
Paws::ApiGateway::Integration(3) User Contributed Perl Documentation Paws::ApiGateway::Integration(3)

Paws::ApiGateway::Integration

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".

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.

The ("id" (https://docs.aws.amazon.com/apigateway/api-reference/resource/vpc-link/#id)) of the VpcLink used for the integration when "connectionType=VPC_LINK" and undefined, otherwise.

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".

Valid values are: "INTERNET", "VPC_LINK" =head2 ContentHandling => Str

Specifies how to handle request payload content type conversions. Supported values are "CONVERT_TO_BINARY" and "CONVERT_TO_TEXT", with the following behaviors:

  • "CONVERT_TO_BINARY": Converts a request payload from a Base64-encoded string to the corresponding binary blob.
  • "CONVERT_TO_TEXT": Converts a request payload from a binary blob to a Base64-encoded string.

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.

Valid values are: "CONVERT_TO_BINARY", "CONVERT_TO_TEXT" =head2 Credentials => 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 string "arn:aws:iam::\*:user/\*". To use resource-based permissions on supported AWS services, specify null.

Specifies the integration's HTTP method type.

Specifies the integration's responses.

 GET /restapis/fugvjdxtri/resources/3kzxbg5sa2/methods/GET/integration/responses/200 HTTP/1.1 Content-Type: application/json Host: apigateway.us-east-1.amazonaws.com X-Amz-Date: 20160607T191449Z Authorization: AWS4-HMAC-SHA256 Credential={access_key_ID}/20160607/us-east-1/apigateway/aws4_request, SignedHeaders=content-type;host;x-amz-date, Signature={sig4_hash}

The successful response returns "200 OK" status and a payload as follows:

 { "_links": { "curies": { "href": "https://docs.aws.amazon.com/apigateway/latest/developerguide/restapi-integration-response-{rel}.html", "name": "integrationresponse", "templated": true }, "self": { "href": "/restapis/fugvjdxtri/resources/3kzxbg5sa2/methods/GET/integration/responses/200", "title": "200" }, "integrationresponse:delete": { "href": "/restapis/fugvjdxtri/resources/3kzxbg5sa2/methods/GET/integration/responses/200" }, "integrationresponse:update": { "href": "/restapis/fugvjdxtri/resources/3kzxbg5sa2/methods/GET/integration/responses/200" } }, "responseParameters": { "method.response.header.Content-Type": "'application/xml'" }, "responseTemplates": { "application/json": "$util.urlDecode(\"%3CkinesisStreams%3E#foreach($stream in $input.path('$.StreamNames'))%3Cstream%3E%3Cname%3E$stream%3C/name%3E%3C/stream%3E#end%3C/kinesisStreams%3E\")\n" }, "statusCode": "200" }

Creating an API (https://docs.aws.amazon.com/apigateway/latest/developerguide/how-to-create-api.html)

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.

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.

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.

Custom timeout between 50 and 29,000 milliseconds. The default value is 29,000 milliseconds or 29 seconds.

Specifies the TLS configuration for an integration.

Specifies an API method integration type. The valid value is one of the following:

  • "AWS": for integrating the API 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.
  • "AWS_PROXY": for integrating the API method request with the Lambda function-invoking action with the client request passed through as-is. This integration is also referred to as the Lambda proxy integration.
  • "HTTP": for integrating the API method request with an HTTP endpoint, including a private HTTP endpoint within a VPC. This integration is also referred to as the HTTP custom integration.
  • "HTTP_PROXY": for integrating the API method request with an HTTP endpoint, including a private HTTP endpoint within a VPC, with the client request passed through as-is. This is also referred to as the HTTP proxy integration.
  • "MOCK": for integrating the API method request with API Gateway as a "loop-back" endpoint without invoking any backend.

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.

Valid values are: "HTTP", "AWS", "MOCK", "HTTP_PROXY", "AWS_PROXY" =head2 Uri => Str

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 (https://en.wikipedia.org/wiki/Uniform_Resource_Identifier), for either standard integration, where "connectionType" is not "VPC_LINK", or private integration, where "connectionType" is "VPC_LINK". For a private HTTP integration, the URI is not used for routing.
  • 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 AWS service (e.g., "s3"); and "{subdomain}" is a designated subdomain supported by certain AWS service for fast host-name lookup. "action" can be used for an AWS 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 AWS service path-based API. The ensuing "service_api" refers to the path to an AWS service resource, including the region of the integrated AWS service, if applicable. For example, for integration with the S3 API of "GetObject (https://docs.aws.amazon.com/AmazonS3/latest/API/RESTObjectGET.html)", 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}"

2022-06-01 perl v5.40.2

Search for    or go to Top of page |  Section 3 |  Main Index

Powered by GSP Visit the GSP FreeBSD Man Page Interface.
Output converted with ManDoc.