AWS for a DevOps / Platform
Provision, secure, and automate — least-privilege IAM, pipelines, and infrastructure as code.
Services that matter
Artifact and state buckets, lifecycle rules that expire old objects before they cost real money, versioning for recoverability, and access logging for audit. An S3 bucket policy is frequently the first place a least-privilege review starts.
Relevant to this role.
Relevant to this role.
Relevant to this role.
Relevant to this role.
Relevant to this role.
Build it, graded
Object storage, static hosting, and public read access — provisioned in CDK, not clicked through a console.
The zero-to-one project: create an AWS account, install the toolchain, and go from `cdk init` to a real `cdk deploy` in TypeScript or Python.
Instance types, machine images, firewall rules, and boot-time scripts — provisioned in CDK, not clicked through a launch wizard.
Event-driven functions, pay only for the compute time used — provisioned in CDK, not clicked through a console.
A managed front door for a backend — provisioned in CDK, wired straight to Lambda, no server ever runs.
A managed NoSQL table — provisioned in CDK, queried by partition key, never scanned end to end.
A static frontend on S3, wired to a real backend — and the two ways that wiring quietly breaks.