Ok. Thanks for clarification.
Please, consider my notes:
1. Yves is stateless Frontend server. Any persistent data flow must go via Zed gateway.
2. Yves containers should have limited access to the services and should be in isolated network conditions. Only Zed gateway, denormalized data access, session and caches should be accessible.
3. Filesystem of the container cannot be assumed as a persistent storage. You would have multiple zed servers for high availability and scaling purposes.
4. A message in a broker queue should not be overloaded with the huge payload. Most message brokers have strict limitations on that.
5. The cost of putting file into the queue would be the same as putting into a file storage service or even better.
So my suggestions are:
1. I would propose to not use containers filesystem as a persistent storage. Even more: I would recommend to avoid any RO/RW operations within PHP containers.
2. If you do not want to use Zed gateway for the uploading you would consider using another service that can manage file storing.
3. You can use
https://www.php.net/manual/en/function.fastcgi-finish-request.php to release client and upload file in background.
I would propose something more particular if you would give me more context, production environment specification and other info.