Amazon Web Services is the largest cloud platform in the world and has been for over fifteen years. It provides the infrastructure that a web product needs to run - servers, databases, file storage, content delivery, networking, security, and more - as managed services that can be provisioned in minutes and scaled without buying physical hardware. We use AWS as our primary cloud platform because the breadth of services is unmatched, the reliability track record is strong, and the operational tooling is mature enough to build serious production systems on.

‍

Stop guessing capacity. With AWS, you scale on-demand and only pay for what you use.

‍

The way we use AWS varies by project because different products have different requirements. A product that needs a managed Kubernetes cluster uses EKS. A product that needs a managed relational database with automated backups and failover uses RDS. A product that stores user-uploaded files uses S3. A product that needs its static assets delivered quickly to users around the world uses CloudFront. A product that needs to run background processing without managing servers uses Lambda. We choose the service that fits the requirement, not a standard set of services applied to every project regardless of fit.

‍

We manage AWS infrastructure through Terraform - a tool that lets you describe the infrastructure you want in code and apply it to the cloud. This means every server, every database, every security rule, every network configuration is written down, version controlled, and reproducible. Spinning up a new environment - a staging environment that matches production, a temporary environment for testing a new feature - is a matter of running a command. The infrastructure that powers the product is as auditable and maintainable as the application code itself.

‍

What this means for your product:

• Infrastructure that scales with the product without manual intervention

‍

• Managed databases, caching, and storage with built-in redundancy and backups

‍

• Automatic scaling when traffic increases and scale-down when it drops

‍

• Every infrastructure decision written in code - auditable, reproducible, and version controlled

‍

Chips:

AWS · EC2 · RDS · S3 · CloudFront · EKS · Lambda · Terraform · IAM

‍