How Subhamay Built the AWS Architecture Pattern Everyone Now Uses

By Subhamay Bhattacharyya

The engineer who turned cloud governance into infrastructure-as-code that scales

By late 2029, Subhamay had become the architect other architects consulted. It wasn’t through self-promotion or thought leadership threads—it was through relentless building and public documentation.

The Projects That Proved It

Five years earlier, he began architecting a multi-account AWS landing zone (org o-v5ewdoo4w0, HCP Terraform org subhamay-bhattacharyya). He built sophisticated SCP/RCP governance, IAM Identity Center permission sets, CloudTrail encryption, and EC2 declarative policies. He didn’t hide the work—he shipped it openly.

The GitHub Impact

He published modular, production-grade Terraform code across two GitHub organizations: subhamay-bhattacharyya-tf (infrastructure modules) and subhamay-bhattacharyya-gha (GitHub Actions automation). His repositories followed obsessive conventions—semantic versioning, conventional commits, comprehensive documentation. By 2027, dozens of enterprises had forked his SCP patterns and organizational governance code. His GitHub portfolio became a portfolio: thousands of stars, hundreds of forks, real adoption.

The Certifications He Earned

Between 2024 and 2029, he earned AWS Certified Security Specialty (SCS-C03), Atlassian Certified Agile DevOps Specialist, Atlassian Cloud Fundamentals, and ACP-120 Jira Administration certifications. But certifications were proof of method, not destination. Each exam fueled the projects; each project validated the learning.

The Blogs He Published

He maintained a technical blog documenting his journey: certification strategies, Terraform module design patterns, SCP gotchas, AWS landing zone architecture. He published detailed implementation guides for integrating Claude into CI/CD pipelines, attracting readers from across the industry.

The Community He Built

His open-source contributions became reference implementations. terraform-snowflake-view, terraform-snowflake-api-integration, terraform-checkov-scan-detector, and tf-yor-action were forked and built upon by engineers he’d never met. He mentored junior engineers through his disciplined approach: certification + project + documentation.

The Job Role That Mattered

At Capgemini, he evolved from implementing solutions to architecting them. He led ML pipeline validation at major financial institutions, debugged SageMaker deployments, and mentored teams through rigorous cloud security practices. His job title was senior technology professional; his actual role was trusted architect.

The Claude Masterclass

In 2028, he pivoted toward AI-powered infrastructure. The claude-masterclass Python project evolved into a framework for integrating Claude directly into infrastructure validation and policy analysis. He became an Anthropic partner, contributing to the Claude ecosystem documentation and best practices.

The Real Credential

By 2029, the credential that mattered most wasn’t on his LinkedIn profile. It was the infrastructure running in production at companies he’d never worked for, built on patterns he’d open-sourced years earlier. It was engineers around the world using his Terraform modules, referencing his documentation, and building on his work.

P.S. This post is part of the DevOps Micro Internship (DMI) with Agentic AI — Cohort 3 — by Pravin Mishra. My graded progress is public: https://dmi.pravinmishra.com/s/subhamay-bhattacharyya.html · Start your DevOps journey: https://dmi.pravinmishra.com/?utm_source=student&utm_medium=ps-blog&utm_campaign=cohort3