I have the FME Server Core running in a CentOS instance in AWS and a number of engines on separate instances. The shared resources folder is in an Elastic File System mounted to all the engines and the Core.
I noticed that when new folders are created from the FME Web UI, they are created by the root user and not by the fmeserver user as I was expecting. This is causing the engines to have problems writing into those new folders because the fmeserver user (which is the user that runs the workspace) lacks the necessary permissions.
I can't keep modifying every new folder's permissions to allow for the fmeserver user to be able to write to them. What could be a more permanent solution? Can the Core be changed to use the fmeserver user instead when creating new directories?