Answers: <p>Yes, you can use the AWS SDK to store objects within google storage. </p>
  
  <p>From <a href="https://cloud.google.com/storage/docs/migrating#migration-simple" rel="noreferrer">Simple migration</a>:</p>
  
  <blockquote>
    <p>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.</p>
    
    <p>To get set up for a simple migration do the following:</p>
    
    <ul>
    <li>Set a <a href="https://cloud.google.com/storage/docs/migrating#defaultproj" rel="noreferrer">default Google project</a>.</li>
    <li>Get a <a href="https://cloud.google.com/storage/docs/migrating#keys" rel="noreferrer">developer key</a>.</li>
    <li>In your existing tools or libraries, make the following changes:
    
    <ul>
    <li>Change the request endpoint to use the <a href="https://cloud.google.com/storage/docs/request-endpoints" rel="noreferrer">Cloud Storage request endpoint</a>.</li>
    <li>Replace the Amazon Web Services (AWS) access and secret key with the corresponding Cloud Storage access key and secret key
    (collectively called your Google developer key).</li>
    </ul></li>
    </ul>
    
    <p>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.</p>
    
    <p>When you use the Cloud Storage XML API in a simple migration scenario,
    specifying the <code>AWS</code> signature identifier in the <code>Authorization</code>
    header lets Cloud Storage know to expect <code>x-amz-*</code> headers and Amazon
    S3 ACL XML syntax in your request.</p>
    
    <p><strong>Note:</strong> 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 <a href="https://cloud.google.com/storage/docs/migrating#migration-full" rel="noreferrer">Full Migration</a>.</p>
  </blockquote>
  
Answers: CC BY-SA 3.0
Answers: 2017-03-08T04:40:00.093Z
Answers: @pwynne: the downvotes were likely caused by your link-only answer - frowned upon, see http://meta.stackexchange.com/questions/8231/are-answers-that-just-contain-links-elsewhere-really-good-answers
Answers: Dan Cornilescu
Answers: CC BY-SA 3.0
Answers: 2017-03-01T18:42:53.040Z
Answers: so sneaky, Google :)
Answers: Assaf Lavie
Answers: CC BY-SA 3.0
Answers: 2017-03-01T16:05:29.910Z
Answers: 2017-03-08T04:35:24.560Z
Answers: 2017-03-08T04:35:24.560Z
Answers: pwynne
Answers: <p>Most of the AWS SDKs mentioned support constructing a custom endpoint, for example as described <a href="http://docs.aws.amazon.com/AWSJavaScriptSDK/latest/AWS/Endpoint.html" rel="noreferrer">here for Node.JS</a>.</p>
  
  <p>Setting the endpoint to <code>storage.googleapis.com</code> and using your GCP access credentials should enable you to operate the Google storage backend service "like S3".</p>
  
Answers: CC BY-SA 3.0
Answers: 2017-03-01T11:11:58.540Z
Answers: Is this just in theory, or does this actually work?
Answers: Evgeny Zislis
Answers: CC BY-SA 3.0
Answers: 2017-03-01T10:36:16.243Z
Answers: 2017-03-03T06:44:01.433Z
Answers: 2017-03-03T06:44:01.433Z
Answers: Michael Bravo
Body: <p>Google Storage claims they support <em>interoperability</em> in their solution with Amazon AWS S3 and Eucalyptus Systems APIs.</p>
  
  <p><sup>source: <a href="https://cloud.google.com/storage/docs/interoperability" rel="noreferrer">https://cloud.google.com/storage/docs/interoperability</a></sup></p>
  
  <p>Can the <code>aws-sdk</code> for Java, or Node.js, or Python, be used to store and retrieve objects with the Google Storage APIs?</p>
  
Tags: <amazon-s3><storage><google-cloud-storage>
Title: Can you use `aws-sdk` to store objects in Google Storage?
UserDisplayName: Evgeny Zislis
ThreadText: # Can you use `aws-sdk` to store objects in Google Storage?
  
  (Asked by: username_0 on 2017-03-01)
  
  Google Storage claims they support *interoperability* in their solution with Amazon AWS S3 and Eucalyptus Systems APIs.
  
  source: <https://cloud.google.com/storage/docs/interoperability>
  
  Can the `aws-sdk` for Java, or Node.js, or Python, be used to store and retrieve objects with the Google Storage APIs?
  
  **Tags:** amazon-s3, storage, google-cloud-storage
  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_1 on 2017-03-01. Score: 8
  
  Yes, you can use the AWS SDK to store objects within google storage.
  
  From [Simple migration](https://cloud.google.com/storage/docs/migrating#migration-simple):
  
  > 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](https://cloud.google.com/storage/docs/migrating#defaultproj).
  > * Get a [developer key](https://cloud.google.com/storage/docs/migrating#keys).
  > * In your existing tools or libraries, make the following changes:
  >   + Change the request endpoint to use the [Cloud Storage request endpoint](https://cloud.google.com/storage/docs/request-endpoints).
  >   + Replace the Amazon Web Services (AWS) access and secret key with the corresponding 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 Cloud Storage XML API in a simple migration scenario,
  > specifying the `AWS` signature identifier in the `Authorization`
  > header lets Cloud Storage know to expect `x-amz-*` headers and Amazon
  > S3 ACL XML syntax in your request.
  >
  > **Note:** 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](https://cloud.google.com/storage/docs/migrating#migration-full).
  
  > **Comments:**
  > **username_3**: so sneaky, Google :)  
  > **username_2**: @username_1: the downvotes were likely caused by your link-only answer - frowned upon, see http://meta.stackexchange.com/questions/8231/are-answers-that-just-contain-links-elsewhere-really-good-answers  
  
  ---
  
  ### Answer by username_4 on 2017-03-01. Score: 7
  
  Most of the AWS SDKs mentioned support constructing a custom endpoint, for example as described [here for Node.JS](http://docs.aws.amazon.com/AWSJavaScriptSDK/latest/AWS/Endpoint.html).
  
  Setting the endpoint to `storage.googleapis.com` and using your GCP access credentials should enable you to operate the Google storage backend service "like S3".
  
  > **Comments:**
  > **username_0**: Is this just in theory, or does this actually work?  
  
  ---
  
  