Closed GoogleCodeExporter closed 8 years ago
It seems that that would be an entirely different project. Is Google Storage
and Amazon S3 100% compatible with respect to their API?
Original comment by dmoore4...@gmail.com
on 31 Mar 2011 at 9:25
Yes, I believe they are; Google's service will even accept x-amzn headers and
turn them into x-goog headers. I took the official AWS SDK for Java, modified
the endpoint URLs, and was able to access Google Storage without any further
changes. I think it will be the same thing for S3FS.
Original comment by apetresc
on 31 Mar 2011 at 9:30
Then try using the url option to point to google's server
url (default="http://s3.amazonaws.com")
e.g.
url=http://s3.google.com (or whatever is the correct URL for google's server)
...it might just work
Original comment by dmoore4...@gmail.com
on 31 Mar 2011 at 9:37
Original comment by dmoore4...@gmail.com
on 31 Mar 2011 at 9:56
Please share the results of your experiment. Thank you.
Original comment by dmoore4...@gmail.com
on 7 Apr 2011 at 2:33
No engagement from the original submitter in a reasonable amount of time.
Closing this issue.
Original comment by dmoore4...@gmail.com
on 21 Apr 2011 at 12:34
This does work!
Use:
s3fs name-of-your-bucket /mnt/google_storage_mount_point/ -o
url=http://commondatastorage.googleapis.com
TIP: You need to enable legacy mode on the google APIs console to get your
access/secret keys.
Original comment by drab...@gmail.com
on 26 Oct 2011 at 11:04
One more note: You can copy files and folders in and out of the mount point,
but listing contents (ls -la) always reveals an empty directory. However, if
you go to the storage sandbox (https://sandbox.google.com/storage/) you can see
all the files. That would be a nice bug to fix, as the google storage seems
otherwise quite a bit faster.
Original comment by drab...@gmail.com
on 26 Oct 2011 at 11:38
[deleted comment]
I tried this as of today Dec 8, the bug is still there? is it a bug? or just
maybe some permission/access?
Original comment by eglac...@gmail.com
on 9 Dec 2012 at 3:28
Original issue reported on code.google.com by
ctass...@gmail.com
on 27 Mar 2011 at 4:12