AWS: Overview, Purpose and Use Cases
By Oleksandr Andrushchenko — Published on
Amazon Web Services (AWS) is a cloud computing platform that provides compute, storage, networking, and database infrastructure over the internet. Instead of managing physical servers, companies consume infrastructure on-demand using a pay-as-you-go model.
Cloud computing replaces the traditional on-premises model, where companies had to buy, install, and maintain physical servers in their own data centers. AWS shifts this responsibility to a cloud provider, allowing developers to focus on building applications instead of managing hardware.
| Aspect | On-Premises | Cloud (AWS) |
|---|---|---|
| Infrastructure ownership | Company owns hardware | AWS owns hardware |
| Cost model | Large upfront capital cost (CapEx) | Usage-based operational cost (OpEx) |
| Scaling | Manual provisioning (slow) | Automatic or near-instant scaling |
| Deployment speed | Weeks to months | Minutes |
| Maintenance | Fully managed internally | Shared responsibility model |
| Global reach | Limited and expensive | Multi-region deployment built-in |
- Key shift: from owning infrastructure → consuming infrastructure
- Key benefit: faster experimentation and delivery
- Key impact: infrastructure becomes elastic and programmable
At its core, AWS enables developers to provision infrastructure instantly, scale dynamically, and only pay for what they use — removing the traditional constraints of hardware management.
Advantages of Cloud Computing
Cloud computing provides flexibility, scalability, and speed of innovation. Instead of managing infrastructure upfront, companies consume compute resources dynamically.
| Advantage | Explanation | Impact on Engineering | AWS Example |
|---|---|---|---|
| Pay as you go | Only pay for actual usage | Lower upfront cost | EC2, Lambda billing |
| Economies of scale | Shared infrastructure reduces cost | Cheaper compute at scale | S3 storage pricing |
| No capacity guessing | Scale up/down dynamically | No over-provisioning | Auto Scaling Groups |
| Speed & agility | Provision resources in minutes | Faster development cycles | Lambda, CloudFormation |
| Cost savings | No need for data centers | Focus on product instead of infra | Managed databases (RDS) |
| Global deployment | Deploy in multiple regions quickly | Lower latency worldwide | CloudFront, multi-region S3 |
- Key idea: cloud shifts infrastructure from capital expense (CapEx) to operational expense (OpEx)
- Main benefit: elasticity replaces fixed capacity planning
AWS Core Infrastructure Model
AWS is built on a global infrastructure of Regions and Availability Zones, designed for reliability and fault tolerance.
| Concept | Definition | Purpose | Example Service Usage |
|---|---|---|---|
| Region | Geographic area | Isolation + latency optimization | us-east-1 |
| Availability Zone | Isolated data center | Fault tolerance | EC2 multi-AZ setup |
| Edge Location | CDN caching node | Low latency delivery | CloudFront |
- Multi-AZ = high availability
- Multi-region = disaster recovery
AWS Services Overview
AWS provides modular infrastructure services grouped into compute, storage, networking, databases, and messaging. These services form the core building blocks for designing scalable distributed systems in the cloud.
| # | Category | Purpose | Key Services | Typical Use Case |
|---|---|---|---|---|
| 1 | Compute | Run application logic and workloads | EC2, Lambda, ECS/EKS | Backend systems, APIs, microservices |
| 2 | Storage | Persist and retrieve data | S3, EBS, EFS | Files, backups, persistent volumes |
| 3 | Networking | Connect services and manage traffic | VPC, Route 53, CloudFront | Service communication, DNS, CDN |
| 4 | Databases | Structured and unstructured data storage | RDS, DynamoDB | Transactional systems, high-scale apps |
| 5 | Messaging | Enable asynchronous communication | SQS, SNS, EventBridge | Event-driven and decoupled systems |
1. Compute
Compute services provide execution environments for running application logic in AWS, from virtual machines to serverless functions and containerized workloads.
| Service | Type | Execution Model | Primary Use Case |
|---|---|---|---|
| EC2 | Virtual machine | Always-on server | Full control workloads |
| Lambda | Serverless | Event-driven execution | APIs, automation, background tasks |
| ECS / EKS | Containers | Orchestrated workloads | Microservices architecture |
2. Storage
Storage services provide durable data persistence across object, block, and file-based storage models.
| Service | Type | Storage Model | Primary Use Case |
|---|---|---|---|
| S3 | Object storage | Key-value objects | Backups, media, static assets |
| EBS | Block storage | Disk volumes | EC2 persistent storage |
| EFS | File storage | Shared filesystem | Multi-instance shared access |
3. Networking
Networking services define how AWS resources communicate internally and how external traffic reaches applications securely.
| Service | Type | Role | Primary Use Case |
|---|---|---|---|
| VPC | Virtual network | Isolation boundary | Secure infrastructure segmentation |
| Route 53 | DNS service | Domain routing | Traffic routing by domain |
| CloudFront | CDN | Edge delivery | Low-latency global content delivery |
4. Databases
Database services provide managed storage engines optimized for transactions, caching, or analytics.
| Group | Data Model | Services | Primary Use Case |
|---|---|---|---|
| Relational Databases (OLTP) | Structured SQL tables | RDS (MySQL, PostgreSQL, MariaDB, Oracle), Aurora (serverless) | Transactional systems, financial apps, user data consistency |
| NoSQL Databases | Key-value / Document | DynamoDB, DocumentDB (MongoDB) | High-scale systems with low-latency access patterns |
| In-Memory Databases (Caching) | Key-value in RAM | ElastiCache (Redis, Memcached) | Caching, session storage, performance optimization |
| Data Warehouses (OLAP) | Columnar analytical storage | Redshift | Analytics, BI reporting, large-scale data queries |
5. Messaging
Messaging services enable asynchronous communication and decoupling between distributed system components.
| Service | Pattern | Role | Primary Use Case |
|---|---|---|---|
| SQS | Queue | Message buffering | Background job processing |
| SNS | Pub/Sub | Event broadcasting | Fan-out notifications |
| EventBridge | Event bus | Event routing | Event-driven architectures |
| Kinesis | Streaming | Real-time data ingestion | Log streams, analytics pipelines, real-time processing |
Summary
AWS is a cloud infrastructure platform that enables scalable, distributed system design using modular services instead of physical infrastructure.
- Cloud = on-demand infrastructure delivery
- AWS = implementation of cloud at scale
- System design = composition of AWS building blocks
Core idea: AWS replaces infrastructure ownership with infrastructure consumption.
Comments (0)