Munah..🐍🖤🦇

Day 3 of learning GCP in public. (1/5) Finished Google Cloud Fundamentals: Core Infrastructure. Hands-on labs I did: - Deployed a LAMP stack on Compute Engine from Cloud Marketplace - Built an auto mode VPC with firewall rules and two VMs, then tested connectivity

Day 4 of learning GCP in public. What I learned this week from Core Infrastructure: 1. Resource hierarchy: organization > folders > projects > resources. IAM policies inherit downward, so a role on a folder applies to everything under it.

Day 5 of learning GCP in public. Started Essential Cloud Infrastructure: Foundation. Lab: Explore the Google Cloud Console and Cloud Shell. Two ways to work in GCP: - Console: the web GUI, good for exploring - Cloud Shell: a browser-based command line with gcloud ready to go

Day 6 of learning GCP in public. didn’t really do much today, was preparing for my siwes defense tomorrow… had to put some things in place Deployed a LAMP stack from Google Cloud Marketplace onto a Compute Engine VM LAMP: Linux, Apache, MySQL, PHP. The classic web app stack

Day 7 of learning GCP in public. (1/2) Today: projects, the unit everything in GCP lives inside. - Every resource belongs to exactly one project, and projects keep resources isolated from each other - A project has a name you choose and an ID that has to be globally unique

Day 8 of learning GCP in public. basically IP addressing + VPC. - CIDR like 10.0.0.0/24 means the first 24 bits identify the network and the rest identify hosts - Smaller number after the slash = bigger network - A VPC is global, but its subnets are regional

Day 9 of learning GCP in public (a day late, it was my birthday). Took the day off from the labs, but I'm back today.

Day 10 of learning GCP in public. Today: IP addresses on Compute Engine. Every VM can have two: Internal IP: assigned by DHCP, and every VM gets one. VM names also resolve to it through internal DNS, but only inside the same network. (1/2)

Day 11 of learning GCP in public. (1/5) Big day: I finished the virtual networks module of Essential Cloud Infrastructure: Foundation and started Compute Engine. Networking first. A route decides where a packet can go. A firewall rule decides if it's allowed through.

Day 12 of learning GCP in public. (1/4) Today: IAM in Essential Cloud Infrastructure: Core Services. IAM answers one question: who can do what on which resource. Policies follow the hierarchy (organization > folders > projects > resources) and flow downward.

Day 13 of learning GCP in public. [1/2] Today I drew the architecture for my first real project: a 3-tier app on Google Cloud, built on VMs. - External load balancer in front - Web tier: Nginx + Angular, 2 VMs across 2 zones

Day 14 of learning GCP in public (posting a day late). Two wins from yesterday: 1. My Google Cloud account finally went through after the signup got flagged. 2. I finished the architecture diagram for my first real project.