technologybriefs
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.

SystemsWeb & cloudAbstractionAutomationComputingAbstraction across the network →
Chapters & takeaways4
  1. 1:03
    The Developer Portal

    AWS began not as a cloud company but as an internal developer platform opened to the public in 2002.

  2. 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. 3:50
    Built for Amazon First

    EC2 emerged from an internal paper calling for full standardisation and automation—not from external market demand.

  4. 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.

Same field · Systems4 of 192
9:29
Docker (software)2013Docker is a Linux containerisation platform that delivers applications in isolated, kernel-native process containers. It launched open-source in March 2013 at PyCon Santa Clara. It works by leveraging cgroups, namespaces, and OverlayFS—avoiding VM overhead but requiring Linux. It enables consistent execution across Linux environments, yet fails on non-Linux hosts without abstraction layers. It changed infrastructure abstraction from machines to processes—but only where the kernel permits. It is worth your time if you operate on Linux and need reproducible deployments.
8:58
Computer numerical controlCNC replaced punched-tape numerical control with computer-driven instruction sets. It shifted manufacturing from fixed logic to editable code—making parts repeatable, but not autonomous. Its success came from falling computing costs, not new physics or AI.
9:07
Kubernetes2014Kubernetes is a container orchestration system announced by Google in June 2014 and released as version 1.0 on July 21, 2015. It was conceived by Joe Beda, Brendan Burns, and Craig McLuckie. Inspired by Google's Borg system but written in Go instead of C++, it uses Promise Theory to define infrastructure as declarative objects. It assembles virtual or bare-metal machines into clusters and automates deployment, scaling, and management of containerised workloads based on CPU, memory, or custom metrics.
9:31
Windows 3.11992Windows 3.1 is a transitional 16-bit operating environment released on April 6, 1992. It introduced the Windows Registry, TrueType fonts, Media Player, Sound Recorder, and screensavers. Its 386 Enhanced Mode functions as a virtual machine monitor virtualising MS-DOS as a guest. It was the last 16-bit Windows release.
Up next in Technology

Advanced Message Queuing Protocol

2003 · 10:23

AMQP doesn’t make messaging easier—it makes it portable, at the cost of ignoring everything that happens before and after the wire.

Play nextBack to Systems
10:23