by ifcologne on 4/8/20, 9:06 PM with 30 comments
by txcwpalpha on 4/9/20, 1:06 AM
That probably won't solve all EFS performance issues, but it's a pretty big boost and a nice announcement to come alongside ECS support.
https://aws.amazon.com/about-aws/whats-new/2020/04/amazon-el...
by finaliteration on 4/8/20, 9:45 PM
Yes, these containers are supposed to be stateless, but I was tasked with converting an app at my previous job over to using ECS on Fargate and we hit so many issues because of the limits on storage per container instance. We ended up having to tweak the heck out of nginx caching configurations and other processes that would generate any "on disk" files to get around the issues. Having EFS available would have made solving some of those problems so much easier.
I've also been wanting to use ECS on Fargate for running scheduled tasks with large files (50gb+) but it wasn't really possible given the previous 4gb limit on storage.
by jboggan on 4/8/20, 10:52 PM
If you're wondering why you'd ever have to do something like that, the answer is SAP.
by koolba on 4/8/20, 10:06 PM
by mark242 on 4/8/20, 9:52 PM
by zapita on 4/8/20, 10:09 PM
We evaluated it for a relatively simple use case, and the performance seemed abysmal, so we didn't select it. I'm hoping that we made a mistake in our evaluation protocol, which would give me an excuse to give it another try.
by geerlingguy on 4/8/20, 10:24 PM
by WatchDog on 4/8/20, 10:45 PM
by rkwasny on 4/8/20, 11:28 PM
My advice, stick to EC2 + EBS, it works.
by djstein on 4/8/20, 9:43 PM
by nnx on 4/9/20, 2:10 AM