Skip to main content
AIDevOps
  • Learn
  • Learning Paths
  • Practice
  • Open Source
  • Books
  • Engineering

    AI DevOpsThe full map of building and operating AI servicesLLMOpsLLM deployment · evaluation · observabilityHands-on ProjectsBuild AI Agent projects

    Knowledge

    DocsTechnical documentationBlogEngineering articlesPloggerDevelopment log feed

    Validate

    Certification3-level skills certification · coming soon
AI Models
LlamaTutorial|MistralTutorial|GemmaTutorial|DeepSeekTutorial|QwenTutorial
☁️ Cloud
Cloud Intro & RoadmapAWSGCPAzureNCPCloudflare
🤖 AI Applied Development
Applied AI Intro & RoadmapHugging FaceLangChainLlamaIndexLLMOps|LangGraphMCPMulti-AgentAgent Evaluation
🧠 AI Core
AI Intro & RoadmapML FundamentalsLLM Fundamentals|Python AIC++|PyTorchTensorFlowJAX
🧠 AI Agent Development
Finance AI AgentLLM API ServerStock Investing AgentAIOps AI AgentEducation AI AgentCoding AI Agent
🌱 Spring Cloud
Spring Intro & RoadmapSpring Cloud GatewaySpring BootJava|Spring AISpring SecuritySpring BatchSpring JPA
🐳 DevOps
DevOps Intro & RoadmapLinuxDockerCI/CD|Kubernetes BasicsK8s AdvancedPrometheusGrafana
🧱 Infrastructure
Infrastructure Intro & RoadmapNginxRedis
🎨 Frontend
Frontend Intro & RoadmapJavaScriptTypeScript|ReactNext.js|VueNuxt|Electron
📱 Mobile
Mobile Intro & RoadmapKotlinAndroidFlutter
⚙️ Backend
Backend Intro & RoadmapPython BasicsFastAPIDjangoFlask|CGoGinNode.js
💾 Database
DB Intro & RoadmapCore SQLOracleMySQLPostgreSQL|MongoDBVector DB
🧪 Testing
k6JMeternGrinder
AIDevOps

Engineering AI. From Code to Production.
An engineering learning platform for building and operating AI and AI Agents

Learn

  • All Guides
  • Learning Paths
  • AI Tutorial
  • Practice
  • Books

Resources

  • AI DevOps
  • LLMOps
  • Hands-on Projects
  • Docs
  • Blog
  • Plogger
  • Open Source
  • Certification (coming soon)

Start Here

  • AI Core Roadmap
  • AI Applied Development Roadmap
  • Spring Cloud Roadmap
  • DevOps Roadmap
  • Infrastructure Roadmap

 

  • Cloud Roadmap
  • Frontend Roadmap
  • Mobile Roadmap
  • Backend Roadmap
  • Database Roadmap
© 2026 AIDevOps. All rights reserved.
Terms of ServicePrivacy PolicySitemaptestforge.kr
  1. Home
  2. Learn
  3. Cloud
  4. Cloud Intro & Roadmap
The first guide for newcomers to the cloud

🧭 Cloud Intro & Roadmap Complete Guide

Visitors

A starting point for anyone new to the cloud. It covers what the cloud is and why it is used, how IaaS, PaaS, SaaS, and serverless differ, a map of the core services every cloud has in common, a comparison of AWS, GCP, Azure, NCP, and Cloudflare, the basics of cost and security, and a step-by-step learning roadmap.

  • Beginner
  • Updated Oct 1, 2026
  • ~8 min read
  • 12 sections
  • 1 code examples

Learning Paths that include this guide

This guide is one step in the paths below. Study it together with the steps before and after.

  • Cloud Native Engineer →
The big picture of cloud conceptsUnderstand the service modelsCompare cloud providersCost and security basicsPreparing for cloud certifications

Related frameworks & environments

☁️AWS→☁️GCP→☁️Azure→☁️NCP→⚡Cloudflare→

Contents

0 / 15
  1. How to use this guide
  2. Architecture diagrams
  3. What the cloud is
  4. Service models
  5. Map of the common core services
  6. Comparing providers
  7. Cloud networking basics
  8. Your first deployment
  9. Cost and security basics
  10. Before you start
  11. Step-by-step roadmap
  12. 8-week study plan
  13. Common mistakes
  14. Key terms
  15. Frequently asked questions
Contents 15 sections
  1. How to use this guide
  2. Architecture diagrams
  3. What the cloud is
  4. Service models
  5. Map of the common core services
  6. Comparing providers
  7. Cloud networking basics
  8. Your first deployment
  9. Cost and security basics
  10. Before you start
  11. Step-by-step roadmap
  12. 8-week study plan
  13. Common mistakes
  14. Key terms
  15. Frequently asked questions

