DevOps & Cloud Topic
Cloud Basics: Understand AWS, Azure and Google Cloud
Cloud services let you use computing resources through a provider. You can rent a server, store files or run a database without owning the hardware.
The provider manages some work. You still choose access, data rules, app settings and budgets. The exact split depends on the service.
Five parts to learn first
- Compute: Where your code runs.
- Storage: Where files and data live.
- Network: How systems connect.
- Identity: Who or what can do something.
- Billing: What usage costs.
Three common service models
IaaS: You rent infrastructure such as virtual machines. You usually manage the guest operating system and app.
PaaS: You deploy an app onto a managed platform. You manage less of the operating system, but still manage code and settings.
SaaS: You use a finished application, such as a hosted work tool. You still manage your account, sharing and data choices.
These are broad groups. A real service may not fit one neat box.
Common service names
- Virtual machines: Amazon EC2, Azure Virtual Machines and Google Compute Engine.
- Object storage: Amazon S3, Azure Blob Storage and Google Cloud Storage.
- Managed Kubernetes: Amazon EKS, Azure Kubernetes Service and Google Kubernetes Engine.
- Managed relational databases: Amazon RDS, Azure SQL Database and Google Cloud SQL are examples, but their engines and features differ.
Use this list as a map, not as a promise that the services are identical. Read the product’s own limits before choosing it.
Regions and zones
A region is a geographic area where a provider runs services. A zone is a separate location within a region, with details that vary by provider.
Choose a region based on your users, service availability, data needs and cost. Running two copies in one zone is not the same as spreading them across zones.
Compute: choose the amount of control you need
A virtual machine gives you control but also work such as patching. A managed container service runs your container while handling more infrastructure. A function service runs short pieces of code in response to events.
On AWS, EC2, ECS and Lambda serve different needs. ECS is not the same as EKS. You do not need Kubernetes just because your app uses a container.
Storage is not all the same
Object storage holds named objects, such as photos or backups. Block storage acts more like a disk for a server. File storage offers shared folders. A database manages structured access and queries.
Ask how the app reads data, how often it changes and how you will restore it. A replica helps availability, but it is not a replacement for a tested backup.
Identity: give a small amount of access
A person signs in. A workload can use a service identity or role. Give only the actions and resources needed for the job.
For example, a job that reads one backup should not be allowed to delete every bucket. Do not put account keys in an image or a public repository.
Network: trace one request
A browser asks DNS for an address. It connects to a public endpoint. A load balancer can send the request to an app. The app may then read a private database.
Each step needs the right route and access rules. An open firewall alone does not create a working route.
Infrastructure tools
Terraform, Pulumi and AWS CDK describe infrastructure in files or code. They help review and repeat changes. They do not remove the need to understand the resources or pay for them.
Start with the local infrastructure-as-code lab. It does not create cloud resources.
Practice without a cloud bill
Draw a small app with a browser, public endpoint, app and database. Mark which parts should accept internet traffic. Name one failure at each step.
Then estimate what may cost money: compute time, storage, requests, logs, network traffic and backups. In a real account, check the provider’s current price pages rather than relying on a tutorial’s old prices.
Official references and further reading
Reviewed on 25 October 2026. Tools change, so check the official documentation for the version you use.
Comments (0)
No comments yet. Be the first to comment!