Skip to Content
Cloud Engineering Academy
0. Orientation & a Safe Learning Environment

Module 0: Orientation & a Safe Learning Environment

Set up a locked-down, cost-guarded AWS learning environment and a Windows toolchain before you build anything.

beginnerโฑ 8 h ๐ŸŸข FreeCLF-C02

Assumes: .NET 10 LTS ยท AWS SDK for .NET v4 ยท AWS CLI v2 ยท Region us-east-1. Verified against official sources on 2026-11-17.

Before you write a single line of AWS code, you need two things that a bank would never skip: a safe place to experiment and controls that stop mistakes from becoming bills or incidents. This module builds both. By the end you will have an AWS environment shaped like a miniature version of a bank's landing zone, a Windows toolchain that signs in without long-lived keys, and habits that keep your learning close to free.

Analogy: Think of this module as setting up a training branch before staff start work. You lock the master vault key away (root user), issue staff badges that expire every evening (IAM Identity Center), put the training room in a separate building (sandbox account), install spending alarms on the tills (budgets) and agree that the room is cleared every night (teardown).

Learning objectives

By the end of this module you can:

  • Explain how this platform is organised, what the cost labels mean and how to use the AI assistant without leaking secrets or customer data.
  • Lock down an AWS root user, create an IAM Identity Center user with MFA and use permission sets instead of IAM users with access keys.
  • Create an AWS Organization with a separate sandbox member account and attach a service control policy (SCP) that restricts Regions.
  • Explain the AWS Free plan vs Paid plan for accounts created after 2025-07-15 and why joining AWS Organizations changes your plan.
  • Configure AWS Budgets, a CloudWatch billing alarm and Cost Anomaly Detection, and name the usual cost traps.
  • Install and configure the Windows toolchain: .NET 10 SDK, AWS CLI v2 with sso-session profiles, an AWS Toolkit for your IDE, SAM CLI, CDK CLI, Terraform, a container runtime, Git and Python.
  • Choose a zero-cost local option (AWS Emulator, LocalStack Hobby, DynamoDB Local, SAM local, Testcontainers) and say what local emulation cannot prove.
  • Run a teardown checklist that finds anything still costing money.
  • Run a C# console app that proves your SSO profile works by calling STS and S3.

Prerequisites

  • A Windows 10/11 PC where you can install software (administrator rights for some installers).
  • A personal email address you control, a phone for MFA, and a payment card (AWS asks for one at sign-up even on the Free plan).
  • No AWS knowledge is assumed. You should already be comfortable with C#, the dotnet CLI and Visual Studio or VS Code.

Use a personal account, not your employer's

Do these exercises in an AWS account you own. Never use your bank's AWS accounts, credentials or data for self-study, and never copy work data into a personal account. If your employer provides a training sandbox, follow its rules instead of the setup here.

Estimated time and cost

ItemEstimate
Study timeAbout 8 hours (reading 5 h, hands-on 3 h)
AWS cost$0 if you follow the guardrails. Everything in this module is free: Organizations, IAM Identity Center, SCPs, Budgets (non-action), Cost Explorer in the console and Cost Anomaly Detection
Local toolsFree, with one licence check: Docker Desktop is free for personal use, education and small businesses only โ€” see Tooling setup

Certification alignment

This module supports AWS Certified Cloud Practitioner (CLF-C02):

CLF-C02 domain (weight)What this module covers
Domain 2 โ€” Security and compliance (30%)Root user protection, MFA, IAM Identity Center, least privilege, Organizations and SCPs, shared responsibility
Domain 4 โ€” Billing, pricing and support (12%)Free Tier plans, AWS Budgets, Cost Explorer, Cost Anomaly Detection, consolidated billing, pricing traps
Domain 3 โ€” Cloud technology and services (34%)Ways to access AWS (console, CLI, SDK, IDE toolkits), Regions

It also lays groundwork for SAA-C03 (multi-account design, SCPs) and SCS-C03 (identity and governance), which later modules build on.

Lessons in this module

#LessonTypeCostTime
1How this platform worksLessonfree30 min
2Secure your AWS accountLessonfree90 min
3Cost guardrailsLessonfree60 min
4Tooling setup on WindowsLessonfree90 min
5Zero-cost local practiceLessonfree60 min
6Teardown disciplineLessonfree45 min
7Microsoft-to-AWS overviewLessonfree30 min
8Lab: verify your setup with C#Labfree45 min

Do them in order: lessons 2 and 3 must be finished before you deploy anything in later modules.

The target setup

This is what you will have at the end of the module. It is a deliberately small version of the multi-account "landing zone" pattern that banks use (Module 15 covers the full version).

Reading the diagram:

  • The management account pays the bill and holds the organisation-wide controls. You almost never work in it.
  • The sandbox account is where labs run. If something goes wrong there, it cannot touch the management account, and the SCP stops it from using unexpected Regions.
  • You never hold long-lived access keys. You sign in through IAM Identity Center in a browser (with MFA); the CLI, SDK and IDE then use temporary credentials that expire.
  • Budgets and alarms watch the whole organisation, so a forgotten resource in the sandbox still triggers an email.

How this module maps to your Microsoft experience

You knowIn this moduleFirst difference to notice
Azure tenant + subscriptions + management groupsAWS Organization + accounts + organisational units (OUs)In AWS the account is the hard isolation and billing boundary, like a subscription โ€” but identities live in Identity Center, not in each account
Entra ID users, Privileged Identity ManagementIAM Identity Center users and permission setsA permission set becomes an IAM role in each account it is assigned to
Azure Policy deny assignmentsService control policies (SCPs)SCPs only limit permissions; they never grant any
Azure Cost Management budgets and alertsAWS Budgets, Cost Explorer, Cost Anomaly DetectionBilling data and the billing alarm metric live in us-east-1
az loginaws sso loginProfiles in %USERPROFILE%\.aws\config select account + role
Azurite, Cosmos DB emulatorAWS Emulator, DynamoDB Local, LocalStackEmulators do not evaluate IAM like AWS does

A fuller table is in Microsoft-to-AWS overview.

Module checklist

  • Root user has MFA, no access keys and alternate contacts set
  • I sign in daily through IAM Identity Center, never as root
  • A sandbox member account exists inside an AWS Organization
  • A Region-restricting SCP is attached to the sandbox OU and I have tested it
  • Zero-spend budget, monthly budget, billing alarm and Cost Anomaly Detection alerts are active and I received the confirmation emails
  • aws sts get-caller-identity --profile learn-sandbox works
  • The lab app prints Result : PASS
  • I can list five cost traps and how to find them

Further reading

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