profile

AWS for the Real World

🚨 Still jumping between accounts for alerts? Fixed.

Published 8 months agoΒ β€’Β 2 min read
AWS FOR THE REAL WORLD
⏱️
Reading time: 6 minutes
🎯
Main Learning: Build a central alerting approach with CloudWatch, Lambda, EventBridge, and CDK across your AWS Organization.
πŸ“
🎬

Hey Reader πŸ‘‹πŸ½

Welcome to the first issue after re:Invent.

For everybody who was out there, I hope you came home safe & healthy. I heard re:Invent cold is a thing like Oktoberfest cold in Munich 🍻

πŸ“° This Week in AWS

⏸️AWS Lambda Durable Functions

Lambda launched Durable Functions! We're pretty hyped on them. We love Step Functions (especially the visual part). But ASL (the language you write SFNs in) can actually be quite a burden. Doing it all in your favorite programming language is great! Read More β†’

πŸ’°Database Savings Plans

FINALLY, we've got some database saving plans. We'll have a dedicated post on them soon! Read More β†’

πŸ–₯️Lambda Managed Instances

Ever needed your Lambda function with some specific compute requirements? Now you can set them up with Lambda Managed Instances. Read More β†’

We'll have dedicated launch newsletters and posts on them as well!

In this week's deep dive, we'll talk about CloudWatch Central Alerting. I (Sandro) just built something similar for a client and published a YouTube video + an example CDK implementation!

video preview​

Now let's learn something and build centralized alerting in this week's deep dive πŸ€“

Cover

πŸ“š This Week's Deep Dive

The Case for Centralized Alerting

If you use AWS, you use CloudWatch to some extent. Having it as a powerful monitoring tool is nice. As your organization grows, organizing alerts, logs, and metrics becomes harder.

You should have a global way of handling your alerts. It doesn't make sense that all of your developers need to think about where your alerts should arrive. You will end up with a mess of:

  • Custom Apps in your IM messengers (Slack, Teams, etc.)
  • Webhook Implementations
  • Email Alerts

Platform teams should make it as simple as possible for developers to be able to create alerts. These alerts should be handled automatically and arrive at some common point where you can handle them. This is often an instant messaging service like Slack. Or it could also be a ticketing system such as Jira.

In this post, we will show you how to create such an architecture in a multi-account setup in AWS.

Architecture Overview

The architecture consists fully of serverless services.

We have three different sets of accounts:

  1. Management Account
  2. Member Accounts
  3. Observability Account

All of these accounts are in an AWS Organization. This organization has different organizational units (OU).

For instance, we could have the following OUs:

  • Production
  • Development

The observability account could live in its own OU or directly in the root.

Typically, two app accounts exist. One in production and one in development.

...

πŸš€ Read the Full Tutorial β†’

Summary

That's it for this week's newsletter!

Tobi & I are traveling to Berlin this week for a client's AWS workshop and some co-working. I'm sure we'll grab a mulled wine at a Christmas market 🍷 (if you're in Berlin, hit us up!)

Have a great pre-Christmas/post-re:Invent time – and talk to you soon ❄️

AWS for the Real World

by Tobi & Sandro

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.

Read more from AWS for the Real World

AWS FOR THE REAL WORLD ⏱️ Reading time: 11 minutes 🎯 Main Learning: Most teams should stay serverless. EKS only pays off at real scale. πŸ“ Blog Post Hey Reader πŸ‘‹πŸ½For years we told everyone the same thing: don't run Kubernetes! And we meant it. Running k8s yourself is a second full-time job. Cluster upgrades, etcd backups, some networking plugin that falls over on a Tuesday and nobody can say why.We're serverless people through and through. Lambda first, a queue behind it, scale to zero, go...

about 2 months agoΒ β€’Β 3 min read

AWS FOR THE REAL WORLD ⏱️ Reading time: 12 minutes 🎯 Main Learning: Most of the complaints in the viral "leaving AWS" post are skill issues β€” but egress pricing is a fair hit. πŸ“ Blog Post Hey Reader πŸ‘‹πŸ½Recently, a post with the title "I returned to AWS and was reminded why I left" hit 810 upvotes on Hacker News last week and went pretty viral with it.I read it twice before forming an opinion. My honest take: most of the complaints are skill issues! πŸ€·β™‚οΈNevertheless, the post is well written and...

2 months agoΒ β€’Β 2 min read

AWS FOR THE REAL WORLD ⏱️ Reading time: 10 minutes 🎯 Main Learning: Describe the agent: model, prompt, tools and AWS runs the orchestration loop behind one API call! πŸ“ Blog Post Hey Reader πŸ‘‹πŸ½ If you've ever built an agent on AWS, you know the pain: glue Bedrock, Lambda, and DynamoDB together, grab LangGraph or Strands, then also own the orchestration loop, the memory layer, and your own tracing. πŸ˜… A "simple" agent ends up with multiple layers of pain.AWS just shipped something that takes most...

3 months agoΒ β€’Β 2 min read