Why Cloud Computing Is the Most In-Demand Skill Right Now

Save the JSON below as scaling-policy.json, then apply it with:
aws autoscaling put-scaling-policy --cli-input-json file://scaling-policy.json
The group then adds servers when busy and removes them when quiet.

{
  "AutoScalingGroupName": "web-asg",
  "PolicyName": "keep-cpu-near-50",
  "PolicyType": "TargetTrackingScaling",
  "TargetTrackingConfiguration": {
    "PredefinedMetricSpecification": {
      "PredefinedMetricType": "ASGAverageCPUUtilization"
    },
    "TargetValue": 50.0
  }
}

Festival sale traffic: old way vs cloud way

Old way:
- Buy enough servers for the busiest day of the year
- Most of that capacity sits idle the rest of the year
- Months of planning and purchase approvals

Cloud way:
- Run a small baseline most of the year
- Auto scaling adds capacity during the sale
- Capacity shrinks again afterwards
- Pay mainly for what was actually used

Someone has to design, test and monitor this - that is a cloud job.

# A minimal AWS Lambda handler in Python
# Deployed behind an API, it runs only when called
import json

def lambda_handler(event, context):
    name = (event.get("queryStringParameters") or {}).get("name", "learner")
    return {
        "statusCode": 200,
        "headers": {"Content-Type": "application/json"},
        "body": json.dumps({"message": f"Hello, {name}!"}),
    }

# pip install boto3  (uses your configured AWS credentials)
import boto3

s3 = boto3.client("s3")
bucket = "my-analytics-practice-12345"

# Upload a local CSV for analysis
s3.upload_file("sales.csv", bucket, "raw/sales.csv")

# List files in the raw folder
resp = s3.list_objects_v2(Bucket=bucket, Prefix="raw/")
for obj in resp.get("Contents", []):
    print(obj["Key"], obj["Size"])

IAM policy (JSON): this user can read one bucket - nothing else.
Start narrow and add permissions only when needed.

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Sid": "ReadReportsBucketOnly",
      "Effect": "Allow",
      "Action": ["s3:GetObject", "s3:ListBucket"],
      "Resource": [
        "arn:aws:s3:::company-reports",
        "arn:aws:s3:::company-reports/*"
      ]
    }
  ]
}

Cloud cost habits employers look for

[ ] Budget alerts on every account
[ ] Tags on every resource: Project, Owner, Environment
[ ] Stop or delete idle resources (especially after labs)
[ ] Choose the smallest instance that meets the need
[ ] Use storage tiers for old or rarely used data
[ ] Review the bill weekly and explain any jump

Mentioning these in interviews shows real-world maturity.

Week 1  Cloud concepts: regions, IaaS/PaaS/SaaS, shared responsibility
Week 2  Account safety: MFA, IAM users/roles, budget alert
Week 3  Compute: launch, connect to and stop a virtual machine
Week 4  Storage: object storage, permissions, static website
Week 5  Databases: a managed database for a small app
Week 6  Serverless: a function behind an API
Week 7  Monitoring and logs
Week 8  Mini project + architecture diagram + clean-up

Add cloud to your current path

Developer:  deploy your existing app to cloud; add CI/CD
Analyst:    move your dataset to object storage; query it
            in a cloud warehouse
Tester:     run your test suite in a cloud CI pipeline
Security:   review IAM policies and enable logging

Pick one add-on and finish it in 4 weeks.

Can I...
[ ] Explain the shared responsibility model?
[ ] Secure a new account (MFA, no root usage)?
[ ] Deploy and remove a small app?
[ ] Write a least-privilege policy?
[ ] Set a budget alert and tag resources?
[ ] Draw my project's architecture?

6 ticks: ready for an associate-level certification