I need to be able to archive execution history and task history to Amazon S3 instead of a local filesystem. From the documentation it looks like the “Output path for archives” field only accepts filesystem paths relative to the local host. How can remote cloud storage be specified and an output target?
Hi starsailor,
I would save the history into the local filesystem and then use File Event Listener with a graph uploading it into Amazon S3 using the following URL format:
http://access_key_id:secret_access_key@bucketname.s3.amazonaws.com/filename.out
Or alternatively, you can download the execution history via HTTP API and upload it right away.
Regards,
So what you are saying is the Archivator doesn’t know how to access Amazon S3 or other cloud based file stores, right? Based on your reply am I correct to say that the Archivator only know how to write archive output thru the local system file api?
Correct, it can save the archive only into the local file system.