Cloud services by Amazon
The hyperscaler with the deepest catalog: use S3, SES and CloudFront selectively before adopting its architecture.
AWS is the hyperscaler that defined cloud breadth: compute, storage, databases, networking, ML and hundreds of services, with the deepest catalog and the most complex pricing in the industry. It is the default for enterprises and the yardstick against which every other provider is measured.
Why it matters to an indie builder: you will use it selectively rather than wholesale. S3 for durable object storage, SES for cheap transactional email, Lambda for event-shaped jobs, CloudFront for CDN: individual services are often the best price for a narrow job. The trap is adopting the platform's full architecture before the product has users.
A realistic setup for a small team: S3 plus CloudFront for assets, SES for email, one small EC2 or Lightsail instance for app servers, and RDS only when a managed database is genuinely needed. Billing alarms and budgets are mandatory from day one.
Trade-offs: cost visibility is hard, IAM is a learning curve, and egress fees punish some architectures. Compare with Cloudflare for edge and storage economics, Hetzner for raw compute price, and the PaaS options for speed to market.
Who it's for
Teams that want the deepest catalogue of cloud services and are willing to manage the complexity.
Official links
Keep exploring
1 in catalog
Amazon Web Services runs on
2 in catalog
Amazon Web Services has a pricing
2 in catalog
Amazon Web Services implements
4 in catalog
Amazon Web Services works with
1 in catalog
Amazon Web Services can be learned in
1 in catalog