All Posts

Use Terraform to easily deploy your Lambda functions while supporting multiple AWS environments, AWS integrations, CloudWatch metrics, secrets, and more.

Your infrastructure, just like the real world, is constantly changing. But differentiating between an expected and an unexpected change can be difficult. How can you tell them apart?

We need to step back and ask what the “Cloud” offers and agree on a set of definitions and concepts; in particular, the concepts of Deployment, Immutable Infrastructure, and Blue-Green Deployments. Once we have a strong grasp of these concepts, we can then apply them using Amazon Web Services (AWS).

AWS SDKs have their particular challenges. This post deep dives into those challenges when SDKs are used to directly setup your infrastructure. Our learnings from using SDK directly justified why we needed Terraform instead.

If we choose a less automated approach, we’d quickly become overwhelmed (and bored) with the numerous routine tasks involved. We’d have little assurance regarding the reproducibility of our infrastructure and we'd accumulate too many one-off hand-crafted changes.