π This is not properly displayed? Read all of our issues online! π‘
Hi Reader ππ½
We hope you're having an amazing week!
After writing about Terraform and the Serverless Framework let's tackle Sandro's favorite framework for IAC, which is the AWS Cloud Development Kit - the CDK.
The CDK was launched back in July 2019, which makes it one of the younger Infrastructure-as-Code tools out there.
It is a so-called componentized for provisioning your resources. Check out this article to learn more about the different stages of Infrastructure-as-Code frameworks.
The main difference between CDK and declarative tools like CloudFormation is the programming language you use.
In CloudFormation, you create configuration files in YAML or JSON. In CDK, you can use a proper programming language such as Python or TypeScript.
After writing your code, CDK will transform this code into CloudFormation templates. This has two amazing benefits:
For the examples, we will use TypeScript. You can also use the examples in another language of your choice.
CDK allows us to use our own programming languages. This enables us to build abstractions. And it also allows us to use our most beloved tool, the IDE. The IDE is the Integrated Development Environment. For example, VS Code, Webstorm, or IntelliJ. What benefits does that actually bring us?
Developers love their IDEs. We are used to them. We understand shortcuts, file managers, and actions like refactoring or debugging.
It is amazing how fast developers can be with a programming language and syntax they know. The only issue in the past came with how to provision resources. These days are gone with the CDK.
The core building blocks of CDK are Constructs. Constructs can but don't have to be shared. This enables developers to create constructs and share them across the company.
For example, if you have a standardized way of creating Lambda functions with attached DLQs you can publish a construct for that.
When choosing a framework to develop your cloud infrastructure in it is important to think about the stability and future of the tool. CDK is developed and supported by AWS. This brings a great benefit compared to other tools.
The CDK follows the concept of:
Constructs are the main building blocks in CDK. You should model your application by creating constructs for the different cloud resources you need. Constructs can be reusable but donβt need to be. That means you can also create a construct that is only used once.
Constructs are differentiated into different levels.
Level 1: This is the exact CloudFormation Construct:
Level 2: Level 2 constructs have some abstractions built-in on top of Level 1 like additional APIs, and default settings. They are often much easier to work with.
Level 3: Level 3 constructs are often community-shared constructs and combine multiple services with each other. The CloudFrontToS3 construct, for example, connects a CloudFront distribution (CDN) with an S3 bucket. This is often used for hosting single-page applications.
Stacks bundle multiple Constructs together and build them into one deployable unit. The concept is similar to stacks in CloudFormation. One stack contains one or more Constructs.
Here is an example stack in CDK:
Modeling stacks is an art in itself. There are two common approaches to modeling your stacks:
In this example, we can see that DynamoDB is in the stateful stack. Lambda and API Gateway are in the stateless stack.
The second common approach is to model your stack by Microservices:
Whatever you decide, try to stick to one approach π
This brings us to the last concept, the App. The App is the entry point of your CDK application (hence the name). The CDK app combines all stacks.
The app bundles all stacks together and has several phases: constructing, validating, synthesizing, and deploying your infrastructure.
The details here are not important to get started with the CDK!
This is about the CDK introduction π
Now get your hands dirty with your first hands-on project.π©βπ» π§βπ»
β
Have a great rest of the week!
Sandro & Tobi βοΈ
β
P.S.: Thanks for making it that far. Maybe you didn't know, but we are working on a new project: The CloudWatch Book. This project will include deployable code πΎ, an e-book π, infographics πΈ, and even a video course π½οΈ.
If you want to receive detailed info about this in the future, click on the following button β
I want to know more about the CloudWatch Book π |
π‘ As a subscriber, you can get our e-book with a 15% discount at all times.
Still hungry for AWS content? Have a look at our blog! π β
Join our community of over 8,800 readers delving into AWS. We highlight real-world best practices through easy-to-understand visualizations and one-pagers. Expect a fresh newsletter edition every two weeks.
β Reading time: 10 minutes π Main Learning: Building a Serverless Platform With SST, Lambda & Next.js βοΈ Read the Full Post Online π Hey Reader ππ½ In this post, we want to guide you through our complete setup for our custom video platform. Our CloudWatch Book's Video Section This starts from the purchase to actually accessing our custom build video-access platform. Overview about our CloudWatch Book Landing Page & Video Platform Architecture We'll explain why we decided against a third-party...
β Reading time: 11 minutes π Main Learning: Step Functions - Express vs. Standard πΎ GitHub Code βοΈ Blog Post Hey Reader while Sandro is learning something new at the AWS Community Day in Munich today, we'll explore Express and Standard Step Functions, the two types of workflows offered by AWS Step Functions. Weβll break down their differences, when to use each, and the benefits of both. Example Application: running both workflow types to see their performance differences If you want to try...
Hey Reader First things first: we apologize for not providing updates on The CloudWatch Book for a while! π’ Sometimes, things don't go as planned and unexpected obstacles arise. But now, we're back in action, creating videos and putting the final touches on the book's content! π₯ Don't just take our word for it! As an early subscriber, here's a free video from one of our favorite chapters: Anomaly Detection π In this deep-dive, you'll learn how to detect unusual patterns in metrics without...