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

The Cheapest Website

Level 2 · BootCampSCS2b Cloud BasicsTaught week 4 Wednesday morning

Start the Lesson

By the end you can say in one plain sentence what S3 is, ask the three questions that decide whether a site needs a server and decide your own client's site with them, sign in from the command line with no key on the laptop, make a bucket in the one region named by the rule and tagged Name and Owner, put your committed site in it after reading the dry run aloud, set up the road the campus ICT department allows and read its policy field by field, prove from outside that a stranger can read your site and nothing more, point one record at it and say what the record could not carry, and end the day with a sweep that shows your site and nothing else.

Start the lesson 70 moves in 15 parts. You need: your portal sign-in and the phone with your MFA app from SCS2b.1 · your copy of the SCS2b.2 folder, copied down from Mufasa · your SCS2.3 site, committed, in ~/scs/projects/<client-slug>-site · your track repo from SCS1.4 · your practice subdomain from SCS2.7 · a phone on mobile data, your own, a partner's or one from the lab pool · the allowed region and the road of the day, from the board · your notebook and a pen

Submit Your Work

What You Turn In

  1. URL receipt and phone screenshot
    1. The live address on your sheet; the site on your phone on mobile data, not signed in, with the address visible
  2. check-scs2b.2 receipt
    1. Bucket in the one region, named by the rule, tagged Name and Owner; the committed site and nothing never-public; every NOT YET fixed or explained
  3. Stranger-test lines
    1. The listing refused, a write refused, a wrong address showing your own 404 page
  4. dig output, before and after
    1. Your practice subdomain pointed at the site with one record, proved from two resolvers; what changed, what did not, what the record could not carry
  5. Repo link: cloud/deploy-log.md and the method note
    1. Every step in three parts; the policy pasted and explained field by field with the AI receipt; the commit deployed and the redeploy on top; six lines, the sixth 'what I might be wrong about, and how I would find out'
  6. Decision card and the client recommendation
    1. Eight cases sorted; your client's site decided, server or no server, with a reason and a monthly cost for each path in words the owner can read
  7. cloud-sweep receipt
    1. Only today's site costing money; the site on the 'what is running' list for SCS2b.5

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. URL receipt + phone screenshot: The live address; the site on a phone on mobile data, not signed in, address visible
  2. Bucket, tagged and on the road: One region, name by the rule, Name and Owner tags; the committed site, nothing never-public; the 403 recorded
  3. Policy annotated + AI receipt: Every field explained; any grant beyond s3:GetObject struck with the reason; road B: the Condition explained
  4. Stranger test + error page: Listing refused, a write refused, a wrong address shows the trainee's 404 page
  5. dig output + the three lists: Own subdomain pointed with one record, two resolvers; what the record cannot carry; the padlock named
  6. Deploy log with the redeploy: Every step in three parts; commit hash; the SGL redeploy; check-scs2b.2 all PASS or explained
  7. Decision card + recommendation: Eight cases sorted; the client's site decided with a reason and a monthly cost for each path
  8. cloud-sweep receipt + method note: Only today's site costing money; on the 'what is running' list; six lines, the sixth real

Counts toward: the SCS2b.2 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.2