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.
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
| Service | What it is for |
|---|---|
| AWS Organizations | Group accounts into OUs; apply SCPs/RCPs; consolidated billing |
| IAM | Users, groups, roles and JSON policies evaluated on every API call |
| IAM Identity Center | Single sign-on for humans; permission sets become roles in each account |
| AWS STS | Temporary credentials; GetCallerIdentity = "who am I?" (needs no permission) |
| Management Console / CloudShell | Browser UI; browser terminal already signed in as you |
| AWS CLI v2 / SDK for .NET v4 | Scripted and programmatic access to the same APIs |
| Billing and Cost Management, Budgets, Cost Explorer | See, alert on and analyse spend |
| AWS Pricing Calculator | Estimate before you build |
| AWS Well-Architected Tool | Record reviews against the six pillars and lenses |
.NET / Azure → AWS
| Microsoft / Azure | AWS |
|---|---|
| Subscription | Account (hard security and billing boundary) |
| Management group | Organizations OU + SCPs |
| Resource group | Tags, CloudFormation/Terraform stacks (no mandatory container) |
| Entra ID + Azure RBAC | IAM Identity Center + IAM roles/policies |
DefaultAzureCredential | SDK default credential chain |
| Managed identity | IAM role (Lambda, ECS task, EC2 instance profile) |
| Azure Reservations / Savings Plans / Spot VMs | Reserved Instances / Savings Plans / Spot Instances |
| Azure Well-Architected Framework | AWS Well-Architected (six pillars) |
Most useful CLI commands
| Task | Command |
|---|---|
| Create an SSO profile | aws configure sso |
| Sign in / out | aws 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 profiles | aws configure list-profiles |
| Filter output | aws s3api list-buckets --query "Buckets[].Name" --output table |
| List Regions enabled for the account | aws ec2 describe-regions --query "Regions[].RegionName" |
| Free plan state | aws freetier get-account-plan-state |
| Anything still tagged? | aws resourcegroupstaggingapi get-resources --tag-filters Key=Project,Values=cea-lab |
Key limits and defaults
| Item | Value | Lesson |
|---|---|---|
| Regions / AZs | 39 Regions, 124 AZs; 34 Regions in the standard aws partition | Global infrastructure |
| Accounts per organisation | Default quota 10 (adjustable) | Accounts and Organizations |
| SCP / RCP size | 10,240 / 5,120 characters | Accounts and Organizations |
| Customer managed IAM policy size | 6,144 characters | IAM fundamentals |
| Role session duration | 15 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 out | Free Tier and billing |
| Lambda always-free | 1 million requests + 400,000 GB-seconds per month | Free Tier and billing |
| Savings Plans terms | 1 or 3 years; Compute up to 66%, EC2 Instance up to 72% | Pricing models |
| Spot | Up to 90% off On-Demand; two-minute interruption notice | Pricing models |
| S3 list page size | Up to 1,000 keys per ListObjectsV2 response | Lab: hello, AWS |
| S3 bucket names | Global, 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 access | IAM Identity Center user + permission set; never an IAM user with keys |
| An app runs in AWS | IAM 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 Region | Data residency first, then service availability, latency, cost |
| Steady 24×7 compute | Compute Savings Plan (flexible) |
| Interruptible batch | Spot, with checkpointing |
| Short or unpredictable workload | On-Demand |
| Static content | Private S3 + CloudFront + Origin Access Control |
| Deciding who secures what | AWS: 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-1amay 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
| Trap | Avoid it by |
|---|---|
| Forgotten resources after a lab | Tags on everything, IaC destroy, tagging-API check, next-day Bills check |
| NAT gateways, load balancers, idle databases | Charged per hour even with no traffic; delete them the same day |
| Unattached Elastic IPs and public IPv4 addresses | Every public IPv4 address is billed hourly; release them |
| Credits hiding real cost | In Cost Explorer, exclude the Credit charge type to see what you would really pay |
| Wrong Region | Resources in a Region you never check keep running; use the Region selector and a Region-deny SCP |
| Budgets are alerts, not brakes | Act on the alert; consider budget actions |
| Committing too early | Buy Savings Plans or RIs only for proven steady baseline load |
| Data transfer out | Free 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.
Lab: hello, AWS — the Module 1 exercise
Call STS and S3 from a C# console app with SSO credentials, create a locked-down bucket holding a fictional bank statement, deploy a private status page through CloudFront with Terraform, prove it is not public, then tear everything down.
Module 2: AWS Networking & Infrastructure
Design and build private, segmented networks on AWS — VPCs, subnets, routing, firewalls, load balancers, DNS and private connections to AWS services and to on-premises data centres. You prove your database cannot be reached from the internet using Flow Logs and Reachability Analyzer.