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 βπ½ |
Dr.-Otto-BΓΆΓner-Weg 7a, Ottobrunn, Bavaria 85521 Β· Unsubscribe Β· Preferencesβ |
Join our community of over 9,300 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.
Hey Reader ππ½ We've been talking a lot about how great SST's switch to Pulumi was, and many of you have asked us how to use plain Pulumi directly. So today, we're sharing our quick guide to Pulumi - a tool we're really excited about since it lets us build infrastructure with languages we already know and love. No more learning weird syntax - just TypeScript, Python, or whatever we're comfortable with! We spent the last few days playing with it, and here's what we've learned... AWS Community...
Newsletter Header AWS FOR THE REAL WORLD β±οΈ Reading time: 8 minutes π Main Learning: Migrating from Edgio to CloudFront βοΈ Blog Post π» GitHub Repository Hey Reader ππ½ this newsletter is about π₯ AI π€ We haven't talked too much about AI, Bedrock, MCPs, and agents yet - so we want to change that. Please let us know if this it interests you to build AI on AWS, or if you are much more interested on hands-on fundamentals services. Should we focus on AI Services? Yes, I want to learn to build...
Newsletter Header AWS FOR THE REAL WORLD β±οΈ Reading time: 8 minutes π Main Learning: Migrating from Edgio to CloudFront βοΈ Blog Post π» GitHub Repository Hey Reader ππ½ This newsletter edition is all about saving Lambda costs. I (Sandro is writing this one) was recently involved in saving Lambda costs for a client. So, I thought writing down my thought process was a good idea. Have fun with it! If you need help saving AWS costs or improving your infrastructure, just reply to this email! Now...