In FME Server, it is currently possible to add a connection to an Amazon S3 bucket as a resource, but because the S3 Bucket is not mounted as a drive, these external resources can not be used as input or output data locations when running a job on FME Server.
When working with a large volume of cloud-based data, it would be helpful to be able to read from and write to the data without having to first copy the data into FME Server Resources.
Hi @stewartatsafe , is there any progress on this Idea? It seems like a big workaround to write to the directory using S3 Transformers in the Workspace. It would be so much easier by using the $(Data_S3) parameter, like for mounted drives. (see https://community.safe.com/s/question/0D54Q000080hNceSAE/reference-an-s3-bucket-as-a-fme-server-parameter)
Just for anyone looking for this - it seems like there is a way to mount an s3 bucket as a filesystem on linux systems: https://bluexp.netapp.com/blog/amazon-s3-as-a-file-system
It has it's limitations for sure but worth looking into if you want to move to the cloud