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

Docker Releases Plugin for Simplified Deployments into AWS

infoq.com

Post reply on HN
Print view View original

71–80 of 116 posts

Re: Docker Releases Plugin for Simplified Deployments into AWS

#71

Post by jcims »

ramraj07 wrote: post #35
mrgordon wrote: post #23

Earlier quoted context omitted.

I mostly agree with you but we definitely reduced reliance on AWS specific functionality after starting to offer on-premise software installations. Most of them don’t gain you THAT much and then the software really isn’t very portable.

I question this logic - there seem to be fundamental differences in even the basic services between various cloud providers. For example you can resize a compute-attached disk size live in GCP while you can't in AWS. Many intricacies like this are annoying, but at the same time advantageous if you know and use them. If you are primarily trying to just offer another layer on top of these cloud services, (like snowflak…

Not the person you are replying too but some industries have regulatory mandates for vendor diversity in cases like this.

In addition, when your bills get to millions per month, the provider supplies quite a bit of TAMs and technical resources to your account. This can be helpful, but they also get a good understanding of where you are and are not in a position to dip out if things get sideways in billing. (Also, other providers will throw 6-7 figure credits your way to earn your business, being in a position to leverage them is a good thing.)

>Many intricacies like this are annoying, but at the same time advantageous if you know and use them.

This is very true. Building services or features that depend upon these is a good idea. Enshrining them deep within your assumptions and requirements about how you operate cloud-based workloads can work against you.

Re: Docker Releases Plugin for Simplified Deployments into AWS

#72

Post by gonzo41 »

jeremylevy wrote: post #69

At my current startup, we're building something like this. A "catalog" of architectures that you could use to create a complete cloud architecture on your AWS, GCP or Azure account in less than one minute. For example, you could create a docker-based architecture with CI/CD, auto-scaling, zero downtime deployment, SSL, load-balancing, high availability and MongoDB in less than one minute in your own AWS account. Like…

AWS in theory has a product called service catalog that fills this role. It's not super fun. Or at least my interactions with havn't been so great. Good luck.

Re: Docker Releases Plugin for Simplified Deployments into AWS

#73

Post by cooljacob204 »

b112 wrote: post #47
secondcoming wrote: post #36

None of this is simple. We're drowning in YAML files. It's difficult to maintain. Jinja + ansible + helm... it's a joke. There must be a better way of doing all this.

The real problem is, people are deploying dozens of different coding languages, any technology that whimsically passes by, and replacing simple, streamlined monolith technology with 100 micro services. All of this is endlessly pushed by AWS, Google, Docker, and anyone else with a foot in the "Snag as much cash from DEVs" crowd. Other old timers will explain how they ran thousands of hits/second on 6 or 7 bare metal s…

You can containerize a monolith server. I think this is more of a microservice issue then a container issue.

Docker seriously simplifies my life greatly.

Re: Docker Releases Plugin for Simplified Deployments into AWS

#74

Post by nolite »

FunnyLookinHat wrote: post #70
techntoke wrote: post #42

Earlier quoted context omitted.

You mean like Terraform?

Terraform is so heavy handed - I wouldn't call it a deployment tool. It's more of a means to build out infrastructure in AWS. Once you get your AWS account setup there's still virtually no tooling to actually manage deploys of new code into that infrastructure. We're going to hand roll some tooling on top of aws-cli most likely.

What's wrong with https://aws.amazon.com/codedeploy/ ?

Re: Docker Releases Plugin for Simplified Deployments into AWS

#75

Post by mcintyre1994 »

indemnity wrote: post #67
irjustin wrote: post #7

I am in the process of migrating my stack from Elastic Beanstalk multi-container to Fargate so this looked like an interesting thing I could 'pick up'. This does potentially unify the container definitions between compose and ContainerDefinitions in the task definitions, but for my self, that's not a super helpful tool. Much of the complexity of running Fargate is outside of Fargate, wiring everything up so Route 53…

I just spent this weekend setting this up to learn a bit of AWS for a toy project. I thought I would "just" quickly drop a Rust API server image in an ECS cluster. By the end of the weekend, I had the architecture you describe. - Route53 alias A record -> ALB DNS name - LetsEncrypt cert in IAM - ALB listener doing SSL termination using the cert -> forwarding to target group - ALB listener doing 80->443 redirect - Sec…

Would definitely be interested in that blog if you write one :)

Re: Docker Releases Plugin for Simplified Deployments into AWS

#76

Post by jeremylevy »

gonzo41 wrote: post #72
jeremylevy wrote: post #69

