Show HN: A CLI to set up container environments in AWS

Copilot is great! But, it's intentionally only about ECS and a single service. Whereas Digger is operating at the entire stack level, and will support a variety of deployment targets, including other AWS services, other cloud providers eg Google Cloud Run, Kubernetes etc. ECS is just the first one supported.

With Digger we want to create a convenience layer to manage cloud infrastructure that will bridge the gap between paas that has great UX but quickly gets expensive and limiting, and major clouds that are cheaper and more flexible, but hard to figure.

Re: Show HN: A CLI to set up container environments in AWS

#5

Post by jordannoble » Tue, Nov 17, 2020, 4:07 PM UTC

This looks cool, but why would I use this over Heroku?

Re: Show HN: A CLI to set up container environments in AWS

#6

Post by izalutski » Tue, Nov 17, 2020, 4:15 PM UTC

jordannoble wrote: post #5

This looks cool, but why would I use this over Heroku?

With Heroku you are stuck with what they offer, and it quickly gets unreasonably expensive compared to AWS / GCP / Azure.

Digger is just as easy to use, but you don't overpay for resource and if you want something more custom, you can always do it directly in the underlying cloud account. Digger helps with that as well by generating Terraform modules that you can tweak for your needs.

Re: Show HN: A CLI to set up container environments in AWS

#7

Post by izalutski » Tue, Nov 17, 2020, 5:05 PM UTC

mz_data wrote: post #3

Amazing project! Good luck!

Thanks @mz_data!

Re: Show HN: A CLI to set up container environments in AWS

#8

Post by gchristenb » Tue, Nov 17, 2020, 5:52 PM UTC

izalutski wrote: post #6

jordannoble wrote: post #5

This looks cool, but why would I use this over Heroku?

With Heroku you are stuck with what they offer, and it quickly gets unreasonably expensive compared to AWS / GCP / Azure. Digger is just as easy to use, but you don't overpay for resource and if you want something more custom, you can always do it directly in the underlying cloud account. Digger helps with that as well by generating Terraform modules that you can tweak for your needs.

Congrats guys - I prefer this level of abstraction. I'm assuming as I user I can dig in a bit deeper? Edit terraform manually, etc?

Re: Show HN: A CLI to set up container environments in AWS

#9

Post by izalutski » Tue, Nov 17, 2020, 5:57 PM UTC

gchristenb wrote: post #8

izalutski wrote: post #6

Earlier quoted context omitted.

With Heroku you are stuck with what they offer, and it quickly gets unreasonably expensive compared to AWS / GCP / Azure. Digger is just as easy to use, but you don't overpay for resource and if you want something more custom, you can always do it directly in the underlying cloud account. Digger helps with that as well by generating Terraform modules that you can tweak for your needs.

Congrats guys - I prefer this level of abstraction. I'm assuming as I user I can dig in a bit deeper? Edit terraform manually, etc?

Yes, Digger generates TF files and stores it in the dedicated "main" repository, separately for each environment. You can tweak these files directly, or override the defaults in the templates. So unlike black-box PaaS you retain full control of the infrastructure, Digger just makes this complexity optional.