Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

AWS Copilot

aws.amazon.com

Post reply on HN
Print view View original

1–10 of 97 posts

Re: AWS Copilot

#2

Post by twillin »

This really seems like it could be a future replacement for Elastic Beanstalk. Especially when they finalize the ability to provision storage infrastructure.

Re: AWS Copilot

#3

Post by polysaturate »

twillin wrote: post #2

This really seems like it could be a future replacement for Elastic Beanstalk. Especially when they finalize the ability to provision storage infrastructure.

That’d be nice. It was a good concept but I really didn’t like how it handled some of the application commands with yaml files.

Re: AWS Copilot

#5

Post by anderiv »

kohidavez wrote: post #4

Hi!! I’m a developer on AWS Copilot! We’d love your feedback! Homebrew: brew install aws/tap/copilot-cli Docs: https://aws.github.io/copilot-cli/ Feedback & Requests: https://github.com/aws/copilot-cli/issues/new

Thanks for your work on this!

Wondering if it’s possible to use this with our own self-managed ASG of ECS Host instances. I trolled through the GH repo quick, but couldn’t find any definitive answer.

Re: AWS Copilot

#6

Post by gavinray »

I happened to catch this on the Github daily trending list a week or so back, really cool.

For similar tools (though this one is ECS + Fargate), also see:

https://somanymachines.com/fargate

https://github.com/awslabs/fargatecli

I'm pretty particular to Pulumi, and defining infra in typed programming languages with full IDE tooling. AWS CDK is the AWS-centric equivalent, and that's a great and under-represented tool as well IMO.

https://www.pulumi.com/containers/

https://docs.aws.amazon.com/cdk/latest/guide/home.html

My issue with ECS/Fargate is that on the surface, it seems amazing. And so you deploy your container, and that's relatively easy.

But now you have just a container on HTTP, on a bare IP. You probably want HTTPS and a domain name attached.

So then you learn that you need to:

- Create a Route53 hosted zone for the domain

- Use AWS Cert Manager to provision certificates for the domain

- Create a load balancer, and figure out how to attach it to the ECS/Fargate service

- Wire up the LB address to the record set and configure the termination for HTTPS

And to do something like change an environment variable, you have to create an entirely new "task definition", deploy the task revision, and then spin up the new service and stop the old one. This takes about 5 not-particularly-easy to find or navigate screens in the AWS console.

This is what it ended up looking like, for me to deploy a Fargate service:

https://gist.github.com/GavinRay97/fbedfb18fe852bf625451a417...

It's great that these tools can help reduce the burden of doing this but man is it a painful experience if you're not a wizard at DevOps.

Google Cloud Run is 1-2 bash commands to deploy a containerized app on HTTPS.

Re: AWS Copilot

#7

Post by kohidavez »

anderiv wrote: post #5
kohidavez wrote: post #4

Hi!! I’m a developer on AWS Copilot! We’d love your feedback! Homebrew: brew install aws/tap/copilot-cli Docs: https://aws.github.io/copilot-cli/ Feedback & Requests: https://github.com/aws/copilot-cli/issues/new

Thanks for your work on this! Wondering if it’s possible to use this with our own self-managed ASG of ECS Host instances. I trolled through the GH repo quick, but couldn’t find any definitive answer.

Not yet - we’ve started out with Fargate but we have a roadmap item to support EC2 and resource imports:

https://github.com/aws/copilot-cli/issues/1094

Re: AWS Copilot

#8

Post by judge2020 »

twillin wrote: post #2

This really seems like it could be a future replacement for Elastic Beanstalk. Especially when they finalize the ability to provision storage infrastructure.

Hopefully. Elastic Beanstalk is a product that "works" and is "maintained", but when it fails it crashes hard. At least for the PHP environment, updating the environment variable configuration can take 2+ minutes, and non-immutable app deployments with 2 hosts can take over 10 minutes to pass health checks. And finally, if it fails to do something (eg. a deploy command fails on the instance), it will be stuck in the "error" state for 5-15 minutes where you can't do anything to the environment and must wait for it to clear to fix your bad deploy.

Re: AWS Copilot

#9

Post by kohidavez »

gavinray wrote: post #6

I happened to catch this on the Github daily trending list a week or so back, really cool. For similar tools (though this one is ECS + Fargate), also see: https://somanymachines.com/fargate https://github.com/awslabs/fargatecli I'm pretty particular to Pulumi, and defining infra in typed programming languages with full IDE tooling. AWS CDK is the AWS-centric equivalent, and that's a great and under-represented tool a…

Copilot can also help set up HTTPS/ACM Certs/Subdomains:

https://github.com/aws/copilot-cli/wiki/Applications#additio...

I love the cloudrun style service too - but one thing I think is cool about running on ECS/Fargate is that once you outgrow the constraints of CloudRun style services - you can drop down to the more granular infrastructure to make tweaks and adjustments. Just my 2c :)

Re: AWS Copilot

#10

Post by throw03172019 »

This reminds me of Convox. Very simple to get started and runs on ECS. Copilot has less features as of now but looks like it’s going in a good direction.

(Happy convox customer)

Post reply on HN