[ 01 ]—AWS
AWS IAM Least Privilege Without the Pain
Long-lived admin keys are how quiet accounts become loud incidents. OnesDev designs IAM so people and pipelines get the access they need — and nothing more — without freezing delivery.
Prefer roles over forever users
Humans assume roles with MFA. Apps assume roles via instance profiles, IRSA, or similar — not embedded access keys in repos. CI assumes a deploy role scoped to what the pipeline must change. This pairs cleanly with Terraform habits.
Start broad, then tighten with evidence
- Ship with a role that can do the job (documented)
- Use Access Analyzer / last-used signals to trim unused actions
- Add condition keys (source IP, MFA, VPC) where they reduce risk
- Review privilege quarterly with the account owner
Break-glass without drama
Keep a tightly audited admin path for emergencies. Log every use. Rotate credentials after. Break-glass is part of incident response— not a second root password in a chat channel.
Boundaries and landing zones
Permissions boundaries and SCPs stop accidental privilege creep when teams create roles. Multi-account layout makes blast radius smaller — see landing zones for product teams and the broader land, run, optimize path.
Next step
Explore AWS services or share how access works today (users, keys, SSO) — we will propose a least-privilege plan that still lets you ship.
OnesDev Engineering Team
Full-Stack & Cloud PracticeEngineers building and operating production Laravel, MERN, WordPress, and AWS cloud systems worldwide.
✓ AWS Certified Architects & Senior Full-Stack Engineers
[ 02 ]—Related