Task 5: The Infrastructure on AWS

In this task you create the place the app runs, and let the pipeline reach it.

Let GitHub Actions into AWS

• An OIDC identity provider and a role that only main of your repository may assume: the steps are in Pipeline Identities, Part 4.
• TODO: Terraform, or the console; and where its state lives.

Estimate what the EKS cluster costs

An EKS cluster is paid for by the hour, from the moment it exists, whether the app runs or not. So the cost follows the hours it exists, not the hours you work.

The hourly price of what this project creates, in us-east-1:

The traffic a student sends costs cents, and is left out.

For a student working 20–30 hours a month:

• Create the cluster at the start of each session, and destroy it at its end.
  • Creating takes about 15 minutes and destroying about 10, so each session adds about half an hour.
  • In about 8 sessions a month, that is 4 more hours: 24–34 hours of cluster.
• A month: 24–34 hours × $0.27 = about $6.50–$9.20.
• 2–4 months: about $13–$37 in all.
• Left running, the same cluster costs $0.27 × 730 hours = about $200 a month, and $6.50 for every day it is forgotten.
  • An AWS budget with an e-mail alert, at $20 a month, catches a forgotten cluster in days.

Create the target

Check the target by hand

• Run the image from Task 4 on it once, by hand, and call /healthz.