Myth: It Was All About Selling Extra Server Space
The most popular version of the AWS origin story is that Amazon bought too many servers for the holiday shopping rush and, rather than let them sit idle, decided to rent out the excess capacity. It’s an elegant, simple narrative. It’s also completely
false. According to company executives, any real excess capacity would have been burned through within months of launching. The reality is that Amazon's own internal infrastructure in the early 2000s was a mess. Teams were struggling to launch new features because they were constantly bogged down by the complexity of provisioning their own computing resources. The drive to create AWS was born from a need to solve Amazon's own crippling internal problems, not from a desire to offload idle machines.
Myth: It Was Part of a Grand Master Plan from Day One
Another common belief is that Jeff Bezos had a grand vision for a cloud computing empire from the very beginning. While Bezos did provide the crucial executive support, the idea for AWS grew organically from the bottom up. Around 2003, two engineers, Benjamin Black and Chris Pinkham, wrote a paper envisioning a future where Amazon's infrastructure was completely standardized and automated. At the same time, Andy Jassy, then a technical advisor to Bezos, was tasked with exploring new business lines. These threads came together not as a master plan, but as a pragmatic solution. Amazon had become good at running reliable, scalable infrastructure out of necessity. The radical idea was to turn this internal competency into an external service, documented with clean APIs that anyone could use.
Myth: EC2, the Virtual Server, Was the First Service
When people think of AWS, they often think of EC2 (Elastic Compute Cloud), the service that lets you rent virtual servers. It's the heart of what many consider 'the cloud.' However, EC2 wasn't the first service AWS launched. The very first service, debuting in a preview form in late 2004, was SQS (Simple Queue Service), a tool for managing messages between software components. The first service to launch to the general public was S3 (Simple Storage Service) in March 2006, which provided object storage. EC2 came months later, in August 2006. This order reveals the true priority: before developers could compute, they needed a reliable way to store their data and manage application workflows—the less glamorous but essential building blocks.
Myth: Its Success Was Purely a Technical Innovation
The technology behind AWS was revolutionary, but the business model was arguably even more disruptive. Before AWS, launching a tech startup meant sinking tens or hundreds of thousands of dollars into buying and managing physical servers. You had to guess your capacity needs, and guessing wrong could kill your company. AWS flipped this model on its head with pay-as-you-go pricing. Suddenly, a developer in a dorm room could access the same world-class infrastructure as a massive corporation and pay only for what they used, by the hour. This wasn't just a technical achievement; it was an economic one. It dramatically lowered the cost of innovation and directly enabled the startup boom of the late 2000s and 2010s, creating an entire generation of companies that were 'born in the cloud'.
