2 ms·

I remember I had asked you forever ago about what issues you had, so I looked it up and you responded! One thing I don't understand from your response is Amazo

by dastbe 10y ago

I remember I had asked you forever ago about what issues you had, so I looked it up and you responded! One thing I don't understand from your response is Amazon also funnels you into using a single container type per EC2 instance. It's not impossible to use a single EC2 instance for multiple containers, but if you desire to run multiple instances of one specific kind of container on one node, ECS doesn't make the implementation easy for you at all. Was this related to ELBs and host ports? ELB really isn't a great fit for containers because you attach them to the instance on specific ports, which stops you from running multiple copies of a task on a single instance and also requires a lot of port janitoring between different tasks. ALBs attach via instance:port pairs, so they can actually work as a "container load balancer".

fapjacks 10y ago
Yes, but actually I just threw in an instance of the jwilder/nginx-proxy for this since it was HTTP-based traffic and needs to be proxied by hostname. I suspect this is similar to what you're describing with ALB, but this goes back to another one of the big reasons I recommend against ECS: Terrible documentation and ##aws on Freenode is not a helpful community. Pretty much any other container orchestration application has a thriving community on Freenode which is indispensable for problems like this. But ##aws is almost exclusively populated by other frustrated users.
- dastbe 10y ago
  Yep, sounds like ALBs would've helped. They were only launched in August 2016 so it sounds like they weren't available when you were doing your project. They just conceptually map better to containers and the documentation has been updated to recommend ALBs unless you need layer4 routing. Documentation is always a moving target, but the feedback links at the bottom of documents, in the console, and feedback to CS do make it through to service teams who act upon it. As for Freenode, AWS doesn't maintain an official presence there (same w/ AWS reddit). I understand you're probably looking for something more synchronous/interactive, but the AWS forums ( https://forums.aws.amazon.com https://forums.aws.amazon.com ) are the official place for getting public feedback from AWS.

by dastbe 10y ago

fapjacks 10y ago

Yes, but actually I just threw in an instance of the jwilder/nginx-proxy for this since it was HTTP-based traffic and needs to be proxied by hostname. I suspect this is similar to what you're describing with ALB, but this goes back to another one of the big reasons I recommend against ECS: Terrible documentation and ##aws on Freenode is not a helpful community. Pretty much any other container orchestration application has a thriving community on Freenode which is indispensable for problems like this. But ##aws is almost exclusively populated by other frustrated users.

dastbe 10y ago
Yep, sounds like ALBs would've helped. They were only launched in August 2016 so it sounds like they weren't available when you were doing your project. They just conceptually map better to containers and the documentation has been updated to recommend ALBs unless you need layer4 routing. Documentation is always a moving target, but the feedback links at the bottom of documents, in the console, and feedback to CS do make it through to service teams who act upon it. As for Freenode, AWS doesn't maintain an official presence there (same w/ AWS reddit). I understand you're probably looking for something more synchronous/interactive, but the AWS forums ( https://forums.aws.amazon.com https://forums.aws.amazon.com ) are the official place for getting public feedback from AWS.