simpleamazonglacieruploader / sagu Goto Github PK

AWS Region ap-south-1 is not listed in server location drop down

Asia Pacific (Mumbai) ap-south-1 glacier.ap-south-1.amazonaws.com

http://docs.aws.amazon.com/general/latest/gr/rande.html#glacier_region

I just started using Amazon Glacier today to backup my files. I found out that you need to use the Glacier SDK to upload/download your files or use a third party client. So I google around for clients on MAC OSX 10.7 and found this SAGU. When I tried uploading a file to test if it is working, after a few seconds the dialog appeared saying upload was successful. But when I tried to check my archive in Glacier the vault was not updated. I provided the Access key, Secret Key, Server location Asia Pacific(Tokyo) and choose a vault. Please tell me what I did wrong.

I'm going to rebuild this soon with better OOP and a serializable user object. As of 7.4.3 SAGU saves access and secret key properties as plain text.

This may be a duplicate of #6 but is SAGU asked

This really was simple at one point. Now I need to make some documentation to help people understand what's going on in the backend.

We need pull requests to be automatically checked (tests, style, coverage, etc.)
See https://github.com/marketplace/category/continuous-integration

Hello,

The AWS zone for EU Frankfurt is missing. Are there any plans to introduce it soon?

Thanks for the app - looks nice.

Best regards,
Iancu

I'm parsing SAGU's Glacier.csv file and ran into a problem when some files we've been uploading have commas in them, which is offsetting columns in CSV. If SAGU could wrap values with double quotations, that would be fantastic. Note that you then have to ensure you properly escape any double quotation marks inside values like so: http://stackoverflow.com/a/17808731

Download attempts from regions other than us-east-1 fail with the following sns related error:

Status Code: 400, AWS Service: AmazonGlacier, AWS Request ID: NXEvJTGUcmgi_XBmOZmEfoDT7nXntp00pnS95iRTHYy0edQ, AWS Error Code: InvalidParameterValueException, AWS Error Message: SNS topics must be in the local AWS region: arn:aws:sns:us-east-1:724017355723:glacier-archive-transfer-1346022657201

Looks to me like the fix is to use a different ArchiveTransferManager constructor in AmazonDownloadRequest.java:

ArchiveTransferManager atm = new ArchiveTransferManager(client, sqs, sns);

See the bottom of the following thread:

https://forums.aws.amazon.com/thread.jspa?threadID=102702

(Love the project, and also would like to see the fork with maven support by haozhou, which builds fine and migrates over to eclipse as well.)

it is the new year and I am doing my backups but it seems that SAGU does not work with the new IAM infrastructure? Has anyone gotten it to work?

Would be nice to be able to encrypt stuff sent to Glacier in such a way that:

(a) We don't need to create an entire archive of a directory tree locally, just to encrypt locally, and
(b) We can decrypt it with any version of any software in the future (Java 10, .NET 6.5, Python on Mac/Linux, you know?) (so... standard PKI-type stuff that isn't subject to the vagaries of how any particular vendor (I'm looking at you, Microsoft) implements it..

Tried to start SimpleGlacierUploaderV0746.jar by double clicking it and the main window doesn't show anymore. The app itself seems to start though... Any idea on how to fix it?

The system setting to "allow all apps" is set.

It would be fine to have suite of "end-to-end integration" tests preventing regression.

Infrastructure for unit tests is done, but we miss support for UI tests and mocking of AWS lib/api.

Currently the drop-down is only populating with the first 10 vaults, I need to implement a loop to get all vaults on a server.

I believe this is because the upload file's path is being used as x-ams-archive-description, and the string isn't being properly sanitized. If this string is to be used, it should be URL encoded or ASCII-fied before being set.

It'd probably be better if you were prompting for a description and simply used the path as a default -- some people'd rather not include their full path for security reasons.

Currently it's unformatted JSON in .txt file

I have about 30GB of data which I need to upload to Glacier in 200MB zip files. When I try uploading these files in SAGU, I see a progress bar bouncing back and forth without any actual progress reporting, which is a little important when uploading such big files.

I'm getting reports that large file uploads are failing with InvalidSignatureException errors. There appear to be different file limit thresholds for each user, some people can upload files of several gigabytes in size, while others can't upload more than a few hundred megabytes.

I am suspecting that there is a problem inside of the AWS ArchiveTransferManager, but I need to review all of my client creation methods to make sure nothing is getting overlapped.

I just finished uploading around 180 files with SAGU in one go, on a Macbook Pro running OS X 10.10 (Yosemite).

The 'Uploaded' dialog box shown when the upload (of all files) is complete expands to fit the set of results. This meant it was ~180 lines high in my case, which expanded way down below the end of my screen. (The 'OK' button couldn't be reached.)

Ideally I think the dialog should have constrained dimensions (proportional to screen dimensions) and contain the results in a scrollable text area.

AWS only accepts unicode characters on upload, I need to add a function to clean non-unicode strings.

Just tried the client for the first time. I'd like to be able to back up an entire directory rather than a single file, if that's possible. Not sure I have room on my disk to create a zip file of the directory before backing it up. Java file-picker dialog apparently doesn't do directories.

On my Macbook Pro Retina this Java app triggers the machien to use its discrete GPU instead of the integrated one. This causes both the fans to go up and uses more battery.

Since the program can be on for hours at once (requesting inventories etc) this is a drawback. I've detected this with the following program (http://gfx.io). Its maker (@codykrieger https://github.com/codykrieger) is willing to help developers using the graphics part more efficiently.

Other Java programs such as Netbeans do not suffer from the issue

There's a lot of empty catch blocks in code and some with printStackTrace(). We need to handle these properly - log them and display to user if appropriate (use own Exception types to differentiate between these).

It would be fine to have some top-level catch block to display and log exceptions. Also ensure the application log file is created on start if doesn't exist.

I would like to change the log path. I use SAGU in Applications folder (OSX), but it saves all logs in the same path, so the 3 files logs are in apps folder. It would be better put them in another path (my user path, for instance).
Thanks.

Long-running uploads fail after several hours because the STS token authenticating the session expires (I'm going to run it again and try to get the specific error message for you).

Lot of code in SimpleGlacierUploader takes care about logging. Replace it e.g. with slf4j and logback and various appenders.

There are now many more AWS server locations (regions) than the five you list in your dropdown. I can't use SAGU with Asia Pacific (Sydney), for example.

Failures should also be logged for review, aside from just success, to aid in debugging.

Homepage link no longer returns dns so no access to binarys.
Any plan to bring these back up?