My team needed a simple on-call scheduler to manage who's on call, handle escalations, and send alerts without building something custom. After evaluating options we landed on GoAlert, an open-source on-call scheduling and alerting platform that does exactly what we needed, without the SaaS price tag.

Initially when we first designed our AWS API Gateway setup, the goal was simple, one custom domain, one REST API, and a top-level path-based routing strategy to serve multiple teams. It worked. Teams were onboarded quickly, routing was predictable, and the Terraform was easy to understand. For a while, it was the right call.

Attending AWS re:Invent is always a highlight for me, and this year’s session, SVS407-R: Understanding AWS Lambda Event Source Mapping, turned out to be a goldmine of insights. As someone who builds and maintains event-driven architectures, I walked away with a deeper understanding of the complexities and best practices around Event Source Mapping (ESM), particularly in handling event streams from services like Amazon Kinesis, DynamoDB Streams, and Amazon SQS.

Ever since the private preview of Terraform Stacks, I’ve been eager to dive in and explore this new approach to provisioning infrastructure. After a year in private preview, the public beta was finally announced at HashiConf 2024, and I’m excited to share my experience!

In this blog, we will provide a brief introduction to data governance and show how to implement it on AWS using DataZone. We will walk through a practical example involving a multi-account setup to manage and share data stored in S3 and Redshift, highlighting key steps and best practices along the way.