11–20 of 21 posts
Self promotion, but I recently published an intro to ECS after doing an extensive evaluation: http://www.infoq.com/articles/intro-aws-ecs . ECS is solid. Happy to answer any questions on it.
As someone relatively new to Docker, the latter was extremely helpful.
We're in the process of transitioning from our datacenter to AWS and we landed on much the same set of technologies, minus Docker.
Using DNS for service discovery is very convenient but it also makes it difficult to change your setup quickly in the face of ops emergencies, since it's so aggressively cached. We're in the process of transitioning from our datacenter to AWS and we landed on much the same set of technologies, minus Docker.
I'm on android 5.0.1 in chrome
No matter what url I try to visit at https://segment.com I get an ssl encryption error. I'm on android 5.0.1 in chrome
I just setup something similar for one of our api services as a trial to see how it would work out. My biggest gripe with ECS is that it currently does not support dynamic port mapping between ELB and a container instance. For example, if your service listens on port 8080, and ELB terminates port 443 and forwards to a container, then you can only have one container instance per EC2 cluster node, b/c spinning up two c…
Using DNS for service discovery is very convenient but it also makes it difficult to change your setup quickly in the face of ops emergencies, since it's so aggressively cached. We're in the process of transitioning from our datacenter to AWS and we landed on much the same set of technologies, minus Docker.
If done right can really be awesome , set up stack using hasicorp's consul(consul.io) and theres the option to change the TTLs and cache limits.If using the DNS interface the updates are relatively painless and nodes are almost instantly available when provisioned.