Ticket intake
Capture requester, environment, business reason, affected resources, risk, approval, rollback, and verification.
CloudOps practice lab
Run AWS operations like a real ticket-driven platform team.
A seven-day lab for access requests, S3, networking, compute, monitoring, audit evidence, Terraform, Ansible, GitHub Projects, and GitHub Actions.
Queue
3
open ops tickets
Flow
PR
review before change
Proof
Audit
evidence per ticket
Operating model
What this lab simulates
Infrastructure change
Use Terraform for AWS resources and Ansible or SSM for server-level operations.
Review and automation
Move implementation through pull requests, validation checks, and approval gates.
Audit evidence
Attach plan summaries, verification notes, CloudTrail references, and rollback instructions.
Seven-day sprint
From ticket flow to interview story
This lab is designed to become speakable experience: not only "I learned AWS", but "I operated AWS changes through a controlled workflow."
Day 1Ticket flow, approvals, evidence
Day 2IAM and access management
Day 3S3, KMS, lifecycle, logging
Day 4VPC, Security Groups, NACLs
Day 5EC2, EBS, Ansible or SSM
Day 6CloudWatch, CloudTrail, Config
Day 7Demo, rollback, final story
Start points
Open the right artifact
Public lab portfolio
Three connected practice environments
These labs are meant to be read together: operations workflow, serverless event design, and Kubernetes platform delivery.