What Is AWS? Core Services, Pricing & Regions (2026)
Last verified: June 17, 2026 · Format: Breakdown
AWS is Amazon Web Services, the cloud platform from Amazon that lets you rent computing power, storage, databases, and more than 200 other services over the internet, paying only for what you use. If you have been asking what AWS is in practical terms, picture a giant catalog of building blocks you can switch on in minutes and switch off when you are done, with no servers to buy or data centers to run. Launched in 2006 and now serving customers in 190 countries, it is the largest and longest-running of the major public clouds, and the others built their language on the same foundations.
This breakdown is plain and practical. We start with what AWS actually is, walk through its core service categories (compute, storage, networking, database, and identity), explain how its pay-as-you-go pricing and Free Tier work, look at its global infrastructure of Regions and Availability Zones, and close with who AWS is for. Service and pricing details below are drawn from AWS documentation and were checked on June 17, 2026; always confirm current figures on the AWS site before you commit.
What AWS Is
Amazon Web Services describes itself as a reliable, scalable, and low-cost cloud platform. In plain terms, AWS is a single account through which you can provision real infrastructure, compute servers, object storage, managed databases, networking, analytics, and machine learning, on demand and over the internet, then pay for it by the hour, the request, or the gigabyte rather than buying hardware up front.
The headline number is the breadth: AWS offers more than 200 fully featured services, from raw virtual servers to managed databases, content delivery, analytics, and machine-learning tools. You do not need most of them. The point of the catalog is that whatever you are building, the primitive you need is already there, running in Amazon's data centers, ready to be turned on with a few clicks or one API call.
Two ideas make AWS what it is. First, it is genuinely on-demand: you self-serve capacity, scale it up for a spike and back down afterward, and the underlying hardware is Amazon's problem, not yours. Second, it is metered: usage is measured and billed, so cost tracks consumption. If you want the standards-body framing behind those ideas, our what is cloud computing guide covers the model AWS is built on, and the broader Cloud Tools hub places AWS alongside the other providers.
AWS Core Service Categories
With 200+ services, AWS can feel overwhelming. The good news is that a handful of categories carry most workloads, and once you recognize the flagship service in each, the rest of the catalog is variations on those themes. Here are the core categories and the services you will meet first.
Compute
Compute is the engine room: the servers that run your code. Amazon EC2 (Elastic Compute Cloud) is the flagship, giving you resizable virtual machines you control down to the operating system. For event-driven work, AWS Lambda runs your code without you managing any servers at all (you pay per request and per millisecond of run time). Between them, EC2 and Lambda cover most of the spectrum from full-control virtual machines to fully managed serverless functions.
Storage
Amazon S3 (Simple Storage Service) is AWS's object storage and one of its best-known services, used for everything from backups to static websites to data lakes. Its pricing is tiered: you choose a storage class based on how often you access the data, with infrequently accessed and archival tiers costing less per gigabyte. S3 is the default place to put files, and its durability and tiering are a large part of why teams standardize on it.
Networking
Amazon VPC (Virtual Private Cloud) is your private, isolated section of the AWS network, where you define subnets, routing, and firewall rules and decide what is reachable from the internet and what stays internal. Every serious AWS deployment lives inside a VPC; it is how you draw the boundary around your resources and control traffic in and out.
Database
AWS offers managed databases so you run queries instead of patching servers. Widely used options include Amazon RDS for managed relational databases (engines such as PostgreSQL and MySQL) and Amazon DynamoDB for a fully managed NoSQL key-value store built for scale. Both are canonical AWS services; the AWS products catalog lists the full database lineup and current details.
Identity
Access control is where security begins. AWS IAM (Identity and Access Management) governs who can do what across your account, using users, roles, and fine-grained policies. For applications that need to sign in and manage end users, Amazon Cognito provides user directories, sign-up and sign-in, and federated identity. Getting identity right early is the single most valuable thing you can do for an AWS account's security.
| Category | Flagship service | What it does | Typical use |
|---|---|---|---|
| Compute | Amazon EC2 | Resizable virtual servers you manage | Apps, web servers, custom workloads |
| Serverless | AWS Lambda | Runs code on events, no servers to manage | Event processing, lightweight APIs |
| Storage | Amazon S3 | Object storage, tiered by access frequency | Backups, media, data lakes, websites |
| Networking | Amazon VPC | Isolated private network you define | Boundaries, subnets, traffic control |
| Database | Amazon RDS / DynamoDB | Managed relational and NoSQL databases | App data, transactions, scale |
| Identity | AWS IAM / Cognito | Access control and end-user identity | Permissions, sign-in, least privilege |
The pattern across the catalog is consistent: AWS gives you a low-level, high-control option and a higher-level, managed option in most categories, and lets you mix them. Start with the flagship in each category and reach for the specialized services only when a real need appears.
Comparing the big three? AWS, Microsoft Azure, and Google Cloud map similar primitives onto different names and pricing. Browse the Microsoft Azure and Google Cloud pillars to see how the same categories take shape across vendors.
AWS Pricing and the Free Tier
Any honest answer to what is AWS has to cover cost, because AWS pricing rests on one core idea: pay-as-you-go. There are no long-term contracts or termination fees on the standard model; you pay for the compute, storage, and requests you actually consume and stop paying when you stop using them. That flexibility is the appeal, and the responsibility, of cloud billing.
Several pricing patterns sit on top of pay-as-you-go, and knowing them is how you keep an AWS bill predictable:
- Pay-as-you-go (on-demand): the default. Pay for what you use, by the hour, second, request, or gigabyte, with nothing to commit to in advance.
- Savings Plans: commit to a consistent amount of usage over a 1-year or 3-year term in exchange for lower rates. Savings Plans cover compute and machine-learning usage and suit steady, predictable workloads.
- Tiered pricing: some services get cheaper per unit as you scale. With S3 and data-transfer-out, the per-gigabyte rate drops at higher volumes, and inbound data transfer into AWS is generally free.
- Free Tier: AWS offers a way to get started for free, so you can explore many services without immediate cost while you learn.
The Free Tier is the natural on-ramp. It lets you stand up real services, an EC2 instance, an S3 bucket, a small database, and learn by doing before you spend anything meaningful. The catch is that free allowances have limits, and it is easy to drift past them, so set a budget and watch usage from day one. Because pricing and free allowances change often, treat any specific figure as a starting point and confirm the current numbers on the AWS pricing page before you plan around it.
AWS Global Infrastructure
A big part of AWS's appeal comes down to its physical footprint, which is one reason it scales the way it does. AWS builds its cloud in two layers: Regions, which are separate geographic areas, and Availability Zones, which are clusters of isolated data centers within a Region. Placing your workload in a Region close to your users lowers latency, and spreading it across multiple Availability Zones in that Region is how you build for resilience, so a problem in one zone does not take your application down.
As of June 17, 2026, AWS reports that its cloud spans 123 Availability Zones within 39 Geographic Regions, with further expansion announced, including new Regions in Saudi Arabia and Chile and additional Availability Zones. These counts are vendor-reported and change as AWS builds out capacity, so check the current numbers on the AWS Global Infrastructure page before relying on them. Where your data physically lives also carries legal and compliance weight, which is why Region choice is a deliberate decision, not a default.
Region choice is not just about latency: data-residency and compliance rules can dictate which Region you must use. Choosing a Region near your users is good for speed, but if regulations require your data to stay in a particular jurisdiction, that requirement wins. Decide Region placement with both performance and compliance in mind.
Who AWS Is For
We have covered what AWS is and how it is structured; the last question is who it suits. The short answer is almost anyone who builds or runs software, from a solo developer on the Free Tier to global enterprises. AWS powers well-known names such as Netflix, Toyota, BMW, United Airlines, and Siemens Mobility, alongside countless startups and public-sector bodies across 190 countries. The right entry point shifts by need.
Developers and students who want a real server, database, or storage bucket without buying hardware. The Free Tier and pay-as-you-go pricing let you start small, and managed services like Lambda and RDS remove most of the operations work.
Best fit: Free Tier, then on-demandTeams that need to move fast and scale unpredictably. AWS's elasticity means you provision for today and grow without re-architecting, while metered billing keeps early-stage costs proportional to actual usage. Netflix is the canonical example of building at scale on AWS.
Best fit: On-demand, then Savings PlansLarge organizations modernizing legacy systems while meeting governance and reliability needs. Multi-Region, multi-Availability-Zone designs and Savings Plans suit predictable, mission-critical workloads. Toyota, BMW, and United Airlines run significant operations on AWS.
Best fit: Multi-AZ + Savings PlansOrganizations with strict compliance, data-residency, or sovereignty rules. AWS's Region choice and identity controls let them meet requirements about where data lives and who can access it, though the configuration responsibility stays with them.
Best fit: Region-aware, IAM-firstHonest Trade-offs
No honest breakdown is complete without the trade-offs. AWS is a sensible default for most new workloads, and the points below are not reasons to avoid it. They are reasons to adopt it with clear eyes.
Pay-as-you-go is a feature until idle instances, over-provisioned resources, or runaway usage quietly add up. AWS removes upfront capital cost but replaces it with an ongoing operating cost that needs active monitoring. Set budgets and watch usage from the first day.
AWS secures the underlying platform, but how you configure IAM, networking, and storage is on you. The shared responsibility line moves by service, and a public S3 bucket or an over-permissive IAM policy is a far more common cause of trouble than any failure of the AWS platform itself.
200+ services is genuinely capable and, at first, overwhelming. The cost of that breadth is complexity: choosing among overlapping services, understanding their pricing, and wiring them together takes time. Start with the flagships and resist adopting services before you have a clear need.
Managed and serverless services are convenient but can tie you to AWS's APIs and pricing. Moving later is rarely a simple lift-and-shift. Weigh the convenience of deeply managed services against how easily you could change course, and confirm current terms with AWS before committing.
Frequently Asked Questions
Go Deeper
Resources from across Tech Jacks Solutions
Cloud Tools Hub
Browse cloud foundations and provider guides, by topic and vendor
Shared Responsibility Model
The single most important diagram for AWS security, demystified
FREEGovernance Charter
Set the rules before workloads scale across teams and accounts
EU AI Act Overview
How regulation frames data, residency, and cloud-hosted systems