Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

That’s actually a good point. It’s been 6 years since I have deployed to EC2. I have been doing Lambda or ECS/Fargate.

But when I did it was either:

1. Azure DevOps with agents on EC2

2. Octopus Deploy with agents (not my choice)

3. CodeDeploy with agents

All of those are horrible choices.

On the other hand, my Fargate deployments have all been:

1. Create Docker container

2. Push to ECR

3. Deploy a parameterized CloudFormation template to update an ECS cluster.

I’ve used a modified version of this template for 7 years. I’m not the author.

https://github.com/1Strategy/fargate-cloudformation-example/...



Exactly, I think any solution that is just like “build docker container, push docker container” is very much what you want as a startup.

“Avoid k8s” shouldn’t mean “avoid containers” because they have major velocity and reliability benefits for small teams with no ops engineers.

I totally agree with you that CodeDeploy in particular is miserable. I’d much rather overpay for compute using Fargate than be saddled with that.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: