Darasa Hub - Learning Lions
Dira Portal Safety and Welfare ICT Support
SCS2b.3

Your First Instance

Level 2 · BootCampSCS2b Cloud BasicsTaught week 4 Thursday morning

Start the Lesson

By the end you can say in one plain sentence what an EC2 instance is, make a key pair in your own Ubuntu and send AWS only its public half, fill a launch sheet before the console opens and launch one micro inside the sandbox rules with two tags on everything, come in by SSH and say why the machine does not know its own public address, serve your SCS2.3 site with nginx and find a stranger's request in the access log, answer "are only 22, 80 and 443 open?" with evidence from the console and from outside, find a fault a partner made from evidence, rebuild the machine from your log alone, and close the day with it stopped, not terminated.

Start the lesson 69 moves in 13 parts. You need: your portal sign-in and the phone with your MFA app · your profile scs-<handle> from SCS2b.2 · your copy of the SCS2b.3 folder, copied down from Mufasa · your SCS2.3 repo, public, and its clone address · your track repo from SCS1.4 · the campus address for the 22 rule and the micro size, from the board · a partner, or a phone on mobile data · your notebook and a pen

Submit Your Work

What You Turn In

  1. Two screenshots
    1. Your terminal with the SSH prompt on the instance beside the browser showing your site at the public address; the security group's inbound rules, exactly three rows fill in on the hub
  2. Repo link: cloud/instance-log.md
    1. The launch sheet as step 0; every step typed, expected, seen; the old and new address after the stop; the fault card with your guess note written before the reveal; any AI ask with its receipt; the rebuild from the log on top fill in on the hub
  3. Wall checklist, initialled by your partner fill in on the hub
    1. Evidence from the console and from outside: 8000 listening but not reachable, 443 refused not timed out
  4. Repo link: method note, VM-versus-instance card, the five handover lines
    1. Six lines, the sixth from a real difference between expected and seen; the card in your own words; five lines a client could follow fill in on the hub
  5. check-scs2b.3 receipt and the check-scs2b.3 --end receipt
    1. All PASS; the end-of-day sweep shows exactly one stopped instance, the SCS2b.2 site kept until SCS2b.5, and nothing else costing money

Stuck, or want to check your thinking? Paste this card into your own AI and ask it to question you, not answer for you.

How

  1. Asha, by Saturday's update.
Done when
  1. Two screenshots: SSH prompt beside the site at the public address; exactly three inbound rules
  2. Key pair, imported: ssh-keygen in own Ubuntu-SCS; private key in ~/.ssh at 600, not in the repo, a chat or the stick
  3. cloud/instance-log.md: Sheet as step 0; every step typed, expected, seen; both addresses; the guess note; the rebuild on top
  4. Wall checklist, partner-initialled: Console and outside: 8000 listening not reachable, 443 refused not timed out
  5. Fault card write-up: Guess before the reveal; what was looked at, in what order, what told them
  6. Method note + card + handover lines: Six lines, the sixth real; the card in own words; five lines a client could follow
  7. check-scs2b.3 and --end receipts: All PASS; the end sweep: one stopped instance, the SCS2b.2 site, nothing else costing money

Counts toward: the SCS2b.3 badge, 1 to 3 stars · the client's hosting line · attendance for the Taught and SGL blocks · LP (Lion Points) for accepted badge work.

Fill in the worksheet Submit work for SCS2b.3