awsdocs / aws-snowball-developer-guide

The open source version of the AWS Snowball Developer Guide. You can submit feedback & requests for changes by submitting issues in this repo.

NOTICE

This repository is archived, read-only, and no longer updated. For more information, read the announcement on the AWS News Blog.

You can find up-to-date AWS technical documentation on the AWS Documentation website, where you can also submit feedback and suggestions for improvement.

aws-snowball-developer-guide's Issues

Batching Small Files - steps need edit, esp. for Windows

https://docs.aws.amazon.com/snowball/latest/developer-guide/batching-small-files.html

Someone should review and edit steps 3-5

The windows instruction is not so clear. The example shows a 7zip example, but 7zip does not come installed in windows. The comment then refers to 'tar' but tar is not use in the sample command.

Step #5 is redundant and should be removed together with the note: "If there are non-archive files, don't use this command."

Clarification needed on the SnowballsFAQ

Hi Team,

Just want to confirm about the usable capacity of Snowball. Is the usable capacity the total data that you can actually store on the snowball device?

It seems to be contradicting itself when we factor in the usable capacity on the example in the above FAQ which says that you can move/store 150 TB of data with two 80 TB of Snowball devices. Considering that you only have 72 TB of usable capacity out of the 80 TB device ( 72 x 2 = 144 ), then this calculation seems to be wrong.

Please see the below screenshot for reference:
https://aws.amazon.com/snowball/faqs/#When_to_use_Snowball

Thank you in advance for your support on this matter.

Cheers,
Jon Bonso

unlock-device command should specify need for absolute path

I think this is really a bug with the snowballEdge client, but I'm not sure where to submit a bug report for it.

When using the unlock-device tool, the --manifest-file argument requires an absolute path to the manifest file location.
Adding a starting slash to the example path might hint at this better.

aws-snowball-developer-guide/doc_source/unlockdevice.md

Line 24 in fef4cfe

snowballEdge unlock-device --endpoint https://ip address --manifest-file Path/to/manifest/file --unlock-code

Preferred would be for explicit documentation of this behavior.

There are examples that the --manifest-file argument requires an absolute path, e.g.

aws-snowball-developer-guide/doc_source/unlockdevice.md

Line 31 in fef4cfe

snowballEdge unlock-device --endpoint https://192.0.2.0 --manifest-file /Downloads/JID2EXAMPLE-0c40-49a7-9f53-916aEXAMPLE81-manifest.bin --unlock-code 12345-abcde-12345-ABCDE-12345

Although these are not explicit and use non-canonical root folders like /Downloads

Clarification needed on the Snowball's Usable capacity in the FAQ

Hi Team,

Just want to confirm about the usable capacity of Snowball. Is the usable capacity the total data that you can actually store on the snowball device?

It seems to be contradicting itself when we factor in the usable capacity on the example in the above FAQ which says that you can move/store 150 TB of data with two 80 TB of Snowball devices. Considering that you only have 72 TB of usable capacity out of the 80 TB device ( 72 x 2 = 144 ), then this calculation seems to be wrong.

Please see the below screenshot for reference:
https://aws.amazon.com/snowball/faqs/#When_to_use_Snowball

Thank you in advance for your support on this matter.

Cheers,
Jon Bonso