Advanced API Gateway

Import APIs

You can use the API Gateway Import API feature to import an API feature to import an aPI from the external definition file into API gateway. Currently, the import API feature supports Swagger v2.0 definition files

With the Import API, you can either create a new API by submitting a POST request that includes a Swagger definition in the payload and endpoint configuration, or you can update an existing API by using a PUT request that contains a Swagger definition in the payload. You can update an API by overwriting it with a new definition, or merge a definition with an existing API. You specifcy the options using a mode query parameter in the request URL.

REMEMBER: YOU CAN IMPORT APIS USING SWAGGER FILES

API Throttling

By default, API Gateway limits the steady-state request rate to 10,000 requests per second(rps).

The Maximum concurrent requests is 5,000 requests across all APIs within an AWS account If you go over 10,000 requests per second or 5,000 concurrent requests you will recieve a 429 Too Many Request error response

  • If a caller submits 10,000 requests in a one second period evenly (for example, 10 requests every millisecond), API Gateway processes all requests without dropping any.
  • If the caller sends 10,000 requests in the first millisecond, API Gateway serves 5,000 of those requests and throttles the rest in the one-second period.
  • If the caller submits 5,000 requests in the first millisecond and then evenly spreads another 5,000 requests through the remaining 999 milliseconds (for example, about 5 requests every millisecond), API Gateway processes all 10,000 requests in the one-second period without returning the 429 Too Many Requests error responses

Soap Webservices Passthrough

You can configure API Gateway as a SOAP web services passthrough.

Advanced API Exam Tips

  • Import API's using Swagger 2.0 definition files
  • API Gateway can be throttled
    • Default limits are 10,000 RPS or 5,000 concurrently (at one time)
  • You can configure API Gateway as a SOAP Webservice passthrough
  • Lambda Proxy Integration
    • The API has one method
    • The API calls the Lambda function with the request data (however order is not preserved)
    • The lambda function will return the response in JSON format
      • if the format is XML, a 502 Bad Gateway error will occur
    • Another valid cause in this scenario is that out-of-order invocation due to heavy loads can occur