AWS veteran shares why complexity and costs led to departure
Original: I returned to AWS, and was reminded why I left
Why This Matters
Highlights enterprise concerns about cloud vendor lock-in and hidden complexity costs
A longtime AWS advocate with 15+ years experience details growing frustrations with the platform, citing complex billing, expensive egress fees, IAM complexity, and vendor lock-in issues that ultimately led to leaving the service after being an early supporter.
A developer who organized the first AWS event in Melbourne and was an early advocate for services like SQS, S3, and EC2 has shared why they departed AWS after 15 years. Initial frustrations included AWS not building client libraries for 6 years, slow Python 3 adoption, and DynamoDB issues resulting in unexpected $75 daily bills. Key concerns highlighted include egress costs dropping from 20 cents to 9 cents per gigabyte but remaining expensive, complex billing with hidden charges for internal data movement, and IAM's complexity. The developer criticized Lambda for slow startup times and development complexity, noting it was the hardest service to migrate away from due to vendor lock-in. They argue AWS has become as complex as self-managed infrastructure while requiring expensive expert teams.