April 19, 2024

EC2-Classic in a museum gallery

Retiring companies isn’t one thing we do at AWS. It’s fairly uncommon. Corporations depend on our choices – their companies actually stay on these companies – and it’s one thing that we take significantly. For instance SimpleDB continues to be round, although DynamoDB is the “NoSQL” DB of selection for our clients.

So, two years in the past, when Jeff Barr announced that we’d be shutting down EC2-Classic, I’m positive that there have been at the least a few of you that didn’t consider we’d really flip the swap — that we’d let it run without end. Effectively, that day has come. On August 15, 2023, we shut down the final occasion of Basic. And with all the historical past right here, I feel it’s price celebrating the unique model of one of many companies that began what we now know as cloud computing.

EC2 has been round for fairly some time, virtually 17 years. Solely SQS and S3 are older. So, I wouldn’t blame you in the event you had been questioning what makes an EC2 occasion “Basic”. Put merely, it’s the community structure. Once we launched EC2 in 2006, it was one large community of 10.0.0.0/8. All situations ran on a single, flat community shared with different clients. It uncovered a handful of options, like safety teams and Public IP addresses that had been assigned when an occasion was spun up. Basic made the method of buying compute useless easy, although the stack working behind the scenes was extremely complicated. “Invent and Simplify” is among the Amazon Leadership Principles in any case…

When you had launched an occasion in 2006, an m1.small, you’d have gotten a digital CPU the equal of a 1.7 GHz Xeon processor with 1.75 GB of RAM, 160 GB of native disk, and 250 Mb/second of community bandwidth. And it could have price simply $0.10 per clocked hour. It’s fairly unbelievable the place cloud computing has gone since then, with a P3dn.24xlarge offering 100 Gbps of community throughput, 96 vCPUs, 8 NVIDIA v100 Tensor Core GPUs with 32 GiB of reminiscence every, 768 GiB of whole programs reminiscence, and 1.8 TB of native SSD storage, to not point out an EFA to speed up ML workloads.

However 2006 was a special time, and that flat community and small assortment of situations, just like the m1.small, was “Basic”. And on the time it was really revolutionary. {Hardware} had change into a programmable useful resource that you could possibly scale up or down at a second’s discover. Each developer, entrepreneur, startup and enterprise, now had entry to as a lot compute as they wished, each time they wished it. The complexities of managing infrastructure, shopping for new {hardware}, upgrading software program, changing failed disks — had been abstracted away. And it modified the best way all of us designed and constructed functions.

After all the very first thing I did when EC2 was launched was to maneuver this weblog to an m1.small. It was working Moveable Type and the this occasion was ok to run the server and the native (no RDS but) database. Ultimately I turned it right into a highly-available service with RDS failover, and many others., and it ran there for five+ years till the Amazon S3 Website feature was launched in 2011. The weblog has now been “serverless” for the previous 12 years.

Like we do with all of our companies, we listened to what our clients wanted subsequent. This led us to including options like Elastic IP addresses, Auto Scaling, Load Balancing, CloudWatch, and varied new occasion sorts that may higher swimsuit completely different workloads. By 2013 we had enabled VPC, which allowed every AWS buyer to handle their very own slice of the cloud, safe, remoted, and outlined for his or her enterprise. And it turned the brand new commonplace. It merely gave clients a brand new stage of management that enabled them to construct much more complete programs within the cloud.

We continued to help Basic for the subsequent decade, at the same time as EC2 advanced and we applied a completely new virtualization platform, Nitro — as a result of our clients had been utilizing it.

Ten years in the past, throughout my 2013 keynote at re:Invent, I informed you that we wished to “help at this time’s workloads in addition to tomorrow’s,” and our dedication to Basic is the perfect proof of that. It’s not misplaced on me, the quantity of labor that goes into an effort like this — however it’s precisely any such work that builds belief, and I’m pleased with the best way it has been dealt with. To me, this embodies what it means to be buyer obsessed. The EC2 workforce saved Basic working (and working effectively) till each occasion was shut down or migrated. Offering documentation, instruments, and help from engineering and account administration groups all through the method.

It’s bittersweet to say goodbye to one in every of our unique choices. However we’ve come a great distance since 2006 and we’re not accomplished innovating for our clients. It’s a reminder that constructing evolvable programs is a technique, and revisiting your architectures with an open thoughts is a should. So, farewell Basic, it’s been swell. Lengthy stay EC2.

Certificate of achievement

Now, go construct!

Beneficial posts