How to use this guide

How to read it

Understanding Cloud Intro & Roadmap as a real-world workflow

A starting point for anyone new to the cloud. It covers what the cloud is and why it is used, how IaaS, PaaS, SaaS, and serverless differ, a map of the core services every cloud has in common, a comparison of AWS, GCP, Azure, NCP, and Cloudflare, the basics of cost and security, and a step-by-step learning roadmap. Rather than listing concepts, this guide is organized so you can follow the content in the order you have to make decisions on a real project.

Key perspective

Infrastructure / operations

Rather than memorizing install commands, understand the order in which traffic, runtime, observability, and incident response connect.

The big picture of cloud conceptsUnderstand the service modelsCompare cloud providersCost and security basicsPreparing for cloud certifications

Architecture diagrams

To make what you read stick, it helps to capture the flow as a picture first. The two diagrams below are reference maps you can keep coming back to while learning Cloud Intro & Roadmap.

Learning flow

Rendering diagram…

Architecture view

Rendering diagram…

What the cloud is: a data center you rent

When you first open Cloud Intro & Roadmap, the big picture matters more than individual commands. This section starts with the problems the concepts ahead were created to solve.

It used to take weeks to run a service: buying servers, installing them in a data center, and connecting the network. If traffic was higher than expected there were not enough servers, and if it was lower, expensive hardware sat idle.

The cloud is a way of renting all of that over the internet, as much as you need for as long as you need. With a few clicks (or a few lines of code) you create a server in minutes, and you delete it to stop paying when you no longer need it.
AspectOn-premises (your own servers)Cloud
Upfront costBuying servers and equipment (a large upfront investment)None — pay for what you use
Lead timeWeeks to monthsMinutes
ScalingNeed to buy more hardwareScale up and down immediately
Management responsibilityEverything from the hardware upThe provider handles hardware and physical security
Global deploymentSecure overseas data centers yourselfJust pick a region

Service models: how much do you manage yourself

Service models: how much do you manage yourself is a point where the options diverge. Using the table to compare what each approach is for and how it differs in operation makes later decisions much easier.

Cloud services are divided by "how much you have to manage". The management burden shrinks as you go down the list, but so does fine-grained control.
ModelYou manageThe provider managesExamples
IaaSOS, runtime, app, dataHardware, network, virtualizationAWS EC2, GCP Compute Engine, NCP Server
CaaS (containers)Container images, configurationThe cluster management planeEKS, GKE, AKS, Cloud Run
PaaSApp code, dataOS, runtime, scalingElastic Beanstalk, App Engine, Azure App Service
Serverless (FaaS)Function codeServers, scaling, and availability entirelyAWS Lambda, Cloudflare Workers
SaaSJust use itEverythingGmail, Slack, Notion

Map of the common core services: different names, same concepts

Map of the common core services: different names, same concepts is a point where the options diverge. Using the table to compare what each approach is for and how it differs in operation makes later decisions much easier.

Service names differ from provider to provider, but the core concepts are nearly identical. Learn one cloud properly and you can adapt to another quickly, at roughly the level of "swapping the names".
CategoryConceptAWSGCPAzure
ComputeVirtual serversEC2Compute EngineVirtual Machines
ContainersManaged KubernetesEKSGKEAKS
ServerlessFunction executionLambdaCloud Functions / Cloud RunAzure Functions
StorageObject storageS3Cloud StorageBlob Storage
DatabaseManaged relational DBRDS / AuroraCloud SQLAzure SQL / Database for PostgreSQL
NetworkingVirtual private networkVPCVPCVNet
SecurityAccess managementIAMIAMEntra ID + RBAC
ObservabilityMonitoring and logsCloudWatchCloud Monitoring / LoggingAzure Monitor

Comparing cloud providers

Comparing cloud providers is a point where the options diverge. Using the table to compare what each approach is for and how it differs in operation makes later decisions much easier.

AWS is the recommended first cloud. It has the most learning material and hiring demand, and the concepts you learn there carry straight over to other clouds. This site (aidevops.us) runs on Cloudflare.
ProviderStrengthsTypically chosen whenGuide
AWSThe largest market share, the most services, vast documentationA first cloud to learn, most companiesAWS
GCPData and AI (BigQuery, Vertex AI), Kubernetes (GKE)Services centered on data analytics and AIGCP
AzureIntegration with the Microsoft ecosystem (Entra ID, Office), OpenAI modelsMicrosoft-based companies, enterpriseAzure
NCP (Naver Cloud)Korean regions, Korean public-sector certification (CSAP), Korean-language supportWorkloads under Korean regulation, such as public sector and financeNCP
CloudflareGlobal edge network, CDN, security, WorkersStatic sites, edge computing, a security front endCloudflare

