This message was deleted.

Is it possible to create a volume using EFS that is loaded up with the source and shared between containers? What are my options?

If you want to have 2 containers, I think using EFS is basically your only option, because you need a file system that can have read/write from multiple sources, which EBS can't do. I would personally make a single container and ensure it's forked properly from something like dumb-init. I think introducing EFS as a potential performance bottleneck is unnecessary. Most php-fpm applications use a single container

Thanks @billowy-army-68599 Doing a COPY on both containers would be fairly trivial. If I was to go the EFS route, how do I actually push the files to it? Is that achievable via the AWS API or does it need to be attached to EC2 or Lambda first?

Yet another alternative (without EFS) is to create a single image with everything in it, but which allows for separate

ENTRYPOINT

or

CMD

. You still run a pod with 2 containers, but both using the same image using the different

ENTRYPOINT

or

CMD

.

What's the best way to get secrets into ECS? The passwords will be visible in plain text.

@quaint-guitar-13446 the best way is to store them in AWS SSM or AWS Secret manager: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/specifying-sensitive-data.html

Thank you