Amazon Web Services
Build a VPC and Ubuntu EC2 server. Then explore S3 storage and Route 53 DNS.
Explore AWS guidesFrom your first account to a real Linux server. Learn AWS, Azure and Google Cloud with plain-English explanations, reusable code and cost guardrails.
One workflow. Every cloud.
# In your configured lab project
terraform fmt -check
terraform validate
# Read the plan before any deployment
terraform plan
# Learn what changes, and why.Compare the starting points below. Each server lab covers networking, restricted access, Terraform, Ansible and teardown.
Build a VPC and Ubuntu EC2 server. Then explore S3 storage and Route 53 DNS.
Explore AWS guidesStart with a resource group, VNet and Linux VM. Add a Blob Storage website.
Explore Azure guidesUnderstand projects, VPC firewalls and Compute Engine. Practice object storage next.
Explore Google Cloud guidesCompare service names, access models and architecture tradeoffs across providers.
Compare cloud servicesPlanning estimates, including setup and cleanup; your pace and account permissions may vary.
Follow a small, repeatable sequence. Know what you're creating, how to reach it and how to remove it.
Choose a learning account, enable MFA, review pricing and set a budget alert. Alerts are not spending caps.
Check the AWS guardrailsConnect the network, firewall and server in the console. See how each piece fits before automating.
Build the first serverRecreate the lab with Terraform, then configure its operating system and web software with Ansible.
Follow the code walkthroughInspect access and logs. Record what you learned, remove the resources and check for leftover charges.
Use the cleanup checklistSmall previews of real guides. Open the tutorial for prerequisites, complete examples and safety checks.
# Review your configured project
terraform fmt -check
terraform validate
terraform planA VPC, a restricted firewall and one Ubuntu EC2 instance. No NAT gateway required.
Open the AWS server lab# Inspect an existing Docker host
docker version
docker ps
docker imagesUnderstand images, ports and persistent data before configuring Docker with Ansible.
Open the container guide# Inspect your Linux server
ip -brief address
free -h
df -hFollow health checks, backups and recovery exercises rather than guessing at failures.
Open the operations guidePair hands-on projects with a credential route that fits your direction.
Certification is the checkpoint—not the curriculum. Build each project before booking the next exam.
Provider knowledge matters. So do the fundamentals that travel with you to every platform.
Understand what the cloud is abstracting before you automate it.
Make every lab repeatable, reviewable, and safe to remove.
A useful cloud engineer can explain both health and spend.
Four focused weeks. One small portfolio project. No endless tutorial queue.
Learn regions, availability zones, identity, shared responsibility, and the core compute, network, storage, and database services.
Ship:A one-page architecture glossary in your own words.Create a private network, deploy a small workload, add logging, and prove that access rules behave as expected.
Ship:An architecture diagram plus setup notes.Rebuild the same environment with Terraform and Git. Use variables, outputs, formatting, and a clean destroy step.
Ship:A public repo with no secrets or account identifiers.Add an alert, test a failure, inspect logs, estimate cost, and document the design tradeoffs you made.
Ship:A short runbook and a two-minute demo.Start with a budget alert, use the smallest eligible services, and remove resources when the session ends.
Publish a small site through object storage and a CDN, connect DNS, enforce HTTPS, and capture access logs.
API endpoint → function → managed key-value database, with structured logs and an error alarm.
Build a network, subnets, route rules, and a tiny compute instance entirely from code—then destroy it cleanly.
Start with one tool in each category. Add complexity only when a project demands it.
A consistent infrastructure workflow across AWS, Azure, and Google Cloud.
Use AWS CLI, Azure CLI, or gcloud to inspect, script, and troubleshoot resources.
Run checks and controlled deployments from versioned workflows.
Configure operating systems and software after infrastructure exists.
Use vendor learning plans and exam guides as the spine; use projects to turn knowledge into skill.
Your first project will teach you more than another week of comparison.