AWS
Also known as: Amazon Web Services, Amazon Cloud
AWS is Amazon's cloud computing platform.
Instead of buying and maintaining your own servers, you rent computing power, storage, and services from Amazon's global data centers -- paying only for what you use.
AWS, explained at three levels
At home
Imagine needing a server to run your website, but instead of buying a physical computer, you rent one from Amazon and pay by the hour. That's AWS -- a massive collection of computing resources you can access over the internet without owning any hardware.
At work
AWS lets businesses run their software, store their data, and serve their customers without managing physical servers. A startup can launch on AWS and scale from one user to millions without buying a single piece of hardware.
At home
AWS offers over 200 services spanning compute (EC2), storage (S3), databases (RDS), machine learning (SageMaker), and more. You pick only what you need, configure it through a web console or code, and AWS handles the physical infrastructure, power, cooling, and redundancy.
At work
Teams use AWS to build architectures that auto-scale under load, replicate data across regions for disaster recovery, and replace upfront capital expenditure with predictable operating costs. IAM roles, VPCs, and Security Groups control access and network isolation.
At home
At the infrastructure level, AWS runs on a global network of regions and availability zones -- physically separate data centers that share low-latency fiber links. Services like Lambda and Fargate abstract away even the virtual machine, letting you deploy code without provisioning anything.
At work
Enterprise AWS usage involves multi-account architectures via AWS Organizations, centralized logging with CloudTrail and CloudWatch, infrastructure-as-code with CloudFormation or CDK, and cost governance via Reserved Instances or Savings Plans. Well-Architected Framework pillars (reliability, security, cost, performance, sustainability) guide design reviews.
Real-world examples
At home
Sophie uses AWS S3 to host her photography portfolio as a static website. She pays less than a dollar a month because S3 charges per gigabyte stored and per request -- and her traffic is light.
At work
Thomas's team deploys their SaaS application on AWS using EC2 auto-scaling groups behind an Application Load Balancer, with RDS PostgreSQL for the database and CloudFront as a CDN. The whole infrastructure is defined in Terraform so any developer can spin up a staging environment in minutes.
Common confusions
- AWS is just for big companies — The pay-as-you-go model and free tier make AWS accessible to individual developers and startups. Many solo projects run for pennies a month.
- AWS and Amazon.com are the same thing — AWS is a separate business unit. Amazon.com (the store) runs on AWS, but AWS also powers Netflix, Airbnb, NASA, and thousands of other organizations.
- Moving to AWS automatically makes your system reliable — AWS provides the building blocks for reliability, but you must architect for it -- using multiple availability zones, health checks, and proper backup strategies.
For analysts
Business analysts use AWS QuickSight for dashboards, Glue for data pipelines, and Athena to query S3 data with SQL -- no server provisioning required.
History & origin
Amazon launched AWS in 2006 with just a handful of services: S3 for storage and EC2 for virtual servers. It was originally built to support Amazon's own e-commerce infrastructure. When engineers realized other companies would pay for the same capacity, AWS became a separate business. Today it controls roughly a third of the global cloud market and generates more profit than Amazon's retail operations.