Skip to Content
Cloud Engineering Academy
1. Cloud Computing & AWS Fundamentals

Module 1 cheat sheet

One-page revision summary for Cloud Computing & AWS Fundamentals: services, Azure mapping, CLI commands, limits, decision rules, exam traps and cost traps.

CLF-C02SAA-C03

Assumes: AWS CLI v2 · AWS SDK for .NET v4 · Region us-east-1 · facts as stated in the Module 1 lessons (checked 2026-11-17/18). Verified against official sources on 2026-11-18.

A printable summary of Module 1. Each row links back to the lesson with the detail.

Key services

ServiceWhat it is for
AWS OrganizationsGroup accounts into OUs; apply SCPs/RCPs; consolidated billing
IAMUsers, groups, roles and JSON policies evaluated on every API call
IAM Identity CenterSingle sign-on for humans; permission sets become roles in each account
AWS STSTemporary credentials; GetCallerIdentity = "who am I?" (needs no permission)
Management Console / CloudShellBrowser UI; browser terminal already signed in as you
AWS CLI v2 / SDK for .NET v4Scripted and programmatic access to the same APIs
Billing and Cost Management, Budgets, Cost ExplorerSee, alert on and analyse spend
AWS Pricing CalculatorEstimate before you build
AWS Well-Architected ToolRecord reviews against the six pillars and lenses

.NET / Azure → AWS

Microsoft / AzureAWS
SubscriptionAccount (hard security and billing boundary)
Management groupOrganizations OU + SCPs
Resource groupTags, CloudFormation/Terraform stacks (no mandatory container)
Entra ID + Azure RBACIAM Identity Center + IAM roles/policies
DefaultAzureCredentialSDK default credential chain
Managed identityIAM role (Lambda, ECS task, EC2 instance profile)
Azure Reservations / Savings Plans / Spot VMsReserved Instances / Savings Plans / Spot Instances
Azure Well-Architected FrameworkAWS Well-Architected (six pillars)

Most useful CLI commands

TaskCommand
Create an SSO profileaws configure sso
Sign in / outaws sso login --sso-session cea · aws sso logout
Who am I?aws sts get-caller-identity --profile learn-sandbox
Where did each setting come from?aws configure list --profile learn-sandbox
List profilesaws configure list-profiles
Filter outputaws s3api list-buckets --query "Buckets[].Name" --output table
List Regions enabled for the accountaws ec2 describe-regions --query "Regions[].RegionName"
Free plan stateaws freetier get-account-plan-state
Anything still tagged?aws resourcegroupstaggingapi get-resources --tag-filters Key=Project,Values=cea-lab

Key limits and defaults

ItemValueLesson
Regions / AZs39 Regions, 124 AZs; 34 Regions in the standard aws partitionGlobal infrastructure
Accounts per organisationDefault quota 10 (adjustable)Accounts and Organizations
SCP / RCP size10,240 / 5,120 charactersAccounts and Organizations
Customer managed IAM policy size6,144 charactersIAM fundamentals
Role session duration15 minutes–12 hours (default 1 hour)IAM fundamentals
Free plan (accounts from 2025-07-15)USD 100 credits + up to USD 100 earned; ends after 6 months or when credits run outFree Tier and billing
Lambda always-free1 million requests + 400,000 GB-seconds per monthFree Tier and billing
Savings Plans terms1 or 3 years; Compute up to 66%, EC2 Instance up to 72%Pricing models
SpotUp to 90% off On-Demand; two-minute interruption noticePricing models
S3 list page sizeUp to 1,000 keys per ListObjectsV2 responseLab: hello, AWS
S3 bucket namesGlobal, 3–63 characters, lowercase, digits, hyphens (and dots)Lab: hello, AWS

SDK for .NET credential chain (first match wins)

Credentials passed to the client always win. Otherwise: 1. env key + secret + session token → 2. env key + secret → 3. env web-identity token file + role ARN → 4. profile in AWSConfigs.AWSProfileName → 5. AWS_PROFILE → 6. [default] profile → 7. container credentials → 8. EC2 instance metadata. Details: SDK first contact.

Decision rules

If…Then…
A human needs accessIAM Identity Center user + permission set; never an IAM user with keys
An app runs in AWSIAM role via the default chain; no profile, no keys
Workloads need isolation (prod/test, teams, PCI scope)Separate accounts in OUs, guardrails via SCPs
Choosing a RegionData residency first, then service availability, latency, cost
Steady 24×7 computeCompute Savings Plan (flexible)
Interruptible batchSpot, with checkpointing
Short or unpredictable workloadOn-Demand
Static contentPrivate S3 + CloudFront + Origin Access Control
Deciding who secures whatAWS: of the cloud; you: in the cloud. More managed service = less for you

Common exam traps

  • SCPs grant nothing. They only limit what IAM policies in member accounts can allow, and do not affect the management account.
  • An explicit Deny always wins over any Allow.
  • AZ names are per account: us-east-1a may be a different physical AZ in another account; use AZ IDs (use1-az1).
  • Edge locations are not Regions: they cache and route; you cannot run your database there.
  • Shared responsibility moves: patching the guest OS is yours on EC2, AWS's on Lambda and Fargate. Data classification and IAM are always yours.
  • Savings Plans vs RIs: Savings Plans commit to USD per hour; RIs commit to an instance configuration. Licence fees are not discounted.
  • Root user tasks are few (for example closing the account or changing some account settings). Lock it with MFA and do not use it day to day.
  • Six pillars include Sustainability: Operational Excellence, Security, Reliability, Performance Efficiency, Cost Optimization, Sustainability.

Cost traps

TrapAvoid it by
Forgotten resources after a labTags on everything, IaC destroy, tagging-API check, next-day Bills check
NAT gateways, load balancers, idle databasesCharged per hour even with no traffic; delete them the same day
Unattached Elastic IPs and public IPv4 addressesEvery public IPv4 address is billed hourly; release them
Credits hiding real costIn Cost Explorer, exclude the Credit charge type to see what you would really pay
Wrong RegionResources in a Region you never check keep running; use the Region selector and a Region-deny SCP
Budgets are alerts, not brakesAct on the alert; consider budget actions
Committing too earlyBuy Savings Plans or RIs only for proven steady baseline load
Data transfer outFree inbound, paid outbound; CloudFront in front of S3 often costs less

Independent learning resource — not affiliated with, endorsed or sponsored by Amazon Web Services. AWS and related marks are trademarks of Amazon.com, Inc. or its affiliates. All banking data in examples is fictional. Sample architectures are for learning and are not automatically compliant with GDPR, PCI DSS or any banking regulation.

On this page