Identities are sorted - an IAM user (Part-1), accounts (Part-2) and roles (Part-3). Time to run something. Amazon EC2 (Elastic Compute Cloud) is the virtual server service, and in this Part-4 we launch one from the console, connect to it, and understand every choice on the launch page so that nothing on the bill …

Before the full VPC build in Part-5 of the AWS series - which takes an hour and creates fifteen resources - here is the five-minute version that the short video above gives you in 27 seconds: what a VPC is, what a subnet is, and the handful of words around them. If you can explain this page to a colleague, the rest of …

Most of this blog uses Terraform to build AWS infrastructure, so people ask me regularly - do I still need to know CloudFormation? The answer is yes, for three reasons - it is the native infrastructure-as-code service of AWS and shows up everywhere (Control Tower, Service Catalog, SAM, CDK, the "Launch …

Every network tutorial on this blog - the AWS VPC, VPC peering, Transit Gateway, Cloud WAN, the GCP VPC posts, even the Kubernetes setup - starts with something like 10.0.0.0/16. If that slash-sixteen has always been a thing you copy rather than a thing you understand, this post fixes it in ten minutes. CIDR - …

Your laptop has the address 192.168.1.10. So does your neighbour's. So do roughly a hundred million other laptops in the world right now - and yet every one of them can open this page. The trick that makes that possible is NAT, network address translation, and it is also the trick behind the AWS NAT Gateway that lets …

In this blog post we are going to build a private AI assistant that lives on Telegram, remembers you, reads your inbox on demand, and sends you a triaged email briefing every morning at 7 - all running on your own server with n8n, self-hosted on a VPS for roughly the price of two coffees a month. This is the companion …

This is the last post of my Google Cloud networking series, and it is about the tool I find the most elegant of them all - Private Service Connect, or PSC. With VPC peering we connected two whole networks. With Shared VPC we put many projects on one network. PSC does something much more surgical - it lets one team …

In the last two posts we connected networks with VPC peering and cross-project VPC peering, and both times we ran into the same wall - peering is not transitive, and every team still has to build and maintain its own VPC. In this blog post we are going to look at the way enterprises actually solve this on Google Cloud …

When I started the Shared VPC lab I hit a wall on the very first command - gcloud compute shared-vpc enable simply does not work on a standalone project. Shared VPC, Organization Policies, folders, hierarchical firewall policies and org-level IAM all need one thing first - a Google Cloud Organization. And most of us …

TL;DR Cross-project peering is the same primitive as same-project peering plus one flag: each side is created in its own project with --peer-project pointing at the other. Nobody needs access to the other project's network; Compute Network Admin on your own project is enough. The lab: hub-vpc 10.10.1.0/24 in project …