Amazon Glacier Integration
#

Amazon Glacier is a cloud-based storage service designed for long-term data archiving and backup. It offers secure, durable, and low-cost storage for infrequently accessed data. For more information, visit: Amazon Glacier Link.

---

⚠️ Important: Dependency jar files must be downloaded and placed in your CrushFTP Install Folder/plugins/ lib. ⚠️ Restart is required to load the new Glacier dependency jar. Download Link

---

⚠️ Proxy Configuration: If your server accesses the internet through a proxy, make sure that the required Glacier domains are whitelisted.

---

The URL should look like this (replace the placeholders with your actual values):

glacier://{ACCESS_KEY_ID}:{SECRET_KEY_ID}@glacier.{REGION}.amazonaws.com/

Make sure to insert your Access Key, Secret key, and AWS region to form a valid connection URL for Glacier.



Select the appropriate region from the Server dropdown menu. The default region is us-east-1.
Enter the Vault Name in the corresponding field. If you leave it empty, the system will automatically list all available Vaults in the selected region. Note that uploads are only allowed inside a Vault folder.
CrushFTP uses a special glacier folder to simulate the folder structure. Files uploaded here are represented as XML pointers referencing the actual archive in Glacier. Each archive includes a description in this format:

<m><v>4</v><p>[Base64 encoded path]</p><lm>[the current date]</lm></m>

You can turn off the XML reference storage by enabling the Delete local representation after upload option.
When this is checked, the XML pointer file will be automatically deleted one second after the upload, leaving only the archived data in Glacier.

Glacier task#

If you already have archives in Glacier that were ⚠️ not uploaded through CrushFTP, you can use this task to rebuild the simulated folder and file structure (XML Pointers) that CrushFTP uses.
This process happens in two steps: first, it creates an Amazon Glacier Inventory retrieval job. Once this job is completed (typically in 3–5 hours), it downloads the inventory and uses it to generate CrushFTP’s simulated folder structure and file references.
For more details, see: Amazon Valult Inventory Link



⚠️ Note: The CrushTask must be run at least twice:

The first run: It creates the Amazon inventory job, and the job ID returned by Amazon will be stored in the glacier_info.XML file located in the Cache folder.
By default, this Cache folder points to the CrushFTP job folder, which can be found or customized in the task settings. This file is used later to track and complete the inventory retrieval process.

<?xml version="1.0" encoding="UTF-8"?>
<GlacierTask type="properties">
        <job_id>Amazon job id</job_id>
</GlacierTask>

The second run: It checks the status of the Amazon job and downloads the inventory once the job is finished. If the glacier_info.XML file exists, the task uses the stored Amazon job ID to check the current status of the job.
You can set up an Email task after the Glacier task to notify the job result, using the Amazon job status variable.
Possible values for the job status are: In progress, Failed, or Succeeded.

{glacier_job_satus}

Once the Amazon job status is Succeeded, the task will download the Glacier Vault Inventory and use it to create CrushFTP’s simulated glacier folder and file structure. These files act as XML pointers referencing your archived data in Glacier.
Each archive entry will include a description in the following format:

<m><v>...</v><p>[Base64 encoded path]</p> ....</m>

This structure allows CrushFTP to represent your Glacier archives in a way that mimics a traditional folder and file system.

⚠️ Note: If your Glacier archive descriptions do not follow the required format, CrushFTP will still create the XML pointers, but it will use the archive description as the file name instead of placing the file in a simulated folder structure.
This means the files will appear flat (without folders), named directly after the description stored with each archive.