AWS

What is it

Amazon Web Services (AWS) is Amazon’s cloud computing platform, offering a broad set of global cloud-based products including compute, storage, databases, analytics, networking, machine learning, and artificial intelligence. AWS was the first major cloud provider (launched 2006) and remains the largest by market share.

My Opinion

AWS is the default choice because it’s the default choice. It has the most services, the largest ecosystem, and the deepest talent pool. But it’s also the most complex, the most expensive to optimize, and the most likely to make you rage-quit during configuration. Being first doesn’t mean being best.

The “Everything Store” Problem

AWS has over 200 services. Two hundred. Some overlap, some are obscure, and many solve problems you didn’t know you had. The learning curve is vertical, not horizontal.

You don’t just “learn AWS”—you learn EC2, S3, RDS, Lambda, ECS, EKS, DynamoDB, ElastiCache, API Gateway, CloudFormation, and a dozen other services just to build a simple application. Compare this to Cloudflare, where you configure Pages and Workers and you’re done.

The Configuration Hell

AWS services are powerful but painful to configure. IAM policies are a JSON nightmare. VPC networking requires a PhD. CloudFormation templates are thousands of lines of YAML. The abstraction layers are deep, and when they leak, you’re debugging service interdependencies that make your head spin.

Every AWS engineer has a story about spending a day debugging why Lambda can’t reach RDS, only to discover a missing security group rule.

The Ecosystem Moat

This is why you choose AWS despite the pain. The ecosystem is massive:

• Third-party tools support AWS first
• Blog posts and tutorials assume AWS
• The talent pool knows AWS
• Every SaaS product integrates with AWS

If you’re stuck on an AWS issue at 2 AM, there are thousands of Stack Overflow posts and blog articles to help. That peace of mind is worth the complexity tax.

The “Pricing Surprise”

AWS pricing is deliberately confusing. Reserved instances, spot instances, on-demand, savings plans—the discounts are real, but understanding them requires a full-time cost optimization team. Your bill arrives and you’re wondering: “What is this $47 ‘Elastic Load Balancing Data Processing’ charge?”

GCP and Azure aren’t perfect either, but AWS’s pricing model feels designed to maximize confusion.

The Innovation Lag

AWS was first, but that doesn’t mean they’re best anymore. GCP has better Kubernetes (they invented it). Cloudflare has better edge computing. Azure has better enterprise integration. Some AWS services feel like they haven’t been updated since 2015.

The innovation rate has slowed as they’ve grown larger. New features often feel like incremental improvements rather than paradigm shifts.

Conclusion

AWS is the safe, boring choice. It works, it’s everywhere, and you’ll never be fired for choosing it. But if you’re starting fresh and don’t need the ecosystem breadth, GCP might be simpler for containers and data, Cloudflare better for edge, or Azure better for Microsoft shops. Choose AWS when you need the ecosystem, not by default.