TL;DR
A long-time AWS supporter recently returned to the platform for testing purposes and was quickly reminded of the many longstanding issues that led him to leave. Despite brief reconnections, core frustrations remain unaddressed, reaffirming his decision to exit AWS previously.
A former AWS supporter returned to the platform for testing purposes and was quickly reminded of its longstanding issues, reaffirming his decision to leave AWS previously. This personal experience underscores ongoing criticisms of AWS’s complexity, cost, and vendor lock-in, which continue to discourage some users.
The individual, an early AWS advocate, had previously exited the platform after years of frustration with its complexity, cost, and policies. Recently, he logged into his AWS account to conduct specific tests, including evaluating AI services on Bedrock and benchmarking high-performance EC2 instances. Despite a smooth initial experience, he was reminded of the platform’s persistent issues, such as high costs, complex billing, and vendor lock-in, which contributed to his decision to leave AWS in the past. He noted that while some services like Bedrock worked adequately, the overall experience reinforced his negative perceptions, especially regarding cost and complexity.
He highlighted ongoing frustrations with AWS’s handling of open-source projects, billing practices, and the difficulty of managing IAM permissions. His recent testing confirmed that AWS remains a platform that, while powerful, is riddled with issues that many users find problematic. He has not returned to use AWS extensively but only for specific research and testing, and he continues to see these issues as reasons for skepticism about the platform’s long-term value for many users.
Why It Matters
This personal account illustrates why some former AWS users remain skeptical about the platform despite its dominance. The issues of cost, complexity, vendor lock-in, and open-source conflicts continue to influence decision-making for developers and organizations. For AWS, ongoing criticism could impact its reputation among tech-savvy users and open-source communities, especially as competitors improve transparency and user control.
AWS EC2 high performance instances
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Background
AWS launched in 2006 and quickly became a dominant cloud provider, praised for its scalability and innovation. Over the years, criticisms have emerged around its billing complexity, high costs, vendor lock-in, and perceived prioritization of profit over user experience. Many users, including early advocates, have left or reduced their use due to these issues. Recent efforts by AWS to expand services like Bedrock and EC2 have not fully addressed these core concerns, which remain a barrier for some users considering re-engagement.
“Despite some services working fine, the experience reminded me why I left AWS in the first place—costs, complexity, and vendor lock-in are still major issues.”
— the individual
“AWS remains a powerful but complex platform that continues to face criticism over cost and vendor lock-in, which could hinder its appeal to a broader user base.”
— industry analyst
Ultimate Certified FinOps Practitioner Exam Guide: Master Cloud Financial Operations with Real-World Strategies, Hands-On Tools, and Complete … FinOps Practitioner Exam (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 AWS has made any significant improvements addressing these longstanding issues or if this experience is representative of broader user sentiment. The individual’s experience is personal and may not reflect all user experiences across the platform.
Implementing Identity Management on AWS: A real-world guide to solving customer and workforce IAM challenges in your AWS cloud environments
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
What’s Next
AWS may continue to refine its services and address some criticisms, but it remains to be seen whether these changes will significantly alter user perceptions. The individual plans to avoid long-term re-engagement but will continue to use AWS for specific testing needs, monitoring for any improvements or further issues.
AWS Bedrock in Action: Hands-On RAG, Agents & Guardrails on AWS with Python, TypeScript & CDK
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Key Questions
Why did the individual leave AWS originally?
He left due to persistent issues with cost, complexity, vendor lock-in, and dissatisfaction with AWS’s handling of open-source projects and billing practices.
What specific issues did he encounter during his recent testing?
He experienced high costs, complex billing, and ongoing frustrations with AWS’s service complexity, especially around IAM and vendor lock-in, despite some services functioning adequately.
Does this mean AWS is no longer a viable platform?
This account suggests that for some users, AWS’s issues remain significant barriers. While powerful, these problems can outweigh benefits for those sensitive to cost and complexity.
Will the individual return to AWS long-term?
No, he plans only to use AWS for specific research and testing, not as a primary platform, citing ongoing frustrations and a desire to avoid vendor lock-in.
