In a simple migration from Amazon S3 to Google Cloud Storage, you can use your existing tools and libraries for generating authenticated REST requests to Amazon S3, to also send authenticated requests to Google Cloud Storage. The changes you need to make to your existing tools and libraries are described in this section.
To get set up for a simple migration do the following:
•Set a default Google project.
•Get a developer key.
•In your existing tools or libraries, make the following changes: ◦Change the request endpoint to use the Google Cloud Storage request endpoint.
◦Replace the Amazon Web Services (AWS) access and secret key with the corresponding Google Cloud Storage access key and secret key (collectively called your Google developer key).
That’s it! At this point you can start using your existing tools and libraries to send keyed-hash message authentication code (HMAC) requests to Google Cloud Storage.
When you use the Google Cloud Storage XML API in a simple migration scenario, specifying the AWS signature identifier in the Authorization header lets Google Cloud Storage know to expect x-amz-* headers and Amazon S3 ACL XML syntax in your request.
A simple migration from Amazon S3 is an easy and quick way to get started using Google Cloud Storage, with a minimal investment in time and changes to your existing code. After you have some experience with a simple migration, you can fully transition to Google Cloud Storage to take advantage of all its features. For more information, see Full Migration.
What you would have to do is implement an access.gdrive plugin, by copying the existings ones (typically dropbox one and s3 one), and reimplementing the correct “StreamWrapper” using the google storage php SDK.
Frankly, if you’re not a php developer, this is a hard-level stuff to do.
Charles, Pydio author - doing my best to help !
If you like the software or want to say thanks, pay by a tweet, mention #pydio or follow us