TL;DR
A long-time AWS user recounts their departure due to frustrations with complexity, billing, and open-source issues, then explains their recent return for testing purposes. The experience underscores persistent challenges with AWS’s ecosystem.
An experienced AWS user who previously left the platform citing numerous frustrations has recently returned to conduct tests, highlighting ongoing issues with AWS’s complexity, billing, and open-source policies.
The user, an early advocate of AWS, publicly detailed their reasons for leaving years ago, citing problems such as lack of native client libraries, expensive and inefficient DynamoDB, complex billing, and restrictive open-source practices. Despite their departure, they recently logged back into AWS to perform specific tests, including benchmarking code on high-performance EC2 instances and evaluating AWS Bedrock for AI models.
During their recent testing, they found that AWS Bedrock and EC2 instances performed as expected, but the costs were significant, and some features, like Claude/Anthropic models, were slow and expensive compared to standalone subscriptions. The user noted that their previous frustrations with AWS remain relevant, especially concerning cost, complexity, and vendor lock-in, but they needed to revisit the platform for specific research and benchmarking tasks.
Why It Matters
This account illustrates that despite years of criticism and a departure driven by frustration, AWS continues to face ongoing challenges related to cost, complexity, and open-source relations, which impact user trust and adoption. The user’s return for testing emphasizes that AWS remains a critical, if problematic, infrastructure provider for certain advanced workloads, and highlights the persistent issues that can influence enterprise decisions.
AWS EC2 high-performance instances
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Background
The user was among AWS’s earliest advocates, witnessing its growth from a small startup to a dominant cloud provider. Their criticisms include the delayed transition to native client libraries, high costs especially for data egress, convoluted billing practices, and aggressive open-source policies. Their departure was driven by frustration with these issues, but their recent return for testing purposes underscores AWS’s ongoing importance in high-performance and AI workloads despite these problems.
“I left AWS because of the unbelievable complexity, cost issues, and their approach to open source. But I had to check how it performs now.”
— the user
“AWS still performs well for certain tasks, but the costs and complexity are still major hurdles.”
— the user
Practical Generative AI on AWS: Building generative AI applications with Amazon Bedrock, Amazon SageMaker JumpStart, and Amazon Q (English Edition)
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
What Remains Unclear
It is not yet clear whether the user’s ongoing frustrations with AWS will influence broader enterprise adoption or if similar sentiments are widespread among other long-term users. The long-term impact of these issues remains to be seen.
Systems Performance (Addison-Wesley Professional Computing Series)
Hardware, kernel, and application internals, and how they perform
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
What’s Next
The user plans to continue testing AWS for specific workloads, particularly high-performance computing and AI, while remaining cautious about costs and vendor lock-in. Broader industry reactions to AWS’s ongoing challenges are also expected to develop as more users share their experiences.
Cloud Cost Management: Volume 13: Practical Strategies to Eliminate Waste and Master Cloud Spending
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Key Questions
Why did the user leave AWS initially?
The user left due to issues with the lack of native client libraries, high costs, billing complexity, and open-source policies that they viewed as predatory.
What prompted the user to return to AWS?
The need to perform specific research and benchmarking tasks that require AWS’s infrastructure, such as testing AI models and high-performance computing, motivated the return.
Are the issues with AWS still present?
Yes, the user reports that many frustrations remain, especially regarding cost, complexity, and vendor lock-in, though AWS still offers valuable capabilities for certain workloads.
Will this influence AWS’s reputation?
This anecdotal account adds to ongoing criticism of AWS but is unlikely to significantly alter its market position unless similar experiences are widely reported.
