4 posts tagged with "API Gateway"

I've spent a fair bit of time with API Gateway over the past few years. It's an awesome (if occasionally frustrating) service for building serverless web APIs using Lambda functions.

In previous blog posts, I took a close look at the internals of API Gateway and ran a performance test for different API setups. We've explored the intricacies of custom authorizers in API Gateway and how to connect API Gateway directly to other AWS services.

In this post, we're continuing the deep dive on API Gateway. Here, we'll be looking at API Gateway access logging. Access logging can save your bacon when debugging a gnarly API Gateway issue, but you need to understand some nuance before you can use it correctly. We'll dig into the details here so that you'll be logging like Paul Bunyan in no time.

AWS API Gateway is an awesome service to use as an HTTP frontend. You can use it for building serverless applications, for integrating with legacy applications, or for proxying HTTP requests directly to other AWS services.

But understanding the elements of API Gateway can be difficult. If you're like me, your understanding of API Gateway might be like the following:

In my last post, I showed how to connect AWS API Gateway directly to SNS using a service integration.

A few people asked me about the performance implications of this architecture.

AWS API Gateway is a powerful service for managing your REST APIs. It was released in 2015 as a way to make the newly-released AWS Lambda compute service accessible over HTTPS.

In this post, we'll discuss one of the more advanced API Gateway use cases -- using an AWS service integration to connect HTTP endpoints directly to other AWS services.