Cheat sheet · Specialise
Cloud engineering cheat sheet (AWS)
Opens with creditsFor students and early-career engineers learning AWS in depth: IAM, EC2, Lambda, S3, RDS, VPC, CloudWatch, cost control and CloudFormation or Terraform, plus the Cloud Practitioner to Solutions Architect Associate path. Every command uses the AWS CLI, and the service map shows the Azure and Google Cloud names alongside.
Chapters
10 chapters · 75 concepts
1Linux and networking for cloudThe server and network basics every cloud service sits on: a Linux shell, SSH keys, IP addresses and CIDR blocks, ports, DNS and HTTPS.7 concepts
- 1Linux shell essentialsThe commands you use on a cloud server: moving around the filesystem, reading logs, checking disk and memory, managing packages and starting or stopping…
- 2SSH key pairsA private key that stays on your laptop and a public key placed on the server.
- 3IP addresses and CIDR blocksAn IPv4 address is 32 bits.
- 4Private IP rangesThree IPv4 ranges are reserved for private networks and never routed on the internet: 10.0.0.0/8, 172.16.0.0/12 and 192.168.0.0/16.
- 5Ports, TCP and UDPA port number picks which service on a machine receives traffic.
- 6DNS recordsDNS turns names into addresses.
- 7HTTPS and TLS certificatesTLS encrypts traffic between a client and a server, and a certificate proves the server owns the domain.
7 in this chapterOpen this chapter2Cloud concepts and billingHow a cloud is organised and paid for: service models, shared responsibility, regions, how accounts are structured, the free offers, pricing models and budgets. Includes a service name map across the three providers.10 concepts
- 1IaaS, PaaS and SaaSIaaS rents you virtual machines, disks and networks to manage yourself.
- 2Shared responsibility modelThe provider secures the physical data centres, hardware and the platform.
- 3Regions and availability zonesA region is a geographic area with its own data centres.
- 4AWS accounts and OrganizationsAn AWS account is the boundary for resources, permissions and billing.
- 5AWS Free Tier and free planAs of September 2026, new AWS accounts get 100 USD in credits and can earn up to 100 USD more, for up to 200 USD over 6 months, on a free plan limited to select…
- 6On-demand, committed and spot pricingOn-demand is pay per second or hour with no commitment.
- 7Budgets and billing alertsA budget watches actual or forecast spend and emails you, or triggers an action, when it crosses thresholds you set, such as 50, 80 and 100 percent.
- 8Well-Architected frameworksEach provider publishes a framework of design principles grouped in pillars such as security, reliability, performance, cost and operations, with review…
- 9Service map: compute and dataThe same job has a different product name on each cloud.
- 10Service map: network, identity and operationsThe networking, identity, monitoring and infrastructure as code services on each cloud, side by side.
10 in this chapterOpen this chapter- Identity and accessWho can do what to which resource: protecting the all-powerful account, users and roles, least privilege, how a permission is written on your cloud, identities for workloads and where secrets belong.7 conceptsOpens with credits
- Compute: VMs, containers and serverlessThe three ways to run code on a cloud: virtual machines you manage, containers on a managed platform and functions that run on demand, plus sizes, images, autoscaling and how to choose.8 conceptsOpens with credits
- Storage and databasesWhere data lives: object storage for files, block disks for VMs, managed relational and NoSQL databases, storage tiers, public access, backups and replication.8 conceptsOpens with credits
- Virtual networks, DNS and load balancersYour private network in the cloud: address space and subnets, public and private tiers, routing to the internet, firewalls, load balancers, DNS, CDNs and private access to managed services.8 conceptsOpens with credits
- Monitoring and cost controlSeeing what your resources do and what they cost: metrics and alerts, logs, audit trails, tags, the cost tools on each cloud and the traps that produce surprise bills.7 conceptsOpens with credits
- Infrastructure as codeDescribing your cloud in files you review, version and apply: the idea, Terraform basics, state, your provider's native tool and the plan, apply and destroy loop.6 conceptsOpens with credits
- Certifications and the order to take themWhich certifications are worth it on your cloud, in what order, what each proves and how to pair every one with hands-on work. Names and codes checked on the official certification pages in September 2026.7 conceptsOpens with credits
- Portfolio: a three-tier app with IaCThe capstone: a web tier, an app tier and a database on your cloud, built with infrastructure as code, monitored, costed and documented so someone else can rebuild it.7 conceptsOpens with credits
- 11Glossary, A to ZEvery concept in the sheet and the smaller terms it uses, in one list.115 terms
About this sheet
One cloud in depth, with certifications.
Related on Sefism
Picked from the other libraries by shared topics.
Roadmaps
See allBest practices
See all- Kubernetes Best PracticesRun workloads on Kubernetes that schedule well, survive restarts and node drains, and stay locked down: resources, probes, PDBs, Pod Security and RBAC.
- Terraform Best PracticesWrite Terraform that teams can review and change safely: file layout, version pinning, remote state with locking, secrets, modules, refactoring and tests.
Checklists
See all- Cloud Cost Optimization ChecklistFinOps for engineers: tagging and allocation, budgets and anomaly alerts, rightsizing, scheduling, commitments, storage lifecycle, egress, idle resources and unit cost metrics.
- AWS Account Security ChecklistLock down an AWS account: root user, IAM Identity Center, roles instead of keys, CloudTrail, GuardDuty, S3 Block Public Access, IMDSv2 and guardrails.
- Incident Response ChecklistPrepare for and handle production incidents: on-call, severity levels, declaring, roles, mitigation, security containment, status updates and blameless postmortems.
Project structures
See all- Terraform project structureAn infrastructure repository for a small app on AWS: reusable modules, one folder per environment with its own remote state, pinned providers, tests and security scans, with plan on every pull request and apply from CI. For students who have finished the Terraform tutorials and want to know how a real team lays out the files. The same layout works unchanged with OpenTofu.
- Kubernetes with Helm project structureA Helm chart repository for one app: the chart that
helm creategives you, grown into a tested, versioned package with per-environment values, unit tests, install tests in a kind cluster and releases to an OCI registry. For students who can write a Deployment by hand and want to know how a team organises charts. It is about the repo layout and what each file does, not about cluster design. - Firebase (Cloud Functions and security rules) project structureFor students building an app on Firebase who need a real backend: Cloud Functions (2nd gen) in TypeScript, Firestore and Storage security rules with tests, and the Local Emulator Suite. The tree starts from
firebase initand grows into feature folders of callables, triggers and scheduled jobs, then adds CI deploys, environments, contract tests and runbooks.
Career questions
See all- Which cloud should I learn first: AWS, Azure or GCP?If you have no reason to choose otherwise, start with AWS: it has the largest market share and the most learning material. Choose Azure if the employers you want run on Microsoft, and GCP if you are heading into data and ML work at companies that use it. The concepts transfer, so the first cloud matters less than learning it properly.
- How do I practise on AWS, Azure or Google Cloud without getting a surprise bill?Use the free offer that fits you, set a budget alert before you create anything, tag every resource, build and destroy your labs with code, and run a five-minute check for the usual culprits, such as NAT gateways, load balancers, databases and public IPs, before you close your laptop.
- Are certifications like AWS or Google Cloud worth it for getting a tech job?It depends on the role. For cloud, DevOps, security and some data roles, a respected certification can help you get shortlisted, especially combined with a real project. For general software engineering roles, projects and skills matter far more. Do the certification to structure your learning, not as a replacement for building.
Stuck on something specific?
Writing only gets you so far. If you want an answer to your situation rather than the general case, book a session and we will work through it together. Sessions are free for approved Sefism members, and a few slots open each week.
- 1:1 Mentorship
- Fresh Graduate Mentorship
- Career Guidance
Brand deals, promos and partnerships: tauseeffayyaz@gmail.com