Amazon API Gateway Extension to OpenAPI

External

• https://docs.aws.amazon.com/apigateway/latest/developerguide/api-gateway-swagger-extensions.html

Internal

• Amazon API Gateway

Organizatorium

• Example: https://docs.aws.amazon.com/apigateway/latest/developerguide/api-as-lambda-proxy-export-swagger-with-extensions.html
• Proxy Integration Example with extension and HTTP https://docs.aws.amazon.com/apigateway/latest/developerguide/setup-http-integrations.html#api-gateway-set-up-http-proxy-integration-on-proxy-resource

Extensions

x-amazon-apigateway-integration

x-amazon-apigateway-integration

Integration

'x-amazon-apigateway-integration' specifies the details of the backend integration for a specific OpenAPI operation.

type

Integration type Reference

A string that specifies the integration type with the backend:

• "http", "http_proxy" defines integration with an HTTP backend.
• "aws_proxy" defines integration with a Lambda functions, via proxy integration.
• "aws" defines integration with other AWS services or with Lambda functions, via custom integration.
• "mock" defines mock integration

passthroughBehavior

Integration passthroughBehavior Reference

A string that specifies how a request body of an unmapped content 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. Supported values:

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

requestTemplates

Integration requestTemplates Reference

x-amazon-apigateway-gateway-responses

x-amazon-apigateway-integration.responses

x-amazon-apigateway-gateway-responses:
  DEFAULT_4XX:
    responseParameters:
      gatewayresponse.header.Access-Control-Allow-Methods: "'POST,OPTIONS'"
      gatewayresponse.header.Access-Control-Allow-Origin: "'*'"
      gatewayresponse.header.Access-Control-Allow-Headers: "'Content-Type,X-Amz-Date,Authorization,X-Api-Key,X-Amz-Security-Token'"
  DEFAULT_5XX:
    responseParameters:
      gatewayresponse.header.Access-Control-Allow-Methods: "'POST,OPTIONS'"
      gatewayresponse.header.Access-Control-Allow-Origin: "'*'"
      gatewayresponse.header.Access-Control-Allow-Headers: "'Content-Type,X-Amz-Date,Authorization,X-Api-Key,X-Amz-Security-Token'"