At my current startup, we're building something like this. A "catalog" of architectures that you could use to create a complete cloud architecture on your AWS, GCP or Azure account in less than one minute. For example, you could create a docker-based architecture with CI/CD, auto-scaling, zero downtime deployment, SSL, load-balancing, high availability and MongoDB in less than one minute in your own AWS account. Like…

AWS in theory has a product called service catalog that fills this role. It's not super fun. Or at least my interactions with havn't been so great. Good luck.

Thanks!

We've released an alpha version, with only one architecture, some days ago.

If you want to learn more, I've written a blog post: https://medium.com/revolv2/im-building-revolv-to-automate-cl...

Re: Docker Releases Plugin for Simplified Deployments into AWS

#77

Post by yjftsjthsd-h »

indemnity wrote: post #67
irjustin wrote: post #7

I am in the process of migrating my stack from Elastic Beanstalk multi-container to Fargate so this looked like an interesting thing I could 'pick up'. This does potentially unify the container definitions between compose and ContainerDefinitions in the task definitions, but for my self, that's not a super helpful tool. Much of the complexity of running Fargate is outside of Fargate, wiring everything up so Route 53…

I just spent this weekend setting this up to learn a bit of AWS for a toy project. I thought I would "just" quickly drop a Rust API server image in an ECS cluster. By the end of the weekend, I had the architecture you describe. - Route53 alias A record -> ALB DNS name - LetsEncrypt cert in IAM - ALB listener doing SSL termination using the cert -> forwarding to target group - ALB listener doing 80->443 redirect - Sec…

> Considering writing up a blog post about it just to firm up my own understanding as well...

Please do; your setup looks quite nice:)

One nit/question:

> LetsEncrypt cert in IAM

Why LetsEncrypt? AWS Certificate Manager is already free and integrated, IIRC

Re: Docker Releases Plugin for Simplified Deployments into AWS

#78

Post by SingAlong »

leetrout wrote: post #55
SingAlong wrote: post #52

Earlier quoted context omitted.

I'm building a bunch of opinionated Ansible playbooks + tooling, with a Heroku-like experience.

I’m curious- why ansible instead of terraform for dealing with the cloud provider APIs for your base layer of infrastructure?

TBH because Ansible is what I’ve been using for a long time.

And based on what FunnyLookinHat mentions in another comment, Terraform seems to offer a lot less. I have no first-hand experience with Terraform to confirm that.

Re: Docker Releases Plugin for Simplified Deployments into AWS

#79

Post by whatsmyusername »

indemnity wrote: post #67
irjustin wrote: post #7

I am in the process of migrating my stack from Elastic Beanstalk multi-container to Fargate so this looked like an interesting thing I could 'pick up'. This does potentially unify the container definitions between compose and ContainerDefinitions in the task definitions, but for my self, that's not a super helpful tool. Much of the complexity of running Fargate is outside of Fargate, wiring everything up so Route 53…

I just spent this weekend setting this up to learn a bit of AWS for a toy project. I thought I would "just" quickly drop a Rust API server image in an ECS cluster. By the end of the weekend, I had the architecture you describe. - Route53 alias A record -> ALB DNS name - LetsEncrypt cert in IAM - ALB listener doing SSL termination using the cert -> forwarding to target group - ALB listener doing 80->443 redirect - Sec…

What you're describing is what I sold the company on last year (save Letsencrypt, that's weird but whatever).

We only use terraform for the initial burn in (VPC, 2x public/2x private subnets, empty lb, bastion, and some subnet groups) but the rest is one to one.

Fargate isn't the cheapest platform out there but it's great for "I don't have any ops people" or "I have a fraction of several ops people not dedicated to my product." It takes a lot of patching and maintenance out of the equation.

If you want to give yourself a huge resume item, hook AWS WAF into the load balancer and play with it (you can alternatively hook it into Cloudfront if you elect to implement that in front of your LB, though then you have to make sure you protect what Cloudfront is talking to).

Easy task would be to geoip limit your application to the US, Canada, and Mexico. You can verify this by running your site through uptrends and looking at what cities get 403ed https://www.uptrends.com/tools/uptime

Re: Docker Releases Plugin for Simplified Deployments into AWS

#80

Post by yahelc »

solarist wrote: post #30
oblio wrote: post #28

Earlier quoted context omitted.

> eat the frog Eat the frog? Which language is that? The expression sounds really cool! Most of the time in English I've encountered "bite the bullet".

Have you heard of Mark Twain by any chance? People say he used to write in English.

This unnecessary condescension is made all the funnier by the fact that the quote the expression alludes to wasn't actually written by Mark Twain, but in all likelihood by a French writer named Nicolas Chamfort.

https://quoteinvestigator.com/2013/04/03/eat-frog/

Post reply on HN