How do I use the restore tiers in the Amazon S3 console to restore archived objects from Amazon S3 Glacier storage class?
Last updated: 2021-03-11
How do I use the restore tiers in the Amazon Simple Storage Service (Amazon S3) console to restore objects from Amazon S3 Glacier Storage Class?
Note: The information in this article doesn't apply to S3 Glacier Deep Archive.
If you have archived Amazon S3 objects to S3 Glacier Storage Class using a lifecycle rule, you can choose from three options to restore them: expedited retrieval, standard retrieval, and bulk retrieval. Follow these steps to restore an archived object using the Amazon S3 console, and choose a restore tier that meets your needs:
1. Open the Amazon S3 console, and choose the Amazon S3 bucket that stores the archived objects that you want to restore.
2. Select the archived object, and choose Actions.
3. Select Initiate restore, and specify the number of days you want the restored file to be accessible for.
4. Select a Retrieval option—Bulk, Standard, or Expedited—and choose Restore.
After the restoration is complete, you can download the restored object from the Amazon S3 console. Depending on the retrieval option selected, the restore completes in:
- 1-5 minutes for expedited retrievals
- 3-5 hours for standard retrievals
- 5-12 hours for bulk retrievals
To confirm that your file is restored, perform the following:
1. Choose the Amazon S3 bucket that contains the file.
2. Select the check box next to the file name to view the file details. The Restoration expiry date verifies that the file is restored. This expiration date indicates when Amazon S3 removes the restored copy of your file.
3. Choose Download to download the object as a file to your local client.
4. (Optional) To permanently restore an S3 object, change the object's storage class using the AWS Command Line Interface (AWS CLI). For more information, see How can I restore an S3 object from the Amazon S3 Glacier storage class using the AWS CLI?
Note: If you receive errors when running AWS CLI commands, make sure that you’re using the most recent AWS CLI version.