When you restrore a whole HDD, it initiates a single data retrieval request (pricing is per GB) and then you pay for "data transfer out" per GB . For file-level restore, you will have a single data retrieval request for a whole HDD again but the download (data transfer out from Amazon S3 to Internet - per GB) occurs for selected files only.

That’s true... it takes 2-2,5h per 100GB with compression/encryption. Is your main use case a restore to Azure?

A quick update - I have to say that we got almost the same speed: 100GB - 1,5h. This is a continuous process, no timeouts or interruptions there.

Thanks for the details. I have submitted a change request for that. We are going to review the dialogs and wizards to fix tab ordering issues together.

Please send a screenshot of the UI where you experienced the issue. Thanks!

This is the same product. We specify them as “different” in order to show our customers that we support both Glacier and Amazon S3 and you can find it on our website with just one look.

The new test is coming, no speed results yet. Sorry.

A quick update so far: we were not able to reproduce your slowness, however, we made some changes and going to run a new test to get new results next week. It is coming to be v5.9.

Please check the instructions here: https://docs.aws.amazon.com/IAM/latest/UserGuide/id_users_change-permissions.html#by-direct-attach-policy how to add permissions to the user.

What permissions does that account have (check the AWS Management Console where you created it)? It seems you need to grant it "iam:*" permissions there.

Are you working under the master Amazon S3 account. The master account has full permissions for all actions. You can check what policies/permissions you have in the AWS Management Console where you generated the access/secret keys.

You can register your master Amazon S3 account in CloudBerry Explorer and configure any IAM user that you want.
If you need those IAM users be able to use IAM manager as well, you should grant them required permissions (i.e. "iam:*").
If you would like those IAM users be able to access certain buckets only, so you can grant them full access for those buckets and no need for "iam" permissions then.

great! I am happy to be helpful :wink:

Please double-check your configuration following the steps here:
https://www.cloudberrylab.com/blog/how-to-host-a-static-website-on-s3/

We will check what we can do for future versions. Thanks!

Please check what ACL is set for the index file: right-click on it and choose Access Control List. Attach the screenshot of it here. Thanks!

Thanks for the update! The provided steps are correct for now and it is the only workaround at the moment. We are going to rewrite the documentation to avoid confusion.
Please inform how the plan has been going.
Thanks!

I was sure you have been working with CloudBerry Explorer all the time :)
Let's start from scratch then - what would you like to configure and to do next with the users?

Could you please provide a screenshot that demonstrates the issue? Thanks!

If you are master account, you can use IAM Manager to create as many IAM users as you want with different permissions. There you can also generate access and secret keys for those IAM users and, finally, use IAM users access/secret keys for different purposes that you have.