Amazon API Gateway data mapping in HTTP APIs

[ewbankkit]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description

Amazon API Gateway now supports data mapping definitions from an HTTP API’s method request data (e.g. path parameters, query string and headers) to the corresponding integration request parameters and from the integration response data (e.g. headers) to the HTTP API method response parameters.

New or Affected Resource(s)

• aws_apigatewayv2_integration

Potential Terraform Configuration

The API's ResponseParameters field is a nested map of type map[string]map[string]*string and Terraform does not support nested maps, so we define response_parameter as a repeating block (TypeSet).

resource "aws_apigatewayv2_integration" "example" {
  request_parameters = {
    "append:header.header2" = "$request.header.header1"
    "remove:header.header1" = "''"
  }

  response_parameters {
    status_code = "500"

    mappings = {
      "append:header.header1" = "$context.requestId"
      "overwrite:statuscode"  = "403"
    }
  }

  response_parameters {
    status_code = "404"

    mappings = {
      "append:header.error" = "$stageVariables.environmentId"
    }
  }
}

References

Announcement.

Requires AWS SDK v1.36.17:

• build(deps): bump github.com/aws/aws-sdk-go from 1.36.12 to 1.36.19 #16934

[ghost]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks!