Amazon S3 file manager for Android handsets.
5 posts • Page 1 of 1
I have been using S3Anywhere 1.8 successfully for a few months and just bought S3AnywherePro 1.9 from google market so that I can sync. Unfortunately I get the "request signature does not match" error when I try to connect with the Pro version (but not with the free version). I've tried setting the connection credentials (KeyID and SecretKey) in the Pro version three different ways:
(1) Importing from free version.
(2) Copying and pasting from the (working) credentials in the free version.
(3) Typing them in manually (yikes!).
As near as I can see, the free and Pro credentials are identical.
Other possibly relevant information:
(1) Both versions complain that my bucket name might not be up to DNS standards (but it works fine on the free version).
(2) I had similar problems when I originally entered the credentials in the free version several months ago. I tried entering them many ways, but it finally worked (I don't recall how).
(3) Coby Kyros MID 7024 tablet running Android 2.2.
Thanks for any suggestions. I am really anxious to get the Pro version working on my tablet.
You get a warning about DNS? That's it, you have a character that makes bucket location fail.
For Free version, S3Anwyhere uses http://s3.amazonaws.com/your_bucket (because US location support only).
For Pro version, S3Anwyhere uses http://your_bucket.s3.amazonaws.com
Can you rename your bucket? The DNS constrains of AWS are detailed at:
http://docs.amazonwebservices.com/Amazo ... tions.html
Thanks, this seems to have fixed it. It's not possible to rename a bucket, but I already had another one that used only lowercase letters (and a "-"). For some reason I thought there was a problem with the dash, so I made a new bucket with no dash but with camelCase. So it was complaining about the upper case letter. I went back to the original bucket that was all lowercase and it worked fine. Thanks for the help! -- Bruce
It's silly that a free version can do what the paid version cannot. I've many Gigs of data online and, as buckets can't be renamed, fixing this would be difficult.
How about fixing this in the pro version?
Cant' you create a new bucket and just move them to his new bucket? S3 allows server-to-server objects moving. Using non DNS compliant bucket name could cause further issues later, I think you should apply S3 rules about naming.