Cloud networking basics: VPC and subnets

Cloud networking basics: VPC and subnets is a point where the options diverge. Using the table to compare what each approach is for and how it differs in operation makes later decisions much easier.

The first wall you hit in the cloud is networking. Most cases of "I created a server but cannot connect" are network configuration problems. A VPC is your own isolated network inside the cloud, and you divide it into subnets by purpose.
ComponentRoleTypical placement
Public subnetCan talk to the internet directlyLoad balancers, Bastion (jump server)
Private subnetNot reachable directly from outsideApp servers, DB
Internet gatewayThe path between the VPC ↔ the internetAttached to public subnets
NAT gatewayThe way out for private servers (inbound stays blocked)For installing packages and calling external APIs
Security groupA per-instance firewall (allow rules)The DB allows 3306/5432 only from the app servers

Tip

Always put the DB in a private subnet. Leaving a DB port open to the internet (0.0.0.0/0) is the most common and most damaging cause of cloud security incidents.

Your first deployment: publish a static site from the CLI

Here you look at Your first deployment: publish a static site from the CLI alongside real code. Rather than copying the example as-is, read it with an eye on the inputs, the outputs, and the parts most likely to change.

The cloud can be driven from the web console, but in real work the default is the CLI and code. Below is an example of publishing a static site to S3 with the AWS CLI. Do the same task in the console once and then repeat it with the CLI to feel the difference.
deploy-static.shBASH
# Prerequisite: set up credentials with aws configure (never use root account keys)
BUCKET=my-first-site-20260924

# 1. Create the bucket (in the region you use)
aws s3 mb s3://$BUCKET --region us-east-1

# 2. Upload the build output (syncs only changed files)
aws s3 sync ./dist s3://$BUCKET --delete

# 3. Configure static website hosting
aws s3 website s3://$BUCKET --index-document index.html --error-document 404.html

# Clean up when the lab is done — make a habit of deleting unused resources right away!
# aws s3 rb s3://$BUCKET --force

Tip

In a real service, rather than making S3 public directly, the recommended setup puts a CDN (CloudFront, Cloudflare) in front and keeps the bucket private.

Cost and security basics: what to take care of from day one

Cost and security basics: what to take care of from day one is a point where the options diverge. Using the table to compare what each approach is for and how it differs in operation makes later decisions much easier.

The two scariest things for cloud newcomers are unexpected bills and security incidents. The cloud follows a "shared responsibility model". The provider is responsible for the data centers and hardware, and the configuration, data, and permissions you put on top are your responsibility.
ItemWhat to doWhy
Root accountEnable MFA, then do not use it for everyday workA stolen root = the whole account stolen
IAMLeast-privilege accounts per person and serviceLimits the blast radius of a leak
Access keysNever in code or on GitHub; temporary credentials where possibleLeaked keys are used to spin up mining servers → a huge bill
Budget alertsSet a monthly budget and usage alertsCatch billing accidents early
Resource cleanupDelete instances, NAT, and load balancers after a labThey bill by the hour just for existing
TagsTag project, owner, and environmentTrack cost and identify what to clean up

Tip

NAT gateways, load balancers, and managed DBs are billed by the hour even with no traffic. Check what the free tier covers, and always delete them when the lab is done.

Before you start

Before you start is a point where the options diverge. Using the table to compare what each approach is for and how it differs in operation makes later decisions much easier.

In the end, the cloud is "Linux servers and networks in someone else's data center". The firmer your Linux and networking fundamentals, the faster you learn the cloud.
AreaWhatHow much
LinuxSSH access, installing packages, managing servicesLinux basics
NetworkingIP ranges (CIDR), ports, DNS, HTTP/HTTPSUnderstand CIDR notation (10.0.0.0/16 and so on)
DockerBuilding and running imagesDocker basics
Payment methodA card for signing up for a cloud accountFree tier + budget alerts are a must
One app to deployA static site or a simple APISomething to practice on

Step-by-step roadmap: from the first server to cloud architecture

Step-by-step roadmap: from the first server to cloud architecture is a point where the options diverge. Using the table to compare what each approach is for and how it differs in operation makes later decisions much easier.

