Using the S32GCS-Copy request type, users of LegacyFlo can copy one or more files from a source S3 bucket to a destination Google Cloud Storage (GCS) bucket.
Buckets can be in different accounts and in any region supported by LegacyFlo.
The request will copy files from the source to the destination, overriding any files with the same name already present.
If source files are not present or cannot be accessed, then these will be skipped. The list of such files will be available in the logs which will be available after the completion of the request.
The S32GCS-Copy request can also be used to copy to and from the Vaultastic Open Store to Google Cloud Storage.
Before submitting an S32GCS-Copy request
1. If the source is your own S3 bucket, then register it with LegacyFlo.
Source information (S3 bucket)
|S3 Bucket Name|
The S3 bucket that has the source file to be copied. Select the S3 bucket name from the drop-down list.
The list will show
|S3 Folder path|
If the files are on the Vaultastic Open Store, then this parameter will have the name of your Vaultastic domain. Example: baya-com.vaultastic.com
If the file is on your own bucket, give the folder which contains the files. Leave this value empty if the source file is on the root of the S3 bucket.
NOTE: S3 folder path should not start or end with a "/"
Source Filter information
|CSV File||Select the CSV file with the list of files to be copied.|
The file should have a single column.
The first row is the header, with the keyword FileName
Subsequent rows will have the names of the files on the source bucket in the specified path.
Note: Each CSV file should not have more than 100 filenames.
Destination information (GCS Bucket)
|GCS bucket name|
The GCS bucket for the destination files. Select the GCS bucket name from the drop-down list.
The list will show
|GCS Folder path|
If the files have to be copied on your own bucket, give the folder which will contain the file. Leave this value empty if the destination file has to be created on the root of the GCS bucket.
NOTE: GCS folder path should not start or end with a "/"