ASBG UOS
koen

AWS Student Builder Groups at University of Seoul

Put your work online,
then keep it running.

We're the official AWS student community at the University of Seoul. We take what classes taught us, deploy it on real servers, and find out first-hand how traffic and cost behave, each in our own account. It's easier to get unstuck together.

Explore activitiesMeet the members
  • 01Learn
  • 02Build
  • 03Share
  • 04Connect
LearnBuildShareConnect
ASBG UOS

01

18

Active members

02

6

Talks given

03

1

Cohorts

01Why

We start where the syllabus stops

  • An official student community AWS runs at universities worldwide
  • Part of a network of ASBG chapters across Korea
  • The first AWS Student Builder Group at the University of Seoul

There are plenty of courses on how to build things: programming languages, data structures, databases, AI. But the last step, putting what you built on the internet and keeping it up, isn't on any syllabus. Most of us learned it by searching and breaking things on our own.

People usually get stuck for one of two reasons. Either VPCs, subnets, IAM and load balancers all show up at once and there's no obvious place to start, or the fear of a forgotten resource turning into a bill stops them before they even open an account. There was nowhere on campus to work through this together, so we made one.

  1. Class

    Make

    Languages, data structures, databases, AI. Classes cover this part well.

  2. ASBG UOS

    Ship

    Getting what you built onto a server so real people can use it.

  3. ASBG UOS

    Keep

    Keeping it running through traffic spikes without the bill getting away from you.

ASBG UOS is for those last two.

02What we do

What happens when we meet

The format shifts a little from cohort to cohort, but a session is usually one of these four.

  • 01

    Hands-on Workshop

    AWS infrastructure, serverless and containers, following the official labs on AWS Workshop Studio. Slides are short; the rest happens in your own console.

    • #Workshop Studio
    • #Lambda
    • #Kubernetes
  • 02

    Tech Talk

    Short talks on a topic someone picked: where the cloud industry is heading, or how a real company actually uses AWS. Sometimes the speaker is a practitioner, sometimes a member who dug in first.

    • #Case Study
    • #Trends
    • #Q&A
  • 03

    Certification Study

    CLF, SAA, SAP. Small groups work through past questions and explain the ones they got wrong to each other. Certifications are hard to start alone.

    • #CLF
    • #SAA
    • #SAP
  • 04

    Networking

    Joint sessions with other ASBG chapters, AWS's global student community events, and chances to meet people working in the field. Official events go up on Meetup.

    • #Guest Talk
    • #ASBG Network
    • #Meetup

03Cloud, in one picture

One request, there and back

The cloud is someone else's data center, and you rent only the parts you need. Instead of buying a machine, you switch servers on and off with a few clicks and pay for what you used. The picture below follows one request from the moment you type a URL until the response comes back, and most of the names that come up in our sessions are on it.

AWS AccountAuto Scalingadds or removes serversUsersa browserRoute 53find the addressCloudFrontanswer nearbyALBspread requestsEC2run the appEC2run the appEC2run the appRDSdatabaseS3file storageIAMpermissionsCloudWatchmetrics and logsBudgetsbudget alerts

Goal

The order we cover them in changes from cohort to cohort. The goal is that by the time your cohort wraps up, you can draw this picture yourself and explain it.

  1. 01

    Find the address, answer from nearby

    When you type a URL, Route 53 says which server to go to. Things that get requested constantly, like images and static files, CloudFront serves from a location near you, so they never reach the server at all.

  2. 02

    Spread the requests out

    Whatever CloudFront couldn't answer goes to the ALB, the load balancer. It spreads requests evenly across several servers, and if one dies it simply stops sending traffic there. From the outside you can't tell how many servers there are or which one dropped.

  3. 03

    Servers grow and shrink

    The app itself runs on a fleet of EC2 instances or containers. Auto Scaling watches traffic and adjusts the count: fewer overnight, more during the day. That costs a lot less than running everything at full size around the clock, and it's why you don't have to buy more servers than you need up front.

  4. 04

    Data lives somewhere safer

    Servers scale up and down and occasionally get replaced, so anything stored on them goes with them. The database lives in RDS and files live in S3, away from the servers. Separating compute from storage is close to the first rule of cloud design, and if you follow it you can swap servers out and lose nothing.

  5. 05

    And keep an eye on it

    IAM decides who can do what, CloudWatch shows metrics and logs, and Budgets warns you before you blow past your spending limit. This is also the first thing you set up on day one.

Edge

  • Route 53
  • CloudFront
  • WAF

Compute

  • EC2
  • ECS / EKS
  • Lambda
  • Auto Scaling

Data

  • RDS
  • DynamoDB
  • S3

Ops

  • IAM
  • CloudWatch
  • Budgets
  • Terraform

04Four words

Learn, Build, Connect. Then we added Share.

AWS Student Builder Groups run on three words: Learn, Build, Connect. We added a fourth, Share, for presenting what you built and explaining why.

  • Learn

    Basics first, in order. We look at why a service exists before memorizing its name.

  • Build

    We don't stop at reading. We launch it, break it, and tear it down.

  • Share

    Present what you built and explain the choices. This is the one we added.

  • Connect

    It starts on campus and reaches ASBG chapters nationwide and people in the industry.

05Contact

Questions? Email us

Questions about the club, topics you'd like a session on, or an offer to come speak: send them all here. We reply within two or three days, every time.

Click to copy