Step 2: Launch the transfer workflow
Important
Avoid starting multiple transfers simultaneously. Multiple transfers can exceed S3 Glacier quotas and induce throttling.
When you transfer multiple vaults, initiate transfers sequentially by starting a new transfer only after the previous one completes.
-
Sign in to the Systems Manager console
. -
Under Shared Resources, select Documents.
-
On the Documents page, select Owned by me, and choose the document called
Launch-Data-Retrieval-for-Glacier-S3-$
.<NAME_OF_STACK>
-
Choose Execute Automation.
(Optional) Download the vault inventory file
If you want to download the vault inventory file as part of this migration, follow these steps.
-
Sign in to the Systems Manager console
. -
Under Shared Resources, select Documents.
-
On the Documents page, select Owned by me, and choose the document called
Launch-Data-Retrieval-for-Glacier-S3-$
.<NAME_OF_STACK>
-
Choose Execute Automation.
-
Enter the following under Input Parameters on the Execute Automation Runbook page.
Note
To enable the data transfer to a bucket in a different region from the S3 Glacier vault, you must manually adjust the automation document's content by setting the InputPayload parameter
allow_cross_region_data_transfer
to true. By default, the solution restricts cross-region transfers to avoid potential costs.Parameter Value Notes AcknowledgeAdditionalCostForCrossRegionTransfer NO
Select
YES
only if you are aware of the excessive additional cost when selecting a destination bucket in a different region than the S3 Glacier vault. See Amazon S3 Glacier data transfer pricing. ProvidedInventory
<Requires input>
Input with two options [
YES,NO
] indicate if the inventory is provided.VaultName
<Requires input>
Enter the name of your S3 Glacier vault. WorkflowRun
<Requires input>
Input to specify the workflow identifier of the workflow that needs to be resumed. Note
Input to specify the workflow identifier of the workflow that needs to be resumed.
Description
<Optional input> Provide an extended description for this migration. NamingOverrideFile
<Optional input> Provide a presigned URL of the NamingOverride file and the bucket that is storing the file if you want to customize S3 object key names. S3StorageClass
<Requires input>
Select the S3 storage class for the migrated archives. See Amazon S3 pricing . -
Choose Execute.
-
It takes approximately less than 1 minute to execute the document and launch the transfer. To confirm that the transfer process started successfully, refer to the runScript step status under the Executed Steps section.
Note
To monitor the progress of the transfer after launching the workflow, please refer to the Solution’s Cloudwatch dashboard. Please note that it might take 5-12 hours before the dashboard Workflow Run ID dropdown menu entries get updated with the new entry after launching the transfer.
(Optional) Provide the vault inventory file
If you want to provide the vault inventory file, follow these steps.
-
Sign in to the CloudFormation console
. -
On the Stacks page, select this solution's installation stack.
-
Choose the Output tab and find the inventory bucket name.
-
-
Sign in to the Amazon S3 console
and choose the inventory bucket from step 1b. -
Choose Create folder. Enter the
workflow_run
value from the WorkflowRun parameter input. For more information about creating and using folders, see Organizing objects in the Amazon S3 console by using folders in the Amazon Simple Storage Service User Guide. -
Create a subfolder called
original_inventory
in this new folder. -
Copy the vault inventory file into this folder. For more information, see Downloading a Vault Inventory in Amazon S3 Glacier in the Amazon S3 Glacier Developer Guide.
-
Rename the vault inventory file to
inventory.csv
.
-
-
Sign in to the Systems Manager console
. -
Under Shared Resources, select Documents.
-
On the Documents page, select Owned by me, and choose the document called
Launch-Data-Retrieval-for-Glacier-S3-$
.<NAME_OF_STACK>
-
Choose Execute Automation.
-
Enter the following under Input Parameters on the Execute Automation Runbook page.
Note
To enable the data transfer to a bucket in a different region from the S3 Glacier vault, you must manually adjust the automation document's content by setting the InputPayload parameter
allow_cross_region_data_transfer
to true. By default, the solution restricts cross-region transfers to avoid potential costs.Parameter Value Notes AcknowledgeAdditionalCostForCrossRegionTransfer NO
Select
YES
only if you are aware of the excessive additional cost when selecting a destination bucket in a different region than the S3 Glacier vault. See Amazon S3 Glacier data transfer pricing. ProvidedInventory
Yes
WorkflowRun
<Requires input>
Provide the name of your workflow run, which becomes the
workflow_run
value.Description
<Optional input> Provide an extended description for this migration. NamingOverrideFile
<Optional input> Provide a presigned URL of the NamingOverride file and the bucket that is storing the file if you want to customize S3 object key names. S3StorageClass
<Requires input>
Select the S3 storage class for the migrated archives. See Amazon S3 pricing . Choose Execute It takes approximately less than 1 minute to execute the document and launch the transfer. To confirm that the transfer process started successfully, refer to the runScript step status under the Executed Steps section.
Note
To monitor the progress of the transfer after launching the workflow, please refer to the Solution’s Cloudwatch dashboard. Please note that it might take 5-12 hours before the dashboard Workflow Run ID dropdown menu entries get updated with the new entry after launching the transfer.