AWS Deep Dive

author: Nathan Acks
date: 2022-11-22

Amazon API Gateway

Continued notes about the Amazon API Gateway.

Working With HTTP APIs

Transforming API Requests and Responses in API Gateway

HTTP APIs can modify inbound requests and outbound responses, but in much more limited ways than REST APIs.

Inbound requests can have their headers, query string (if applicable), and path modified. While request bodies cannot be modified, API Gateway can extract values from them (or at least from the first 100 KB).

Outbound responses can have their headers and status codes modified. As with inbound requests, the response body can be used as a data source, even if it can’t be modified.

Working with OpenAPI Definitions for HTTP APIs in API Gateway

As with REST APIs, HTTP APIs can be exported and imported to OpenAPI 3.0 definition files. The import/export process can even be used to “convert” a REST API into an HTTP API, though not all REST API attributes (for example, request validation) will be imported (since HTTP APIs don’t have all of the same features).

Working with Stages for HTTP APIs in API Gateway

Stage variables work more-or-less the same for HTTP APIs as they do for REST APIs.

Setting Up Custom Domain Names for HTTP APIs in API Gateway

Custom domains work more-or-less the same for HTTP APIs as they do for REST APIs (modulo the absence of $context variables).