glacier-upload | A simple python script to upload files to AWS Glacier vaults | AWS library

by tbumi Python Version: 2.1.1 License: GPL-3.0

X-Ray Key Features Code Snippets Community Discussions(2)Vulnerabilities Install Support

kandi X-RAY | glacier-upload Summary

glacier-upload is a Python library typically used in Cloud, AWS, Amazon S3 applications. glacier-upload has no bugs, it has no vulnerabilities, it has a Strong Copyleft License and it has low support. However glacier-upload build file is not available. You can install using 'pip install glacier-upload' or download it from GitHub, PyPI.

A simple python script to upload files to AWS Glacier vaults

Support

Quality

Security

License

Reuse

Support

glacier-upload has a low active ecosystem.

It has 115 star(s) with 36 fork(s). There are 3 watchers for this library.

There were 1 major release(s) in the last 6 months.

There are 0 open issues and 18 have been closed. On average issues are closed in 249 days. There are 6 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of glacier-upload is 2.1.1

Quality

glacier-upload has 0 bugs and 0 code smells.

Security

glacier-upload has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

glacier-upload code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

glacier-upload is licensed under the GPL-3.0 License. This license is Strong Copyleft.

Strong Copyleft licenses enforce sharing, and you can use them when creating open source projects.

Reuse

glacier-upload releases are available to install and integrate.

Deployable package is available in PyPI.

glacier-upload has no build file. You will be need to create the build yourself to build the component from source.

Installation instructions are not available. Examples and code snippets are available.

Top functions reviewed by kandi - BETA

kandi has reviewed glacier-upload and discovered the below as its top functions. This is intended to give you an instant insight into glacier-upload implemented functionality, and help decide if they suit your requirements.

Upload a file
Calculate the hash of a list of checksums
Calculate the hash of a tree
Gets the output of the given job
Retrieve the output of a job
List all uploads in a vault
List all multipart uploads in a vault
Lists the parts of a upload
List parts in a multipart upload
Create a delete archive command
Delete an archive
Returns the abort command
Aborts a multipart upload
Upload a piece of parts
Create a upload command

Get all kandi verified functions for this library.

glacier-upload Key Features

No Key Features are available at this moment for glacier-upload.

glacier-upload Examples and Code Snippets

No Code Snippets are available at this moment for glacier-upload.

Community Discussions

Trending Discussions on glacier-upload

upload_archive() operation in boto3 for glacier

Archive retrieval from AWS Glacier

QUESTION

upload_archive() operation in boto3 for glacier

Asked 2018-Jul-27 at 13:29

Does the upload_archive() operation in boto3 for glacier automatically use multi-part upload when the data to be uploaded is larger than 100MB?

I believe this is the case in boto2 (see @lenrok258's answer in Boto Glacier - Upload file larger than 4 GB using multipart upload)

I have tried different ways to view the source code for the upload_archive() operation in boto3 for glacier, but I haven't been able to find it using inspect or ipython. If anyone happens to know how to do this and is willing to share it would be much appreciated.

...

ANSWER

Answered 2018-Jul-27 at 13:29

Unlike boto2, boto3 does not automatically use multi-part upload.

From a comment from a member of the boto project on an issue on the boto3 Github:

... boto3 does not have the ability to automatically handle multipart uploads to Glacier. That would be a feature request. There are some features that exist in boto2 that have not been implemented in boto3.

You'll have to implement it yourself using the initiate_multipart_upload functionality.

Or, as another commenter on the issue suggests instead:

The optimal usage pattern for interacting with Glacier is generally to upload to S3 and use S3 lifecycle policies to transition the object to Glacier.

Source https://stackoverflow.com/questions/50972226

QUESTION

Archive retrieval from AWS Glacier

Asked 2017-Oct-26 at 13:07

I uploaded an archive to AWS glacier using boto3 using the code as described here: https://github.com/tbumi/glacier-upload/blob/develop/main.py

It returned me archive id which I didn't save at the time and i went through the AWS documentation and archive id is needed for archive retrieval.

As i understood from the boto3 documentation, You first need to create a job as follows:

...

ANSWER

Answered 2017-Oct-26 at 13:07

You can get all the IDs by running a vault inventory.

...you can use Initiate a Job (POST jobs) to initiate a new inventory retrieval for a vault. The inventory contains the archive IDs you use to delete archives using Delete Archive (DELETE archive) . http://boto3.readthedocs.io/en/latest/reference/services/glacier.html

So just use Client.initiate_job with Type set to inventory-retrieval, and you'll get your ID after the inventory finishes. http://boto3.readthedocs.io/en/latest/reference/services/glacier.html#Glacier.Client.initiate_job

Source https://stackoverflow.com/questions/46950884

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install glacier-upload

You can install using 'pip install glacier-upload' or download it from GitHub, PyPI.
You can use glacier-upload like any standard Python library. You will need to make sure that you have a development environment consisting of a Python distribution including header files, a compiler, pip, and git installed. Make sure that your pip, setuptools, and wheel are up to date. When using pip it is generally recommended to install packages in a virtual environment to avoid changes to the system.

Support

Contributions and/or bug fixes are welcome! Just fork, make a topic branch, format the code using black --line-length=80 and submit a PR. Don't forget to add your name in CONTRIBUTORS. A good place to start is the TODO file.

Find more information at: