Skip to main content

๐Ÿท๏ธ Enterprise AWS Tagging Strategy: 4-Tier Taxonomy for FinOps & APRA CPS 234 Compliance

ยท 9 min read
CloudOps
CloudOps Engineer

Enterprises waste an estimated $8โ€“15M annually on untagged or mis-tagged AWS resources โ€” not because engineers are careless, but because tagging strategy is treated as an afterthought rather than a first-class architecture decision. Without a governed taxonomy, cost attribution collapses, compliance audits become manual nightmares, and FinOps teams spend weeks reconciling spreadsheets instead of driving optimization.

The 4-Tier Enterprise AWS Tagging Strategy solves this at the source: mandatory enforcement through AWS Organizations Tag Policy, FOCUS 1.2+ FinOps dimension alignment, and APRA CPS 234 Para 15/36/37 traceability โ€” all expressed as Terraform-native common_tags.

๐Ÿ—๏ธ Terraform State Management & Design Mindset for Enterprise AWS Multi-Account Landing Zones

ยท 23 min read
CloudOps
CloudOps Engineer

When a team of 20 engineers concurrently runs terraform apply across 50 AWS accounts, state management stops being an operational concern and becomes a business risk. State corruption takes hours to diagnose, compliance audits fail when drift goes undetected, and the root cause is almost never the engineers โ€” it is the absence of a principled architecture before the first line of Terraform is written.

This post combines three disciplines that belong together but are rarely addressed as a unified system: the design mindset that prevents state problems from occurring, the S3 native locking strategy that eliminates the DynamoDB tax (ADR-006, saving up to $9,000/year at 50 accounts), and a real production-ready IAM Identity Center module that demonstrates both principles working at enterprise scale in an AWS multi-account Landing Zone.

All code, configuration, and test artifacts referenced here are live in the terraform-aws framework โ€” not theoretical examples, but verified, scored output (97/100 production-readiness) from a running ADLC-governed project.

Data-Driven GitOps Platform

ยท 9 min read
DevOps
DevOps Engineer

Welcome to our Data & AI/ML GitOps Platform with Hybrid-Multi-Cloud approach:

  • Dev (k3d): Local ephemeral clusters with k3d for rapid iteration and prototyping.
  • Staging (k3s): A pinned k3s environment providing a realistic test bed for integrated data workflows.
  • Production (AWS): A fully provisioned AWS environment (e.g., Amazon EKS) for large-scale data ingestion, training pipelines, and real-time inference.

DevOps Docker & DevContainer

ยท 4 min read
DevOps
DevOps Engineer

Overviewโ€‹

The nnthanh101/terraform:latest Docker image is a secure, lightweight, and production-ready environment tailored for modern CloudOps and DevOps workflows. Built on Chainguard's Wolfi Linux, this image incorporates best practices for multi-cloud, Infrastructure-as-Code (IaC), and Kubernetes ecosystem management.

Designed to meet the demands of multi-cloud environments and enterprise-grade automation, it includes tools for provisioning, configuration management, orchestration, and secrets management. The devops tag extends its functionality with Kubernetes tooling, making it ideal for hybrid-cloud operations.

CloudOps Docker Container

ยท 4 min read
DevOps
DevOps Engineer

Overviewโ€‹

The nnthanh101/runbooks:latest image is a secure, lightweight, and production-grade Python environment built on Chainguard's Wolfi Base. This image has been optimized to support multi-cloud environments (AWS, Azure) and cross-platform workflows for CloudOps, FinOps, Analytics, AI, and Data Science projects.

With a focus on modern CloudOps and DevOps practices, this image incorporates security, maintainability, and scalability into its design. It integrates essential extensions like MkDocs, JupyterLab, and Vizro for documentation and analytics workflows.