AWS Learning Journey

Your AWS Certification Roadmap — and the Capstone That Ties It All Together

Which AWS certifications to take, in what order, how they map to everything you've built in this series — and a final walkthrough of the complete capstone architecture.

12 min read · 2272 words
AWS CertificationAWSCloud ComputingCareer DevelopmentData Engineering
Your AWS Certification Roadmap — and the Capstone That Ties It All Together cover image

AWS from Zero to Production — Phase 12, Part 1 of 1 · See the full series roadmap


If you’ve followed this series from the start, look at what you’ve done.

You set up a secure AWS account. You built a VPC by hand. You shipped a container to ECS, connected it to a private database, and rotated its password live. You rebuilt everything in Terraform, deployed it from GitHub with no stored keys, and watched the pipeline roll itself back. You built a dashboard that diagnosed an outage in a minute, a data platform from a production database, and an AI assistant that cites its sources.

That’s not a tutorial collection. That’s the work of a cloud engineer.

This final article answers two questions: How do you prove it? And how does it all fit together?

What you’ll walk away with


Are certifications worth it?

Certifications are optional. Hands-on skill is what makes you effective — and that’s what this series focused on.

But certifications are useful:

The best approach: build first, then certify. The exam becomes a review of things you’ve done, not facts you memorized.


Certification levels

AWS organizes certifications into levels:

The current lineup

Foundational

Associate

Professional

Specialty

Check before you plan: AWS updates its catalog regularly — exams are added, renamed, updated, and retired. Always confirm the current exam and its exam guide on the AWS Certification site.


The recommended path

This path matches the series — and a career in cloud and data engineering.

Step 1: Foundation — AWS Certified Cloud Practitioner

When: after Phase 1, or skip it if you already have hands-on experience.

Covers: AWS services at a high level, security, cloud concepts, billing, support, and the shared responsibility model.

Series coverage: Phase 1 (Parts 1.1–1.5), plus the overviews in Phase 2.

Step 2: Architecture — AWS Certified Solutions Architect – Associate

When: after Phases 2–8.

Focus areas: secure architectures, resilient architectures, high-performing architectures, and cost-optimized architectures.

Series coverage:

This is the most widely recognized AWS certification, and a strong base for everything else.

Step 3: Data engineering — AWS Certified Data Engineer – Associate

When: after Phase 9.

Focus areas: data ingestion and transformation, data store management, data operations and support, and data security and governance.

Series coverage:

Step 4: Operations or development — pick one

Choose based on your role:

Step 5: Advanced — pick one after substantial hands-on experience

Optional: AI tracks


A study approach that builds real skill

1. Start with the official exam guide

Every exam has an exam guide listing domains, task statements, and in-scope services. Map each item to something you’ve built — if you can’t, that’s your study list.

2. Rebuild, don’t just reread

Go back to the labs in this series and change something:

Variation is how understanding sticks.

3. Use AWS’s own preparation resources

AWS Skill Builder offers exam prep courses, official practice question sets, and practice exams — many free. AWS microcredentials add hands-on, scenario-based assessments in live AWS environments for topics like serverless and agentic AI.

4. Practice exams — for diagnosis, not memorization

Take a practice exam early to find weak domains. For every question you miss — and every one you guessed — read the relevant documentation until you can explain why each wrong answer is wrong.

5. Read the question for the constraint

AWS exam questions usually hinge on one phrase: “most cost-effective,” “least operational overhead,” “highest availability,” or “minimum changes to the application.” Several answers can work; only one best fits the constraint.

Exam logistics


A realistic timeline

Learning alongside a full-time job, the series and certifications fit into about a year:

Faster or slower is fine. What matters is finishing the labs.


The capstone architecture, end to end

Here’s everything you built, as one system:

GitHub Actions
      |
      | OIDC (no stored AWS keys)
      v
AWS IAM Role
      |
      +------> Amazon ECR
      |             |
      |             v
      +------> Amazon ECS / Fargate
      |             |
      |             +------> Amazon RDS
      |             |
      |             +------> AWS Secrets Manager
      |
      +------> Amazon S3 Data Lake
                    |
                    +------> AWS Glue
                    +------> Amazon Athena
                    +------> Amazon Redshift
                    +------> AWS Lake Formation

