Sydney AWS Workshops

Learn AWS by building it, then prove it works.

Six hands-on sessions that take you from a static site on S3 to a full-stack app with monitoring. You build in your own account, and our Lab Checker verifies every step against your real resources.

Join the meetup Open the Lab Checker

6Hands-on sessions

26Automated lab checks

FreeCommunity workshops in Sydney

How the workshops work

Build it yourself, in your own account

Every session is practical. You leave with something running that you built, and a way to check that you built it correctly.

Hands on, not slides

You work in a real AWS account and deploy real resources. The teaching happens while you build, not before it.

Verified by the Lab Checker

Enter your bucket, instance or role and the checker inspects your account with read-only calls, stamping each step pass or fail.

Hints, not just fails

Every failed check points you back to the exact step to revisit, so you fix it yourself instead of waiting for a demonstrator.

The curriculum

Six sessions, one working stack

Cert-aligned and job-ready. Each session builds on the last, and finishes with a lab the checker can verify.

Host a static website on S3

Buckets, static website hosting, public access policy and how a request actually reaches your page.

Checked: bucket exists, hosting enabled, public reads allowed, index.html uploaded, website URL serves your page.

Launch an EC2 web server

Instances, key pairs, security groups and what it takes to get a web server answering on port 80.

Checked: instance running, public IP assigned, security group allows HTTP, web server responds.

Build a least-privilege IAM role

Trust policies, permissions policies, and why wildcard and admin access is the habit that breaks accounts.

Checked: role exists, trust policy is correct, permissions attached, no admin or wildcard policies.

Deploy a serverless REST API

Lambda, DynamoDB and API Gateway wired into an endpoint that returns real data from a table.

Checked: Lambda active, DynamoDB table has a partition key, API returns HTTP 200 and valid JSON.

Provision a production-shaped RDS database

The difference between a database that works and a database you can defend in an audit.

Checked: instance available, NOT publicly accessible, automated backups on, storage encrypted.

Capstone: full-stack app with monitoring

Put it together: a frontend, an API and a CloudWatch alarm that actually tells someone when it breaks.

Checked: frontend serves HTML, API responds with JSON, CloudWatch alarm exists and has a notification action.

Verify a lab you have finished

Two things people ask

Safe by design, and teardown is graded too

The checker is read-only

It only inspects. It never creates, changes or deletes anything in your account, and it runs with a role limited to read-only actions. You can open the check files and see exactly what it does.

Clean up when you are done

Cloud bills come from things you forgot to delete. After teardown, run the checker again: a red FAIL on step 1 is your proof of a tidy account, and that is the point.