Cloud › Module 1 › Lesson 4
Lab — Setup
Pack cloud scope, account inventory, and ethics card — lab setup file only, dest $CLOUD_LAB.
Visual · t31_lab_setup
Lab: write cloud setup pack. $CLOUD_LAB only. Original Cyberlium.
Opening
Lab setup before cloud CLI — scope paperwork cloud mentors expect.
Lessons 1–3 defined why cloud security matters, your accounts only, and stranger-tenant refusal. This lab ships the combined artifact: topic scope paragraph, account inventory row, and ethics card for $CLOUD_LAB under $HOME/cyberlium-lab/t31-cloud/. No stranger tenant access required — scope and account paperwork first. Next: Quiz — Cloud Mindset and Lab.
1. Lab contract: write the setup pack
Create $HOME/cyberlium-lab/t31-m01-l04-lab-setup.txt with date, operator, $CLOUD_LAB account placeholder, literacy vs unauthorized tenant paragraph, account inventory row, and ethics card.
Optional: one-line proof your t31-cloud folder exists — still no stranger tenant work required in this lab.
Command guide
Try these commands — Lab contract: write the setup pack
═══ TOOLS & WEBSITES ═══ Browse / read these (authorized learning only — stay in YOUR lab / program scope)
AWS CLI configure — https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-quickstart.html Azure CLI login — https://learn.microsoft.com/en-us/cli/azure/authenticate-azure-cli Checkov — https://www.checkov.io/1.Welcome/Quick%20Start.html
═══ INSTALL ═══
Linux (Debian/Ubuntu):
Command — copy this
sudo apt install curl
macOS: Built-in
Windows: Built-in (PowerShell: Invoke-WebRequest)
═══ LINUX / macOS ═══
Command — copy this
export CLOUD_LAB=${CLOUD_LAB:-$HOME/cyberlium-lab/t31-cloud}
cat > "$CLOUD_LAB/roe.txt" <<'EOF'
CLOUD_LAB=$HOME/cyberlium-lab/t31-cloud
targets: YOUR AWS account, YOUR Azure subscription, YOUR docker images, YOUR local kind cluster
never: stranger S3 buckets, prowler on unauthorized orgs, container escape PoCs
allowed: mkdir notes, IAM/S3/CloudTrail checklists, aws sts get-caller-identity (YOUR ACCOUNT)
allowed: az account show (YOUR subscription), docker ps/inspect, trivy/checkov on YOUR assets
output: checklists, yaml stubs, finding writeups in lab folder
EOFCommand — copy this
chmod 600 "$CLOUD_LAB/roe.txt" grep -E 'CLOUD_LAB|never|allowed|YOUR' "$CLOUD_LAB/roe.txt" command -v aws >/dev/null && aws --version || echo 'aws CLI not installed — install for YOUR account literacy' command -v az >/dev/null && az version || echo 'az CLI not installed — install for YOUR subscription literacy'
═══ WINDOWS ═══
Run on YOUR lab Windows VM only
Command — copy this
Get-Content $HOME/cyberlium-lab/t31-cloud/roe.txt | Select-String never
aws --version 2>$null; if (-not $?) { Write-Output 'Install AWS CLI for YOUR account literacy' }Primary tools to practice this lesson: grep, curl. Reference sites: AWS CLI configure (https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-quickstart.html); Azure CLI login (https://learn.microsoft.com/en-us/cli/azure/authenticate-azure-cli); Checkov (https://www.checkov.io/1.Welcome/Quick%20Start.html). Run every command in the box — install first, then the usage lines — only on YOUR lab / program scope.
2. Cross-check against misuse patterns
Grep notes for 'leaked key,' stranger account IDs, live customer resource names, exploit scripts, or victim cloud exports — redact or delete. Rewrite forum habits to $CLOUD_LAB placeholders before you copy workflows.
Classmates build their own setup packs for their $CLOUD_LAB — not yours.
3. Lock the proof
chmod 600 on the pack. Quiz is next — then Shared Model.
Cloud mentors archive lab setup before first sandbox console login; you are practicing that habit early.
4. What you ship: cloud lab setup pack for $CLOUD_LAB
Setup pack: scope, account row, ethics card. $CLOUD_LAB named. NEVER stranger tenants. chmod 600.
5. What you record before the next lesson
Date. Setup pack path. $CLOUD_LAB scope note. File t31-m01-l04-lab-setup.txt chmod 600.
6. Wrong vs right: stranger tenants vs YOUR cloud accounts
Worked failure — same MSF word, opposite target. Right never needs a café Wi-Fi or classmate laptop.
Wrong
Skip the file and scan unknown AWS account. Add employer subscription to approved list.
Right
Write YOUR lab setup pack for $CLOUD_LAB. chmod 600. Next: Quiz — Cloud Mindset and Lab.
Mission: freeze YOUR cloud lab setup pack on disk
1) Merge scope, account, ethics sections. 2) Name $CLOUD_LAB. 3) chmod 600. Never list stranger tenant scanning as approved practice.
Stuck? Ask Cyberlium AI Mentor
Setup packs are boring on purpose — boring keeps cloud work defensible.
Knowledge Check
APPLY: This lab requires:
Multiple choice
Knowledge Check
APPLY: True or False: You should chmod 600 on cloud lab notes.
True or False
Knowledge Check
APPLY: A tutorial scans stranger S3 buckets without scope. You:
Multiple choice