3 ms·

I believe those are just symptoms of the underlying issue; AWS's closed off and slow roll development practices simply could not keep up. They tried to rectify

by Rapzid 8y ago

I believe those are just symptoms of the underlying issue; AWS's closed off and slow roll development practices simply could not keep up. They tried to rectify the situation with Blox; I'm honestly not sure how that is going. When you ask about attaching EFS or EBS to services in fargate and they ask what your use case for that is... In the words of Drake; "...we gonna see."

geerlingguy 8y ago
Yeah, no EFS in Fargate is a deal-breaker; we manage our own nodes in ECS right now, just because we want EFS support. It was kind of too-little-too-late, same thing with Route53 DNS-based service discovery—it's annoying when you feel nickel-and-dimed into adding an (relatively expensive, IMHO) ELB/ALB per service to be able to direct requests to the backend. I'm hoping EKS will evolve a lot more quickly and stay up to date with the upstream; it would be awesome if AWS has full and stable support for all the major bits like persistent volumes (on EFS or EBS), LoadBalancers (ELBs/ALBs, hopefully more configurable someday), etc. It sounds like the beta period is over and AWS is ramping up for EKS' GA soon.