An archived file can still appear in your S3 bucket while its contents are unavailable to open. That is expected for S3 Glacier Flexible Retrieval and S3 Glacier Deep Archive: you must request a restore and wait before reading the object. A restore is a retrieval workflow, not a way to change the object permanently to a warmer storage class.
Before a colleague needs an old contract or media master urgently, decide which files may be restored, who can request it, how quickly they need it, and who pays the AWS retrieval bill. The steps below cover one object first, then the option for a larger set.
Check the storage class before requesting a restore
Look at the object’s storage class and restore status. S3 Glacier Instant Retrieval is available through a normal GET request and does not need a restore. S3 Glacier Flexible Retrieval and S3 Glacier Deep Archive require one. The Archive Access and Deep Archive Access tiers of S3 Intelligent-Tiering also require a restore request, but their restored objects move back to the Frequent Access tier instead of using a temporary copy with an expiration date.
This distinction matters when planning the next step. If the object is in Instant Retrieval, investigate permissions or the viewing tool before starting a restore workflow. If it is in Flexible Retrieval or Deep Archive, plan for a wait and a limited window to use the restored copy.
Choose a retrieval tier for the deadline
Bulk is intended for lower-cost retrieval when you can wait. Standard is the middle choice. Expedited is available for S3 Glacier Flexible Retrieval, but not for S3 Glacier Deep Archive, and it costs more. AWS publishes typical completion times rather than a guarantee for every object; size, storage class and the retrieval tier all matter.
For Flexible Retrieval or Deep Archive, choose how many days the temporary restored copy should remain readable. A longer window can make handoff easier, but AWS charges for the temporary copy as well as the archived object. Check current AWS pricing and the selected tier before confirming an expensive or large restore.
Request the restore for one object
In the S3 console, select the object, choose Actions, then Initiate restore. Pick the retrieval tier and, for Flexible Retrieval or Deep Archive, the number of days the restored copy should remain available. An application can submit the same request through the S3 API or AWS CLI using an authorized identity.
Submitting the request does not make the file readable immediately. If your workflow needs to notify someone, record which object and version was requested, the chosen tier and retention, and who approved the cost. Do not repeatedly submit a new restore just because the first one is still running.
Watch the status, then use the copy before it expires
The object details page shows whether restoration is in progress or complete. The S3 HeadObject response also reports restore state and, for a completed temporary restore, the expiry date. When the restore completes, authorized users can read the object during that window. The original remains in its archived storage class.
If you need the file available permanently, make a separate copy in a storage class suited to regular access after restoration. AWS says that copying a restored Glacier Flexible Retrieval or Deep Archive object to a new class requires the CLI, an SDK or the API; that copy operation is not supported in the S3 console. Plan the copy before the temporary restoration expires.
Use Batch Operations when many objects need retrieval
For a collection of archived objects, S3 Batch Operations can submit restore requests from a manifest. It needs its own permissions and job review. Separate jobs are required for Glacier storage-class objects and S3 Intelligent-Tiering archive-tier objects. A single-object workflow is easier to review when the request is only for one contract or media file.
Bring the workflow to the people who need the file
BucketDesk Business lets an operator request a manual restore for one Glacier or Deep Archive object from the file workspace, choose a retrieval tier and how long the copy stays readable. AWS retrieval charges remain in the customer’s account. This is a per-object workflow; use AWS Batch Operations for bulk restores.
First confirm the storage class. For Glacier Flexible Retrieval or Deep Archive, choose the retrieval tier and temporary access window, request the restore, and wait for completion before opening the file. Use Batch Operations for large sets, and make a separate warm copy if access must outlast the restore window.