Amazon API Gateway Now Features Content Encoding Support for API Responses

Amazon has added content encoding support for API responses in its API Gateway product. Content encoding allows clients to call APIs with compressed payloads. Developers can configure their APIs to support content encodings such as deflate, gzip, and identity. Clients can then request that content be compressed before it is sent back in the API response. By enabling content encoding in the API definition, the amount of data sent from the API Gateway to API clients is reduced and transferring data takes less time. Developers must configure their APIs so that compression is enabled because content encoding support is disabled by default.

Amazon API Gateway is a managed service for creating, publishing, maintaining, and monitoring APIs. Using the AWS Management Console, developers can create APIs that serve as a gateway for applications to access data and functionality from back-end services. These APIs can access back-end services running on AWS Compute products such as Amazon EC2 and AWS Lambda or from any type of web application. The Amazon API Gateway handles traffic management, monitoring, and many of the other tasks required to process and accept concurrent API calls at scale. Developers can also use the gateway to create RESTful endpoints for existing services and create server-less APIs (with the help of Amazon Lambda).

For more information about the Amazon API Gateway, visit the official product page.

Be sure to read the next API Design article: Coursera Dogfoods REST-to-GraphQL Translation Tool


Comments (0)