Monitoring: Amazon CloudWatch + AWS CloudTrail
Security: IAM + KMS + Security Hub
Infrastructure: Terraform / CloudFormation
Networking: VPC + private subnets + endpoints
AI: Amazon Bedrock Knowledge Bases + Guardrails

Walking through it

1. Code to production (Phases 2 and 7). A developer merges a pull request. GitHub Actions tests and scans the code, then requests an OIDC token. AWS STS checks the role’s trust policy — this repository, this environment — and issues temporary credentials. No AWS keys exist anywhere in GitHub.

2. Build and gate (Phases 4 and 7). The pipeline builds a container image tagged with the commit SHA, pushes it to Amazon ECR with immutable tags, and blocks the deploy if the scan finds critical vulnerabilities.

3. Deploy safely (Phases 4 and 7). The pipeline registers a new task definition and updates the ECS service on Fargate. Tasks start in private subnets behind an Application Load Balancer. The circuit breaker rolls back failed starts; a smoke test — and an automatic rollback — catch versions that start but don’t work.

4. Data with no passwords in code (Phases 2 and 5). The application fetches database credentials from Secrets Manager at runtime, using its task role. RDS manages and rotates the password; the database lives in isolated subnets, encrypted with KMS, with automated backups.

5. The network (Phase 3). A two-AZ VPC with public subnets for the load balancer, private subnets for the app, and isolated subnets for data. Security groups chain load balancer → app → database. VPC endpoints keep AWS service traffic private and cheaper.

6. Everything as code (Phase 6). Terraform — or CloudFormation — defines the VPC, ECS, RDS, ECR, IAM, and alarms, with remote state in S3. terraform plan catches drift; terraform apply rebuilds the environment.

7. Observability and audit (Phases 2 and 8). CloudWatch dashboards show traffic, errors, latency, and saturation from the load balancer to the database. Composite alarms page once, with a runbook. CloudTrail records every API call; Security Hub and GuardDuty watch for threats and misconfigurations.

8. Analytics (Phase 9). DMS replicates the orders database into an S3 data lake without touching production query capacity. Glue turns raw data into clean, partitioned Parquet. Athena answers ad hoc questions; Redshift serves dashboards. Lake Formation controls who sees which columns and rows. Step Functions orchestrates it, and SNS alerts on failure.

9. AI on your own data (Phase 11). A Bedrock Knowledge Base indexes runbooks and policies from S3. The assistant answers with citations, while Guardrails mask PII, block off-limits topics, and reject ungrounded answers.

10. Designed for failure and cost (Phases 8 and 10). Multi-AZ everywhere, tested restores, documented RTO and RPO, idempotent event consumers, and a bill you can read like a design document.

Explain it in two minutes

If an interviewer asks, “Walk me through a system you’ve built on AWS,” this is your answer. Practice explaining it out loud — especially the why behind each choice: why OIDC instead of keys, why private subnets, why fetch secrets at runtime, why a smoke test in addition to health checks, why DMS instead of querying production.

That explanation is worth more than any badge.


What to do next


Key takeaways


Quick self-check

Test yourself one last time:

  1. Which certification is the best next step after Phases 2–8?
  2. You’re a data engineer. Which Associate certification maps most directly to Phase 9?
  3. What’s the best way to use practice exams?
  4. In the capstone, why does the app fetch its database password at runtime?

Answers

  1. AWS Certified Solutions Architect – Associate.
  2. AWS Certified Data Engineer – Associate.
  3. To diagnose weak domains — then study until you can explain why every wrong answer is wrong.
  4. So the password can rotate without redeploying — and never appears in code, images, or task definitions.

Thank you

This is the final article in AWS from Zero to Production. If you’ve made it here — especially if you did the labs — you’ve done something most people who start learning AWS never finish.

The full roadmap stays available as a reference. Bookmark it, revisit the labs, and come back whenever you need a refresher.

What did you build, and what’s next for you? I’d genuinely love to read it in the comments.


Share this article

LinkedIn post draft