[finaliteration]

This is great news!

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.

[rumanator]

> Yes, these containers are supposed to be stateless,

You got it backwards. NFS type services help containers be stateless because they are a separate service accessed through an interface where all the state is handled by a third party.

Thus by using a NFS-type service to store your local files, you are free to kill and respawn containers at will because their data is persisted elsewhere.

[dekhn]

containers shouldn't necessarily be stateless; most existing codes don't know how or want to talk to services via RPC interfaces. In some sense, a mounted remote filesystem is just a standard API the OS provides you to access state in a convenient way that happens to be high performance, indexed, etc.

[lsaferite]

Yeah, I think they are conflating stateless and ephemeral in this case.

[finaliteration]

> conflating stateless and ephemeral in this case

You're totally right, I was mixing up stateless and ephemeral. My mistake and thanks for pointing it out!

[blueter]

https://aws.amazon.com/about-aws/whats-new/2020/04/aws-farga... PV 1.4 comes with Single 20gb Volume.