The S3Connector would be useful if there could be a Writer that intigrates and uses the connection to an S3 bucket (i.e., treat it like a virtual drive. So anywhere you define a file path, an S3 bucket connection/path can be specified making S3 storage as transparent as possible.
Also, within the S3Connector parameters that there are only two options for "If file exists": Reject or Overwrite. It would also be very useful to add an Append option so that the same zip file can be used for scenarios where batches of workspace runs can be captured in a single zip file...
I'm hoping this gets into 2019 sooner than later.
Thanks for all you do...
Also, suggest adding a s3connector topic.
