I returned to AWS and was reminded why I left

A former AWS supporter who left the platform after 15 years due to persistent frustrations has recently returned to conduct tests and research, highlighting ongoing issues with the service.

The individual, an early advocate for AWS, describes their initial enthusiasm and subsequent disillusionment over issues such as lack of native client libraries, high costs, complex billing, and the platform’s increasing complexity. They left AWS completely, retaining only a few services like Route53, S3, and Workmail. Recently, they logged back into AWS to perform specific tests, including benchmarking code on large EC2 instances and experimenting with AWS Bedrock for AI models.

During the recent tests, they reported no significant issues with launching instances or using Bedrock, but emphasized that the costs are prohibitively high for regular use. They also noted that their brief return was solely for research purposes and not a sign of renewed loyalty to AWS.

Why It Matters

This account illustrates the challenges and frustrations faced by long-term users of AWS, including cost, complexity, and vendor lock-in, which continue to influence cloud strategy decisions. It also highlights how even disillusioned users may briefly re-engage with the platform for specific needs, revealing the platform’s persistent dominance despite criticisms.

Background

Originally launched in the mid-2000s, AWS rapidly grew to dominate the cloud infrastructure market, attracting developers and enterprises worldwide. Over the years, many users, including early advocates, have expressed frustrations over AWS’s evolving features, costs, and policies. The individual’s experience reflects a broader trend of disillusionment among some long-term users who feel AWS’s complexity and pricing have become prohibitive, prompting some to leave or reduce their reliance on the platform.

“I left AWS after 15 years because of its unbelievable complexity, high costs, and vendor lock-in. Returning was just for testing and research, not a sign of renewed loyalty.”

— former AWS advocate

“Costs for services like Bedrock and large EC2 instances are astronomical, but sometimes you need to test or benchmark, and AWS remains the only viable option for certain workloads.”

— the user

What Remains Unclear

It remains unclear whether this brief engagement will lead to any future use of AWS or if the user’s criticisms reflect broader industry trends. The long-term impact of such disillusionment on enterprise cloud adoption is also uncertain.

What’s Next

The user plans to analyze the cost-effectiveness of AWS services for specific research projects and may revisit the platform for further testing. Broader implications for AWS’s user base remain to be seen, especially as competitors and alternative solutions evolve.

Key Questions

Why did the user leave AWS after 15 years?

The user left due to frustrations with AWS’s lack of native client libraries initially, high costs, billing complexity, vendor lock-in, and increasing platform complexity.

What motivated the recent return to AWS?

The return was driven by the need to conduct specific tests, including benchmarking large EC2 instances and experimenting with AWS Bedrock for AI models, which are not easily replicated elsewhere.

Does this mean the user is returning to AWS long-term?

No, the user emphasizes that their return was solely for research and testing purposes, not a renewal of loyalty or ongoing reliance on AWS.

What does this reveal about AWS’s user experience?

It highlights persistent issues with costs, complexity, and vendor lock-in that continue to frustrate long-term users, despite AWS’s dominance in the cloud market.