8:50in productionCh. 1 · The Developer Portal/ 8:50 · ceiling 15 min
Systems · Web & cloud
Amazon Web Services
2006
AWS did not invent the cloud—it repackaged Amazon’s internal automation as a product, and won by shipping first, not by being smarter.
AWS launched S3 in March 2006 as its first generally available Infrastructure-as-a-Service offering. It evolved from internal Amazon platform standardisation efforts beginning in the early 2000s. Its first developer-facing web services shipped in July 2002. Simple Queue Service (SQS) launched in beta in November 2004 and became generally available in July 2006. EC2 followed in August 2006. AWS was the first cloud provider to build infrastructure specifically for U.S. government security and compliance requirements, launching GovCloud in 2011.
AWS began not as a cloud company but as an internal developer platform opened to the public in 2002.
2:26
First Services, Not First Vision
S3 (March 2006) was AWS’s first generally available IaaS; SQS (November 2004, beta) was its first infrastructure service.
3:50
Built for Amazon First
EC2 emerged from an internal paper calling for full standardisation and automation—not from external market demand.
5:32
GovCloud Preceded the Market
AWS was the first cloud provider to build infrastructure specifically for U.S. government security and compliance requirements.
Worth your time?
Yes. Study the whole thing.
4.5/ 5
What works
S3 delivers durable, scalable object storage via HTTP APIs
EC2 delivers virtual servers on demand
SQS provides managed message queuing
GovCloud meets U.S. government classification requirements
What does not
eliminate infrastructure complexity
abstract away failure modes
remove vendor lock-in
Study it if
developers who need scalable, on-demand infrastructure
organisations with capacity to manage cloud-native operations
Skip it if
teams requiring predictable low-level control
those unable to adapt applications to distributed systems
The written brief1 min read
What it is and the problem it solves
AWS is a set of programmable infrastructure services built from Amazon’s internal platform. It solves the problem of slow, manual infrastructure allocation for external developers and internal teams alike.
How it works
AWS exposes internal Amazon infrastructure as programmable web services. Developers call APIs to provision storage (S3), compute (EC2), or message queues (SQS). It runs on Amazon’s own data centres, not third-party hardware.
What works
S3 delivers durable, scalable object storage via HTTP APIs. EC2 delivers virtual servers on demand. SQS provides managed message queuing. All three operate at global scale with documented SLAs. The GovCloud initiative proves AWS can isolate infrastructure to meet U.S. government classification requirements.
What does not
AWS does not eliminate infrastructure complexity. It shifts it from hardware procurement to API governance, state management, network configuration, and vendor lock-in. It does not abstract away failure modes—network partitions, region outages, and misconfigured permissions remain operational realities.
What it changes
It changes who controls infrastructure provisioning—from IT departments and colocation providers to software developers with API keys. It changes cost models from capital expenditure to variable, usage-based billing. It changes security responsibility from shared physical premises to a defined split between AWS and the customer.
Is it worth your time
Yes—if you need scalable, on-demand infrastructure and can manage the operational overhead of cloud-native tooling. It is not worth your time if you require predictable low-level control or have no capacity to adapt applications to distributed systems.