API Gateway

How to create IP-protected endpoints with API Gateway and Lambda

If you haven’t been pay­ing close atten­tion you might have missed the API Gate­way announce­ment for resource poli­cies. It lat­er played a key role in sup­port­ing API Gate­way pri­vate end­points — a way to put your API inside a pri­vate VPC. To con­fig­ure resource poli­cies with the Server­less frame­work, you need to upgrade to v1.28.0 or …

How to cre­ate IP-pro­tect­ed end­points with API Gate­way and Lamb­daRead More »

auto-create CloudWatch Alarms for APIs with Lambda

In a pre­vi­ous post we dis­cussed how to auto-sub­­scribe a Cloud­Watch Log Group to a Lamb­da func­tion using Cloud­Watch Events. So that we don’t need a man­u­al process to ensure all Lamb­da logs would go to our log aggre­ga­tion ser­vice. Whilst this is use­ful in its own right, it only scratch­es the sur­face of what …

auto-cre­ate Cloud­Watch Alarms for APIs with Lamb­daRead More »

how to do fan-out and fan-in with AWS Lambda

In the last post, we look at how you can imple­ment pub-sub with AWS Lamb­da. We com­pared sev­er­al event sources you can use, SNS, Kine­sis streams and DynamoDB streams, and the trade­offs avail­able to you. Let’s look at anoth­er mes­sag­ing pat­tern today, push-pull, which is often referred to as fan-out­/­fan-in. It’s real­ly two sep­a­rate pat­terns …

how to do fan-out and fan-in with AWS Lamb­daRead More »

I’m afraid you’re thinking about AWS Lambda cold starts all wrong

When I dis­cuss AWS Lamb­da cold starts with folks in the con­text of API Gate­way, I often get respons­es along the line of: Meh, it’s only the first request right? So what if one request is slow, the next mil­lion requests would be fast. Unfor­tu­nate­ly that is an over­sim­pli­fi­ca­tion of what hap­pens. Cold start hap­pens once for …

I’m afraid you’re think­ing about AWS Lamb­da cold starts all wrongRead More »

AWS Lambda — use the invocation context to better handle slow HTTP responses

With API Gate­way and Lamb­da, you’re forced to use rel­a­tive­ly short time­outs on the serv­er-side: API Gate­way have a 30s max time­out on all inte­gra­tion points Server­less frame­work uses a default of 6s for AWS Lamb­da func­tions How­ev­er, as you have lim­it­ed influ­ence over a Lamb­da function’s cold start time and have no con­trol over the amount of …

AWS Lamb­da — use the invo­ca­tion con­text to bet­ter han­dle slow HTTP respons­esRead More »

Applying principles of chaos engineering to AWS Lambda with latency injection

This is part 2 of a mul­ti­part series that explores ideas on how we could apply the prin­ci­ples of chaos engi­neer­ing to server­less archi­tec­tures built around Lamb­da func­tions. part 1: how can we apply prin­ci­ples of chaos engi­neer­ing to Lamb­da? part 2: laten­cy injec­tion for APIs <- you’re here part 3: fault injec­tion for Lamb­da …

Apply­ing prin­ci­ples of chaos engi­neer­ing to AWS Lamb­da with laten­cy injec­tionRead More »

Using Protocol Buffers with API Gateway and AWS Lambda

AWS announced bina­ry sup­port for API Gate­way in late 2016, which opened up the door for you to use more effi­cient bina­ry for­mats such as Google’s Pro­to­col Buffers and Apache Thrift. Why? Com­pared to JSON — which is the bread and but­ter for APIs built with API Gate­way and Lamb­da — these bina­ry for­mats can pro­duce sig­nif­i­cant­ly small­er pay­loads. At scale, …

Using Pro­to­col Buffers with API Gate­way and AWS Lamb­daRead More »

Capture and forward correlation IDs through different Lambda event sources

Server­less archi­tec­tures are microser­vices by default, you need cor­re­la­tion IDs to help debug issues that spans across mul­ti­ple func­tions, and pos­si­bly dif­fer­ent event source types — asyn­chro­nous, syn­chro­nous and streams. This is the last of a 3-part mini series on man­ag­ing your AWS Lamb­da logs. If you haven’t read part 1 yet, please give it a read now. …

Cap­ture and for­ward cor­re­la­tion IDs through dif­fer­ent Lamb­da event sourcesRead More »

Yubl’s road to Serverless — building better recommendations with Lambda, BigQuery and GrapheneDB

part 1: overview part 2: test­ing and CI/CD part 3: ops part 4: build­ing a scal­able noti­fi­ca­tion sys­tem part 5: build­ing a bet­ter rec­om­men­da­tion sys­tem <- you’re here When I joined Yubl in April 2016, it had launched just 2 months ear­li­er, after a long and chaot­ic devel­op­ment cycle that last­ed more than 2 years …

Yubl’s road to Server­less — build­ing bet­ter rec­om­men­da­tions with Lamb­da, Big­Query and GrapheneDBRead More »

Serverless 1.X — enable API Gateway caching on request parameters

Hav­ing pre­vi­ous­ly blogged about the untrod­den path to enable caching on API Gate­way request para­me­ters in the Server­less frame­work 0.5.X, it’s a lit­tle dis­ap­point­ing that it’s still not offi­cial­ly fixed in the 1.X ver­sions… The Prob­lem The prob­lem is two-fold: there’s cur­rent­ly no way to spec­i­fy caching should be enabled for path & query string …

Server­less 1.X — enable API Gate­way caching on request para­me­tersRead More »

By continuing to use the site, you agree to the use of cookies. more information

The cookie settings on this website are set to "allow cookies" to give you the best browsing experience possible. If you continue to use this website without changing your cookie settings or you click "Accept" below then you are consenting to this.

Close