AWS Cloud Practitioner
AWS vocabulary primer. Useful for first cloud roles, transparent at any senior level.
AWS vocabulary primer. Useful for first cloud roles, transparent at any senior level. Pursue if: You're targeting first cloud role; Your employer pays for it. Avoid if: You can ship a small Terraform stack already, go straight to SAA.
In context
This cert in isolation tells you very little. Here is where it actually sits. The pathways that use it, and the roles it realistically supports.
Recommended prior knowledge
- A free-tier account and 2 weeks of poking
Common misconceptions
- It helps with junior cloud screening. It does not unlock engineering roles on its own.
- AWS Cloud Practitioner alone clears HR filters; it doesn't replace shipped, documented work.
What this cert does NOT guarantee
- Engineering roles on its own
- Any architecture conversation
Practical skills that matter
- Junior cloud screening
- Internal mobility from helpdesk
- Pre-SAA confidence
Where this fits
A cert is only useful for some routes. Here's where this one earns its place.
- Cloud Engineer → Cloud Architect
Highest-paid generalist track. Stack: networking + Linux + cloud + IaC.
- Cloud Security Engineer
Cloud-native IAM, workload security, policy-as-code. Entered from cloud, not from SOC.
- Platform / DevOps Engineer → SRE
Build the systems other engineers depend on. Requires coding fluency. Rarely entry-level.
The serious next step
A cert is a signal. A Career Verdict tells you whether the signal is worth sending.
A Career Verdict tells you whether this cert earns its place on your specific route, what it won't fix, and what to sit before or after it.
Built on POST's practitioner-authored assessment framework, calibrated by James from twenty years across helpdesk, infrastructure and security. Framework is human-authored; the verdict applies it to your inputs.