Happy New Year, Reader! π We hope you had some great holidays and could recharge with your loved ones. In this update, we will show you the table of contents of the CloudWatch Book and give you some insights into a lesser-known feature of CloudWatch - Evidently. As always, we love to hear your feedback. If you have any topics that you are missing or think are completely useless, let us know! Table of Contents
These are all the high-level chapters. The major part of the book will be in Chapters 4 - 8. Because we think these are the most important ones. All checked (β ) chapters are already done, in an initial draft version. Everything else is still in the works. The chapters are not pure theory! They will include a lot of code and examples from the example project. You can use your own AWS Account and reproduce everything we explain in the book. Additional ChapterDavid Yanacek (Engineer @CloudWatch) has an amazing talk about Observability from the last re:Invent. We recommend you check this one out! β He structured his talk around diagnosing issues, uncovering hidden issues, and preventing future issues. This got us thinking about adding a second part to the book. The second part would all be about applying the CloudWatch Fundamentals on detecting, finding, and preventing issues. Let's dive into one small part of the upcoming book: CloudWatch Evidently. Evidently - Feature Flags and Dark LaunchesAmazon CloudWatch Evidently is a feature within the CloudWatch suite designed to help you run experiments and gain insights into your experimental features or proof-of-concepts before releasing them to the full audience of your application. You can decide which features are activated for which part of your users and you can measure the impact by collecting metrics. The key components of Evidently are:
In our book's application, we'll also go in-depth with Evidently by implementing several feature flags that steer some features. We'll also show you how Evidently helps to collect metrics on the different feature flag configurations so we can make sense of the experiments we run. Previous Updates Our goal is to let you participate in the creation of the CloudWatch Book as best as possible. For that, we want to send 1-2 emails per month. If you've missed the last ones, you can find them here:
Thank you for joining the journey of the CloudWatch Book! If you only want to receive the AWS Newsletter and not these updates anymore, please update your preferences here. Best βπ½ |
GrΓΌnwalder Strasse 145a, Munich, Bavaria 81547 Β· Unsubscribe Β· Preferencesβ |
We teach AWS for the real world - not for certifications. Join more than 10,500 developers learning how to build real-world applications on AWS.
AWS FOR THE REAL WORLD β±οΈ Reading time: 5 minutes π― Main Learning: How to make Claude write production-ready Terraform instead of technical debt π¬ Watch on YouTube π Blog Post π» GitHub Repository Hey Reader ππ½ We've been heads-down the past weeks. Preparing the live AMA workshops from Black Friday (sorry for the delay!) and recording new YouTube videos. It's been a lot of fun. Speaking of videos - this week Tobi recorded one you'll want to watch. Here's the problem: LLMs want to close the...
AWS FOR THE REAL WORLD β±οΈ Reading time: 8 minutes π― Main Learning: 5 practical techniques to cut Lambda costs (memory, timeouts, ARM, batching, caching) π Blog Post π¬ Watch on YouTube Hey Reader ππ½ Lambda bills can sneak up on you. One function is often not expensive. But then you scale it up and π₯ it costs you $5,000. Sounds familiar? We had this exact problem with our Shopify fraud detection app. Orders coming in via EventBridge, each triggering its own Lambda.And the bill was $150/month...
AWS FOR THE REAL WORLD β±οΈ Reading time: 8 minutes π― Main Learning: Generate AWS architecture diagrams using AI with Kiro and MCP servers - skip the hours of dragging boxes in Lucidchart. π Blog Post π¬ Watch on YouTube Hey Reader ππ½ Big news: We launched our YouTube channel! π¬ We've published 7 videos so far and are almost at 800 subscribers. Our goal is to keep a weekly rhythm, so expect fresh content every week. If you haven't subscribed yet, here's the link. No exciting AWS news this week....