At Vancouver's Cloud Summit 2024, I presented on how to develop directly in the cloud (particularly AWS) and the numerous benefits it has, including which architectural layer can benefit most from it. I was one of three community speakers and this talk was labeled the "Advanced" talk.
When you leverage the Cloud as a framework, your infrastructure simply reflects your architecture! CDK makes this very evident.
AWS acts increasingly like a framework. And if you can understand how this framework is meant to be used, the better you can harness its potential.
In order to successfully go Serverless, and use AWS as a framework, you need to be ready for these structural differences and challenges.
How to use Terraform to not only set up your orchestration platform, but also to deploy code updates as part of Continuous Delivery.
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.
