Injecting Chaos to AWS Lambda functions with Lambda Layers— RELOADED

Adrian Hornsby
The Cloud Architect
6 min readJul 16, 2019

--

UPDATE — October 2019

The code used for this blog post has evolved a bit and became that and that. However, the principles explained here remains similar. Just be aware :-)

I would like to express my gratitude to Gunnar Grosch for giving me some very useful feedback and for providing a nice little serverless application to easily test and visualize the effect of the failure injection layer. Give him a big thumbs up and give him a follow!

In the initial post — Injecting Chaos to AWS Lambda functions with Lambda Layers, I explained how to use AWS Lambda Layers to conduct chaos engineering experiments on Lambda functions using latency injection. Since then, the little latency injection layer has evolved into a more general failure injection one. In this post, I will explain the new features and how to use them.

What’s new?

The current v0.2-alpha version of the FailureInjection layer supports:

  • HTTP Error status code injection using error_code
  • Exception injection using exception_msg
  • Latency injection remains using delay
  • Per Lambda function injection control using Environment variable (FAILURE_INJECTION_PARAM)…

--

--

Adrian Hornsby
The Cloud Architect

Principal System Dev Engineer @ AWS ☁️ I break stuff .. mostly. Opinions here are my own.