Cloud Architect | AWS + Azure | Kubernetes, Terraform, Container Platforms | Building Scalable, Cloud-Agnostic Systems
AVM-Series
The networking layer established the traffic control plane: a hub VNet with a firewall at its centre, subnets reserved for security infrastructure, and route tables that force spoke traffic through inspection. This layer occupies those reserved spaces. By the end of this article you will have Azure Bastion running in
AVM-Series
This is the first hands-on deployment in the series. By the end of this article you will have a working hub virtual network in Azure: firewall, VPN gateway, DNS private resolver, private DNS zones covering all Azure PaaS services, route tables, and NSGs — all managed as Terraform code you can
AVM-Series
The previous two parts of this series covered what IaC is and how to get a local environment working. Before writing any infrastructure configuration, this article establishes the architectural model the rest of this series builds. This is the only article with no code and no deployment. Its purpose is
Azure
Before writing any infrastructure configuration, you need three things installed and working: the Terraform CLI, the Azure CLI, and a code editor configured for HCL. This article walks through each installation on Windows, explains the authentication options available to you, and deploys a single resource group to confirm everything is
AVM-Series
Infrastructure as Code (IaC) is the practice of defining and managing cloud infrastructure through machine-readable configuration files rather than through manual processes. This article explains what problem IaC solves, how it solves it, and why Terraform is the tool this series uses to do it. The problem: infrastructure that can’