Activities

What we learn, build, and reflect on together, one cohort at a time.

  • PresentationSession 01

    Why We Learn AWS Together — ASBG UOS Cohort 1 Kicks Off

    Opening Cohort 1: what ASBG UOS is and why we learn AWS together. Why we grow one service over the semester instead of clicking through services one by one, how the group handles the cost worries and isolation that stop people who start alone, and why certifications come after.

    • #Community
    • #Hands-on
    • #Curriculum
  • PresentationSession 01

    Beyond Code, Into Service

    Learning back-end and front-end got me to the point of building a service, but building one and running one turned out to be different jobs. What the cloud makes cheap and fast for a startup that keeps trying things, and why it still isn't free, with Airbnb as the example.

    • #Operations
    • #Startup
    • #Iteration
  • PresentationSession 01

    Learn the Cloud, Then Do What?

    Where cloud skills actually take you: the CSP, MSP, and customer sides of the industry, how SA, cloud engineer, DevOps, and SRE roles differ, one customer request followed step by step as the architecture grows, and what you need to know to explain each choice.

    • #Career
    • #High Availability
    • #Learning Path
  • PresentationSession 01

    A First-Year Developer's Strategy for the AI Era

    A year after graduation, building a smart-building digital twin: what's left for a developer now that AI writes the code, the gap between what I hand off to AI and what I can verify myself, and why closing that gap led me to the cloud.

    • #AI Delegation
    • #Verification
    • #Domain Knowledge
  • PresentationSession 02

    From Network Basics to AWS Services

    Only the network terms you really need, IP and ports, TCP and UDP, and CIDR, then one picture to hang AWS on: a VPC inside AWS, subnets inside the VPC, EC2 inside the subnets. On top of it, what goes in public and private subnets, which paths requests take in and out, and what NACLs and security groups each guard.

    • #Network Basics
    • #VPC
    • #Subnet
  • PresentationSession 02

    What Is a 3-Tier Architecture?

    A website runs fine with the web server, application, and database all on one server. So why split them into separate environments by role? Access control, scaling each tier on its own, and keeping resources and changes contained, plus why not every service needs it. Then the hands-on: deploying your own web page with Nginx on a single EC2 instance, and watching one security group rule block access and open it again.

    • #3-Tier
    • #EC2
    • #Nginx
  • PresentationSession 03Upcoming

    Serverless Event-Driven Services

    • #Lambda
    • #SQS
    • #EventBridge
  • PresentationSession 04Upcoming

    Moving to Container-Based Microservices

    • #ECS
    • #ECR
    • #CodePipeline
  • PresentationSession 05Upcoming

    Integrated Service Architecture Design and SAA-C03 Practice

    • #Architecture
    • #SAA-C03
    • #Trade-offs