AWS on Cloudy Mountains

aws_oam_sink and aws_oam_link in Terraform: Centralized AWS Observability (Part 2)

Mon, 30 Mar 2026 13:00:44 +0100

In part one we covered the architecture and design behind the centralized observability solution. In this post, we walk through the practical configuration and provide code snippets to build the first part of the solution: metrics centralization.

CloudWatch cross-account observability (OAM) requires you to designate a monitoring account (or create one). AWS recommends a dedicated monitoring account. In our case, we used the existing Shared Services account where we already run shared services, so we did not use a separate account.

Centralized AWS Observability Architecture: CloudWatch, YACE and Grafana (Part 1)

Sun, 25 Jan 2026 13:00:44 +0100

In this series of blog posts I will describe the journey (or one of the possible ways) of building a comprehensive observability solution for AWS and on-prem workloads. I will provide a step by step guide and how the decisions were made for choosing or not the particular technologies (observability stacks or whatever you call it). I will try to provide as much as possible examples and code snippets. So lets start. First let say a few words about the initial state and the goals that I have to achieve with this solution.

Hugo on S3 and CloudFront with Terraform and GitHub Actions OIDC

Fri, 06 Jun 2025 12:20:44 +0100

When I decided to build my own site, I knew I wanted something fast, scalable, and modern — not just in terms of the tech stack, but also in the way it’s managed and deployed. This post walks you through exactly how my site (Cloudy Mountains) is deployed using Hugo, AWS (S3 + CloudFront), Terraform, GitHub Actions, and OIDC authentication. I’ll show you the challenges that I had and how to solve them properly.