Set a budget alert first, then map the global infrastructure you can deploy to

Steps

1. Create the budget alert with AWS Budgets, before you do anything else. Print your account ID, then write the budget and its two notifications, and create it. The budget has a monthly cost limit of 1.00 USD. The first notification emails you when actual spend passes 1 percent of that limit, which is the first cent; the second emails you when AWS forecasts that the month will pass the whole limit.

aws sts get-caller-identity --query Account --output text
cat > clf-lab01-budget.json << 'EOF'
{
  "BudgetName": "clf-zero-spend-budget",
  "BudgetLimit": {"Amount": "1.00", "Unit": "USD"},
  "TimeUnit": "MONTHLY",
  "BudgetType": "COST"
}
EOF
cat > clf-lab01-notify.json << 'EOF'
[
  {"Notification": {"NotificationType": "ACTUAL", "ComparisonOperator": "GREATER_THAN", "Threshold": 1, "ThresholdType": "PERCENTAGE"},
   "Subscribers": [{"SubscriptionType": "EMAIL", "Address": "you@example.com"}]},
  {"Notification": {"NotificationType": "FORECASTED", "ComparisonOperator": "GREATER_THAN", "Threshold": 100, "ThresholdType": "PERCENTAGE"},
   "Subscribers": [{"SubscriptionType": "EMAIL", "Address": "you@example.com"}]}
]
EOF
aws budgets create-budget --account-id 111122223333 --budget file://clf-lab01-budget.json --notifications-with-subscribers file://clf-lab01-notify.json

Put your own email address in place of you@example.com in both places, and your own account ID in place of 111122223333. A successful create prints nothing. 2. Read the budget back where you will see it later. Open the Billing and Cost Management console and choose Budgets. The list shows clf-zero-spend-budget with a budgeted amount of 1.00 USD. This alert is how the variable cost from lesson 1 stays visible: you pay only for what you use, so you need to know when you have started to use something. 3. See how far you can reach without buying hardware. Count the Regions your account can deploy to now, then list the Regions it could opt in to:

aws ec2 describe-regions --query 'length(Regions)' --output text
aws ec2 describe-regions --all-regions --query "Regions[?OptInStatus=='not-opted-in'].RegionName" --output text

Each Region in the first count is somewhere you could deploy in minutes. That is "go global in minutes": no contract, staff or building is needed there. 4. Look inside your own Region. List its Availability Zones:

aws ec2 describe-availability-zones --query 'AvailabilityZones[].[ZoneName,State]' --output table

Count the rows. A workload with servers in only one of these zones has a single point of failure; spreading it across two or more is what high availability means in lesson 1. 5. Look at a Region on the other side of the world. Asia Pacific (Sydney) is enabled for every account:

aws ec2 describe-availability-zones --region ap-southeast-2 --query 'AvailabilityZones[].ZoneName' --output text

In lesson 1, a European company whose Australian customers saw slow pages fixed it by deploying in a Region close to Australia. You have just read that Region's zones from the same browser tab, which is the whole point: the infrastructure is already there. 6. Match each scenario to the one benefit it describes, then check your answers in the Notes. (a) A ticketing site adds servers for the hour when tickets go on sale and releases them afterwards. (b) Web servers in two Availability Zones keep serving when one zone fails. (c) Test environments that took weeks to arrive now take minutes. (d) A company serves customers on a new continent within days. (e) Staff no longer replace failed disks or manage cooling. (f) A small firm pays the same low prices as a very large one because AWS combines the usage of many customers.