Module 1: Cloud Computing & AWS Fundamentals
Learn what the cloud really is, how AWS is organised (Regions, Availability Zones, accounts) and how you talk to it from the console, the CLI and C#. You finish by calling AWS from a .NET console app using short-lived SSO credentials, deploying something small and tearing it down.
Assumes: .NET 10 LTS · AWS SDK for .NET v4 · AWS CLI v2 · Region us-east-1. Verified against official sources on 2026-11-18.
Learn what the cloud really is, how AWS is organised (Regions, Availability Zones, accounts) and how you talk to it from the console, the CLI and C#. You finish by calling AWS from a .NET console app using short-lived SSO credentials, deploying something small and tearing it down.
| Estimated time | About 12 hours (lessons 8 h · labs 3 h · exercise 1 h) |
| Priority for you | Foundation — required before everything else |
| Level | Beginner |
| Certifications | CLF-C02 (primary) · SAA-C03 |
| Cost profile | 🟢 almost entirely free · 🟡 one small deploy-and-destroy |
Why this matters in banking
A bank's first AWS questions are rarely technical: Where physically is our data? Who is responsible if something is breached? How do we stop a developer running up a five-figure bill? Those answers come from this module — Regions and data residency, the Shared Responsibility Model, account boundaries and billing controls. Get these wrong and every later design inherits the mistake. Get them right and you can hold your own in a meeting with risk, compliance and finance colleagues.
From .NET/Azure to AWS
| You know (Microsoft/Azure) | AWS equivalent | What's different |
|---|---|---|
| Azure subscription | AWS account | An account is a hard security and billing boundary, not just a billing grouping |
| Management groups | AWS Organizations + organizational units (OUs) | Guardrails (SCPs/RCPs) attach to OUs and apply to every account below |
| Resource groups | Tags, AWS Resource Groups, CloudFormation stacks | There is no mandatory container for resources; tagging discipline matters more |
| Azure regions and availability zones | Regions and Availability Zones | Very similar idea; AZ names are mapped per account, so us-east-1a in two accounts may differ |
| Entra ID users + Azure RBAC | IAM Identity Center users + IAM roles and policies | Permissions are JSON policies evaluated on every API call |
| Azure Portal / Azure CLI / Az PowerShell | Management Console / AWS CLI v2 / AWS Tools for PowerShell | Same API underneath all of them |
DefaultAzureCredential | SDK credential provider chain | Both search a list of sources; on AWS prefer SSO profiles locally and roles in AWS |
| Azure Pricing Calculator / Cost Management | AWS Pricing Calculator / Billing, Cost Explorer, Budgets | AWS bills almost everything per second, hour or request; idle resources still cost |
| Azure Reservations / Savings Plans / Spot VMs | Reserved Instances / Savings Plans / Spot Instances | Same concepts, different commitment rules |
| Azure Well-Architected Framework | AWS Well-Architected Framework (six pillars) | AWS adds industry lenses, including a Financial Services Industry Lens |
Learning objectives
By the end of this module you can:
- Explain cloud computing, the IaaS/PaaS/SaaS models and public, private and hybrid cloud in plain language.
- Describe Regions, Availability Zones, edge locations and Local Zones, and explain how Region choice affects latency, cost, service availability and data residency.
- Explain why banks use many AWS accounts and how AWS Organizations groups them.
- Read a simple IAM policy and explain the difference between users, groups, roles and policies.
- Use the console, the AWS CLI v2 with an SSO profile, and the AWS SDK for .NET without any long-lived access keys.
- Explain how the SDK finds credentials and a Region, and fix the common "unable to get credentials" error.
- Compare On-Demand, Savings Plans, Reserved Instances and Spot pricing, and set up Free Tier and budget alerts.
- Draw the Shared Responsibility line for a service you use and name the six Well-Architected pillars.
Prerequisites
- Module 0: Orientation & a safe learning environment — account lockdown, budgets and tooling
- C# and .NET experience (assumed); no prior AWS knowledge
How the pieces fit
You sign in once through IAM Identity Center, receive temporary credentials for a role in your sandbox account, and every tool (console, CLI, C# SDK) uses those. Guardrails attached to the sandbox OU limit what even an administrator in that account can do.
Lessons
- What cloud computing really is — on-demand, pay-as-you-go infrastructure explained against your on-premises IIS and SQL Server experience.
- IaaS, PaaS and SaaS — the three service models, with AWS and Azure examples of each.
- Public, private and hybrid cloud — why most banks run hybrid for years and what that means for networking and identity.
- AWS global infrastructure — Regions, Availability Zones, edge locations and Local Zones; choosing a Region for latency, cost, features and data residency.
- AWS accounts and Organizations — accounts as blast-radius and billing boundaries, OUs and the multi-account mindset.
- IAM fundamentals — users, groups, roles, policies, the root user, and why humans should use Identity Center, not IAM users.
- The Management Console — navigation, Region selector, CloudShell, and the habits that prevent "it's in the wrong Region" mistakes.
- AWS CLI v2 with SSO profiles —
aws configure sso, named profiles, output formats and JMESPath queries. - AWS SDK for .NET: first contact — the credential provider chain, profiles, Region configuration and your first S3 and STS calls.
- Free Tier and billing — the current Free plan for new accounts, always-free services, Budgets, Cost Explorer and the classic billing traps.
- Pricing models — On-Demand, Savings Plans, Reserved Instances and Spot, and when each suits a bank workload.
- The Shared Responsibility Model — security of the cloud vs security in the cloud, and how the line moves between EC2, Fargate and Lambda.
- Cloud architecture fundamentals — scalability, elasticity, loose coupling, designing for failure, and managed services over self-managed.
- Well-Architected Framework introduction — the six pillars (Operational Excellence, Security, Reliability, Performance Efficiency, Cost Optimization, Sustainability) and the Financial Services Industry Lens.
Labs and module exercise
- Lab 1.1 (🟢) — In AWS accounts and Organizations: confirm your Module 0 account set-up: MFA on root, Identity Center user, budget alert received by email.
- Lab 1.2 (🟢) — In AWS CLI v2 with SSO profiles: configure an SSO profile for the CLI and the AWS Toolkit for Visual Studio; prove no access keys exist on disk.
- Lab 1.3 (🟢) — C# console apps: call STS
GetCallerIdentityand list S3 buckets (SDK for .NET: first contact), then deliberately break the credential chain to read the errors (Lab: hello, AWS, steps 1–3). - Lab 1.4 (🟢) — Lab: price a banking web app: price a small banking web app in the AWS Pricing Calculator three ways (On-Demand, Savings Plan, Spot workers).
Module exercise — hello, AWS (🟡 credits, expect $0.00). Create the account securely (from Module 0), configure CLI SSO access, call S3 and STS from a C# console app, deploy a simple application (a static status page in a private S3 bucket served through CloudFront, or a single Lambda function URL with IAM auth), confirm it works, then tear everything down and check the Billing console the next day. The lab implements the S3 + CloudFront option; the code is in labs/m01-hello-aws/ (72 tests that run without an AWS account).
When you finish, keep the Module 1 cheat sheet handy for revision.
Cost profile
| Part | Label | Free alternative |
|---|---|---|
| Account set-up, IAM Identity Center, Organizations, CLI, SDK calls | 🟢 free | No charge for these services themselves |
| S3 and STS calls from C# | 🟢 free | Tiny request volumes; or run against AWS Emulator locally |
| Simple app deployment (S3 + CloudFront or Lambda) | 🟢 / 🟡 credits | Delete the same day; costs are cents at most |
| Pricing Calculator exercise | 🟢 free | Runs in the browser; nothing is deployed |
Free Tier for new accounts
Accounts created after 2025-07-15 start on a Free plan that lasts six months or until the sign-up credits are used, after which the account must be upgraded or it closes. Always-free allowances (for example Lambda requests) still apply. Check the official Free Tier page for the current credit amounts and rules ⚠ VERIFY.
Certification alignment
| Exam | Domains (weight) | What this module covers |
|---|---|---|
| CLF-C02 | Cloud Concepts (24%) · Security & Compliance (30%) · Technology & Services (34%) · Billing & Pricing (12%) | Nearly the whole exam blueprint at foundation depth |
| SAA-C03 | Secure (30%) · Cost-Optimized (20%) | Shared responsibility, IAM basics, pricing models, global infrastructure |
The domain labels are short forms; see each exam page for the official wording.
Key AWS services
AWS Organizations · AWS IAM · AWS IAM Identity Center · AWS Security Token Service (STS) · AWS Management Console · AWS CloudShell · AWS CLI v2 · AWS SDK for .NET v4 · AWS Toolkit for Visual Studio · Amazon S3 · AWS Lambda · Amazon CloudFront · AWS Billing and Cost Management · AWS Budgets · AWS Cost Explorer · AWS Pricing Calculator · AWS Well-Architected Tool
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: verify your setup with C#
Run a .NET 10 console app that uses your IAM Identity Center profile to call STS and S3, and prints the account, caller ARN and Region.
What cloud computing really is
Explain cloud computing in plain language, map it to your on-premises IIS and SQL Server experience, and reason about capacity, cost and agility like a cloud engineer.