[OK] COPIED TO CLIPBOARD:
DISCIPLINE //
PLATFORM ENGINEER [AWS]
ENGAGEMENT STATUS //
OPEN FOR B2B CONTRACTS
[00] SYSTEM THESIS
I MAKE YOUR PLATFORM WORK BETTER.
I build and simplify critical cloud infrastructure. Operating independently from Europe, I partner with engineering teams to turn fragile, over-engineered cloud estates into calm, predictable systems.
My approach is grounded in first principles: understanding how systems fail, automating infrastructure changes, applying least-privilege security, and measuring what actually matters.
[01] ENGINEERING INVARIANTS
-
01. OWNERSHIP: Every system, deployment and operational decision has a clear owner.
-
02. LEAST PRIVILEGE: Every role gets exactly the access it needs. Nothing more.
-
03. RELIABILITY: Failures are anticipated, observable and documented. Every critical incident has a known first response.
-
04. SIMPLICITY: Every abstraction must justify its operational and cognitive cost.
[02] CASE STUDIES
CASE // 01
Multi-account AWS baseline
Fragmented accounts, no shared guardrails, a bill nobody could attribute. Consolidated into one baseline: accounts, network, access and cost visibility.
CASE // 02
Least-privilege access
Admin by default, keys without rotation, nobody reviewing. Every role rebuilt to what it actually needs — plus a review that keeps it that way.
CASE // 03
Deploys that stopped being events
Releases planned around fear. Pipeline, environments and rollback reworked until the Friday deploy stopped being a group decision.
CASE // 04
Alerting that respects on-call
Alerts nobody trusted and a rota nobody envied. Signals cut down to what indicates a real failure — each one with a runbook.
ADRIAN ROSZAK · AWS PLATFORM ENGINEERING