How Jeff Bezos Deployed Amazon Without AWS

Introduction

Today, spinning up a website is as simple as running "gcloud app deploy" or "terraform apply". But back in the mid-1990s, when Jeff Bezos was launching Amazon, cloud computing didn’t exist. There was no AWS, no Azure, no GCP. Only bare-metal servers, co-location facilities, and long nights of manual configuration.

So how did Amazon scale from a tiny online bookstore in Bezos’s garage to a global e-commerce powerhouse, all without the cloud? Let’s step back in time and explore.

---

1. The World Before Cloud

In the mid-90s:

• Hosting meant buying physical servers, typically Unix machines from Sun, SGI, or DEC.
• Networking was set up with routers, switches, and ISPs you negotiated with.
• Scaling wasn’t auto-scaling. It meant physically ordering more machines.
• Deployments involved FTP, tapes, and sometimes sneakers to the data center.

Bezos and his early team had to work in this environment, balancing growth with extremely limited infrastructure options.

---

2. The Garage Setup

Amazon famously started in Bezos’s garage in Bellevue, Washington. The first setup included:

• A couple of small Sun desktop machines, which ran the entire business before the team moved to Digital servers.
• A dial-up connection, in an era when the fastest consumer modems topped out around 28.8kbps.
• Orange extension cords running across the floor, because the garage did not have enough outlets. Power was tight enough that they could not run space heaters and the computers at the same time.

Early on, a bell rang on their computers every time an order came in. It was charming for about a week, then they turned it off, because orders were arriving faster than a bell could stay novel. Orders were printed out and worked from paper. No serverless queues, no managed databases. Just raw scripts and persistence.

---

3. Scaling Without AWS

As orders grew, the tiny garage setup couldn’t keep up. Amazon moved into its own leased office and warehouse space and kept running its own machines. As employee number one, Shel Kaphan, put it, it was all build your own and run it yourself. Scaling meant:

• Buying more servers upfront.
• Racking and cabling them yourself.
• Manually installing operating systems and configuring networking.

Every surge in traffic, especially during holidays, required guessing demand months ahead, often leading to overprovisioning hardware. Unlike today’s elastic compute, there was no “scale to zero” when traffic dropped.

---

4. How Deployments Worked

Deployments at Amazon in the 90s were radically different:

• Deployment was manual, in the way most of the web was manual then.
• Downtime was expected. Taking the site down briefly was normal.
• Logs had to be manually rotated, monitored, and analyzed.
• Databases ran on traditional relational systems (like Oracle) without managed backups or replicas.

Imagine debugging production at 2 a.m. when the only monitoring tool you had was "tail -f logfile".

---

5. Resilience Without the Cloud

To survive:

• Amazon invested in redundant servers for failover.
• Early engineers wrote load-balancing logic themselves (before ELBs or GCLBs).
• They built internal deployment tooling, primitive versions of what we now call CI/CD.

It is tempting to draw a straight line from this era to AWS, and the thematic rhyme is real: Amazon had to build infrastructure nobody could buy. But the honest history is that AWS grew out of the company's early 2000s rebuild around internal services, roughly a decade later, not directly out of the garage.

---

6. Lessons for Today’s Builders

Looking back, Amazon’s early journey teaches us:

• Constraints fuel innovation: Amazon had to invent solutions because nothing existed.
• Manual scaling builds discipline: Teams couldn’t “throw servers at the problem,” so efficiency mattered.
• Cloud is a privilege: Today, startups deploy globally in minutes with infrastructure-as-code, something unthinkable in the 90s.

---

Conclusion

Jeff Bezos didn’t have AWS when he launched Amazon. He had a garage, a handful of servers, and a scrappy team willing to do whatever it took. The fact that Amazon scaled under those conditions is nothing short of remarkable.

The company that once had to buy, rack, and cable every machine it ran eventually built the thing that means you never have to.

So next time you type "gcloud", "aws", or "az" to spin up infrastructure in seconds, remember: Amazon itself was born in a world without the cloud.

---

Liked this post? Follow me for more explorations of how tech giants were built before the cloud era.