StepGoalWhat to learnGuidesDone check
0. BasicsServers and networksLinux, SSH, CIDR, DNS, HTTPLinuxSSH into and configure a remote server
1. Account and securityA safe startRoot MFA, IAM users and roles, budget alertsAWSWork only as an IAM user
2. Compute & storageDeploy a first serviceVirtual servers, object storage, security groupsAWSA web app on a server + static files on S3
3. NetworkingVPC designPublic/private subnets, gateways, load balancersAWSBuild a 2-tier VPC architecture
4. Managed servicesReduce the operations burdenManaged DBs, container services, serverlessGCP, AzureA managed DB + a container deployment
5. Edge & CDNFast around the worldCDN, DNS, WAF, edge functionsCloudflareCustom domain + CDN + HTTPS
6. IaCInfrastructure as codeDefine the VPC, servers, and DB with TerraformCI/CDReproduce the whole environment with terraform apply
7. Regional requirements & multi-cloudRegulation and optionsRegional cloud certifications, comparing providersNCPReproduce the same setup on a second cloud

Tip

Cloud certifications (AWS SAA and others) are good for organizing the concepts systematically. A certificate alone is not enough, though, so always keep the hands-on deliverables from the steps above as well.

8-week study plan: 1-2 hours a day

8-week study plan: 1-2 hours a day is a point where the options diverge. Using the table to compare what each approach is for and how it differs in operation makes later decisions much easier.

The "all resources deleted" step in the last week is an important exercise too. If you built everything with Terraform, a single terraform destroy cleans it all up — the moment you feel the value of IaC.
WeekTopicDeliverable
Week 1Account security + IAM + budget alertsA safely configured cloud account
Week 2Virtual servers + security groupsA web server you can SSH into
Week 3Object storage + CDNA static site deployment + custom domain
Week 4VPC designA 2-tier public/private subnet layout
Week 5Managed DB + load balancerA 3-tier architecture: 2 app servers + DB
Week 6Container services / serverlessA container app deployment + a serverless function
Week 7TerraformWeeks 1-6 reproduced as code
Week 8Monitoring + cost analysis + cleanupDashboard + cost report + all resources deleted

Common mistakes of cloud beginners

Common mistakes of cloud beginners is a point where the options diverge. Using the table to compare what each approach is for and how it differs in operation makes later decisions much easier.

Most cloud incidents come not from technically hard problems but from configuration mistakes. The habit of making a checklist and going through it every time is the most powerful security tool.
MistakeProblemDo this instead
Doing everyday work as the root accountTotal damage if the account is hijackedMFA + IAM users/roles
Committing access keys to GitHubHarvested automatically within minutes and abusedEnvironment variables or a secret manager, revoke the key immediately
Opening a security group to 0.0.0.0/0Exposed to brute-force attacksAllow only the ports and IPs needed
Leaving lab resources runningA huge bill at the end of the monthDelete right after the lab, budget alerts
Building only by clicking in the consoleCannot be reproduced, reviewed, or recoveredRecord it with the CLI and IaC
Putting everything in a single availability zoneEverything goes down if the data center failsA multi-AZ setup
Working without checking the regionResources cannot be found, or latency goes upCheck the region before you start (e.g. us-east-1)

Key terms

Key terms is a point where the options diverge. Using the table to compare what each approach is for and how it differs in operation makes later decisions much easier.

TermOne-line explanation
RegionThe geographic area where cloud data centers are located (e.g. N. Virginia)
Availability zone (AZ)A group of physically separate data centers within one region
VPCA logically isolated private network you create inside the cloud
CIDRNotation for IP address ranges (10.0.0.0/16 = about 65,000 addresses)
IAMAccess management that defines who can do what to which resources
Security groupVirtual firewall rules applied to instances
Object storageA service that stores files without limit as key-object pairs (S3 and others)
ServerlessAn execution model billed per code execution, with no servers to manage
Shared responsibility modelThe principle that the provider is responsible for the cloud itself and the user for the configuration and data in it
Free tierA benefit that gives new sign-ups a certain period or amount of usage for free

Tip

The next step is the AWS guide. Follow it step by step, starting with account security settings.

Cloud Intro & Roadmap: frequently asked questions

Should I learn AWS, Azure, or GCP first?

Learning the cloud used by the company you want to join, or by your current organization, is best. If nothing is decided, many people start with AWS because it has the most users and learning material. Virtual servers, networking, storage, and access management are similar across clouds under different names, so learning one makes the others easy to pick up.

How do IaaS, PaaS, and SaaS differ?

With IaaS you rent infrastructure such as virtual servers and networks and manage everything from the operating system up. With PaaS you upload code and the platform manages the runtime. With SaaS you use finished software as it is. The higher you go, the less there is to manage and the less fine control you have.

How do I keep the cloud bill from being higher than expected?

Set a budget alert as soon as you create the account, and delete resources when a lab is finished. Common causes are servers left running and forgotten, detached disks and static IPs, outbound data transfer, and managed databases. Tagging resources makes it easy to trace where costs come from.

Next guide →AWS