Creating custom file names for S3 objects - Amazon S3 Glacier Re:Freezer

Creating custom file names for S3 objects

You can provide your own custom S3 object key names for each ArchiveId that is to be copied to your Amazon S3 bucket, by providing your own filename-mapping file to the solution.

Use the following process to provide your own filename-mapping file during deployment via the [OPTIONAL] External filenames override for ArchiveDescription parameter.

  1. Create a filename-mapping file in CSV format. The file must contains only two columns: GlacierArchiveID and FileName (separated by a comma).

GlacierArchiveID

FileName
WVfrXME2KC6JIedfadJF937412-e mydata1.txt
yLam5H76JXYSKKIY34404D-Kwcrk myfolder/mydata2.txt

Table 3: Example filename-mapping csv

  1. Obtain a copy of your S3 Glacier vault inventory file.

  2. Copy all the ArchiveId values from your S3 Glacier inventory file, and paste them into the GlacierArchiveID column of your filename-mapping CSV file.

  3. In the FileName column, for each ArchiveID, enter the your new S3 object key name.

    For any rows in the filename-mapping file where you provide an empty value for the ArchiveDescription, the original value for ArchiveDescription from the S3 Glacier vault inventory file will be used as the S3 object key name.