Selkobase certification index

Cloud Engineer Certification Path: A Reviewed Route from a First Cloud Credential to Professional Design

Foundation, associate, automation, and professional steps across three major clouds

Moving into cloud engineering from IT support, system administration, or development takes more than one exam. This reviewed route shows what to take first, where the real choices are between AWS, Azure, and Google Cloud, and which dependencies are genuine provider requirements rather than suggested order.

Key takeaways

  1. 01

    Commit to one platform before adding another. Employers hire for the stack they run, and depth shows more than a spread of foundations.

  2. 02

    Azure is the one place with a hard gate: the Azure architect credential requires the Azure administrator credential, so pick that associate if Azure is a possibility.

  3. 03

    Foundation and associate credentials from AWS, Azure, and Google Cloud have no formal prerequisites, so every order in this route is a suggestion.

  4. 04

    Terraform and Kubernetes skills are portable and keep their value if you change cloud, which makes step three the safest investment in the route.

Who it is for

IT support staff, system administrators, and developers who want to build and run infrastructure on a public cloud and have not yet committed to one provider.

The goal

Operate and design workloads on one major cloud platform, with the automation and container skills most cloud engineering teams expect on day one.

Maybe not for you

People who already work on one platform every day and hold its associate credential can start at the automation step or go straight to the professional step.

Where to start

Where to start on the Cloud Engineer path depending on your experience

If cloud is new to you, begin at the first step. If you already administer systems or write software, go straight to the associate step for your platform, and if you run cloud workloads today, start with automation and containers or aim at the professional step.

Where are you starting?

Choose your background. We mark where to begin and fold away steps people with your experience usually skip.

The route

The route from a first cloud credential to professional-level design

The route starts with a platform foundation and moves to a role-based associate on the cloud you will work on. It then adds infrastructure as code and containers, which travel between clouds, and ends with a professional design credential. Each step lists the options for AWS, Azure, and Google Cloud.

  1. 1
    Step 1Pick oneNew to the field

    Learn cloud fundamentals

    Get fluent in how cloud works before you touch a console: core services, shared responsibility, pricing models, and basic security. Each option introduces one provider's platform.

    These are real alternatives for the same goal. Choose the one that fits.

    3 options

    How to choose

    Choose the provider your employer or target employers use. If you are undecided, pick the platform you can practice on for free, since the concepts carry over. The Google Cloud option is the most business-oriented and the least technical.

    You can skip this step if

    Suggested skip if you already use a public cloud at work and can explain its core services. This is an editorial suggestion, not a provider waiver.

    After this step you can

    • Explain what cloud services are and how responsibility is shared with the provider
    • Recognize a platform's core compute, storage, networking, and identity services
    • Describe at a conceptual level how cloud pricing and support models work
  2. 2
    Step 2Pick oneSome experience

    Operate one cloud platform

    Move from concepts to hands-on work on one platform: deploying, securing, monitoring, and fixing real resources. These associates are role-based, so pick the one that matches the work you want to do.

    These are real alternatives for the same goal. Choose the one that fits.

    4 options

    How to choose

    Pick the platform you will actually work on. On AWS, the operations credential suits administration and support work and the solutions architect credential suits design work. The Azure administrator credential is also the formal requirement for the Azure architect credential in the last step.

    You can skip this step if

    Suggested skip if you already hold an associate-level credential on the platform you will use.

    After this step you can

    • Deploy and manage compute, storage, and networking resources on one platform
    • Apply identity, access, and monitoring basics to keep workloads secure and observable
    • Troubleshoot common operational problems using the platform's own tooling
  3. 3
    Step 3Pick any that fit

    Add automation and containers

    Learn to describe infrastructure as code and to run containerized workloads. These skills are not tied to one cloud, so they keep their value if you change platform.

    Each option adds something different. Take the ones that match your work.

    3 options

    How to choose

    Terraform Associate is the usual first choice because infrastructure as code appears in most cloud engineering jobs. The Kubernetes and Cloud Native Associate is a conceptual introduction, while Certified Kubernetes Administrator is a hands-on, command-line exam for people who already run clusters.

    You can skip this step if

    Suggested skip if your team already codes its infrastructure and you work with containers daily. You can then go straight to the professional step.

    After this step you can

    • Describe repeatable infrastructure as code and manage its life cycle
    • Explain how containers and Kubernetes schedule and run workloads
    • Weigh managed against self-managed container platforms and their trade-offs
  4. 4
    Step 4Pick oneExperienced

    Design at professional level

    Design and justify complete cloud solutions that balance reliability, security, cost, and operations. These credentials assume substantial hands-on experience and are the main career signal in this route.

    These are real alternatives for the same goal. Choose the one that fits.

    3 options

    How to choose

    Stay on the platform you used in step two. The Azure architect credential formally requires the Azure administrator credential, so it is reachable only through that option. The AWS professional credential is moving to a new exam version, so confirm what is current with AWS before booking.

    After this step you can

    • Design multi-service solutions that meet reliability, security, and cost requirements
    • Evaluate migration, resilience, and governance options for larger organizations
    • Justify architectural trade-offs to technical and non-technical stakeholders

Effort and upkeep

What this path asks of you

Steps

Steps

4

Certifications on the reference route

Certifications on the reference route

4

Study effort

Study effort

210-390h

Exam fees

Exam fees

$620.50

Reference route estimates use the recommended option at each required step and come from the structured certification records. Prices and study time change and vary by region, so confirm with the provider. Last reviewed: Oct 22, 2026

Effort and upkeep

Expect the heaviest preparation at the associate and professional steps. The foundation step is mostly vocabulary, and credentials on the same platform overlap, so each step builds on the last. The professional step rewards time spent building real solutions far more than extra reading.

Keeping it current

Cloud credentials expire, and the rules differ: some providers offer a short renewal assessment, others require a full retake, and a higher-level credential can sometimes renew a lower one. Check your chosen provider's policy before you plan the sequence.

Where it leads

Where the Cloud Engineer path leads in the work you can do

Finishing the route positions you for hands-on cloud engineering and administration, and points toward architecture, DevOps, or cloud security. The role page shows the skills and related certifications connected to the work, and experience still decides how far credentials carry you.

Completing this route positions you for cloud engineer and cloud administrator roles, with a credible path toward architecture, DevOps, or cloud security. Experience still decides how far credentials carry you.

Explore the Cloud Engineer role

More paths

Other paths worth comparing

  • Start a role

    Cybersecurity Analyst pathway

    Start a defensive security career: from fundamentals to security operations analyst

    From an entry-level security foundation through a security operations associate to broader practitioner credentials and optional incident response specialization.

    • 4 steps
    • 13 certifications
    Entry pointsNew to the fieldSome experienceExperienced
    Cybersecurity AnalystView the path
  • Start a role

    Project Manager pathway

    Build a project management career with PMI, from first credential to portfolio level

    From an entry-level project management credential to the professional credential, then optional specializations and program or portfolio credentials.

    • 4 steps
    • 10 certifications
    Entry pointsNew to the fieldSome experienceExperienced
    Project ManagerView the path

Reviewed and editorial. Paths suggest an order; they do not replace the provider's own requirements.

Pick the path that matches the role you are aiming for

Open the path closest to your goal, check where your current experience places you, and follow the links to the certifications behind each step. If no path fits yet, search certifications directly and compare level, provider, and assessment style.