claude-code-as-ops-team-prefers-ec2-over-fargate
When Claude Code is the operations team with SSH access, fully managed services (ECS Fargate, RDS, ElastiCache) actively reduce capability by removing SSH, direct Docker exec, live cron writing, and container-level debugging. The correct pattern for a Claude Code-managed infrastructure is EC2 + Docker Compose, mirroring the Hostinger model — Claude Code needs root access and direct container management to operate at full effectiveness. Fargate ‘zero maintenance’ is the wrong framing when Claude Code IS the maintenance team.
Related
- claude-code-as-ops-team-means-ec2-not-fargate
- zero-maintenance-means-claude-code-manages-not-saas
- claude-code-as-ops-team-changes-aws-architecture-decision
- claude-code-as-ops-team-eliminates-managed-services-need
- fargate-removes-ssh-making-it-incompatible-with-claude-code
- zero-maintenance-means-claude-code-maintains-not-managed-ser
- next-public-env-vars-baked-at-build-time-require-rebuild