This page describes how to migrate from Amazon Simple Storage Service (Amazon S3) to Google Cloud Storage for users sending requests using an API. If you are not currently using Amazon S3 and you want to send requests using the Google Cloud Storage API, then start here: XML API Overview .
If you are new to Google Cloud Storage and will not be using the API directly, consider using the Google Developers Console . The Google Developers Console provides a graphical interface to Google Cloud Storage that enables you to accomplish many of your storage tasks using just a browser.
Overview of migration
If you are an Amazon S3 user, you can easily migrate your applications that use Amazon S3 to use Google Cloud Storage. You have two migration options:
- Simple Migration
-
This is this easiest way to get started with Google Cloud Storage if you are coming from Amazon S3 because it requires just a few simple changes to the tools and libraries you currently use with Amazon S3. For more information, see Simple Migration .
While a simple migration allows you to get going quickly with Google Cloud Storage, it does not allow you to use all the features of Google Cloud Storage. To take full advantage of Google Cloud Storage, follow the steps for a full migration.
- Full Migration
- A full migration from Amazon S3 to Google Cloud Storage requires a few extra steps than a simple migration, but the benefit is that you can use all the features of Google Cloud Storage, including support for service accounts, multiple projects, and OAuth 2.0 for authentication. For more information, see Full Migration .
Simple migration
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.
Setting a default project
To use the Google Cloud Storage in a simple migration scenario, you must choose a default project. When you choose a default project, you are telling Google Cloud Storage the project to use for operations like GET service or PUT bucket.
To set a default project:
-
Go to the Google Developers Console .
-
Click the name of the project you would like to set as your default project.
-
In the left sidebar, expand the STORAGE section, click CLOUD STORAGE , and then click Project dashboard .
This opens a new browser window that displays additional storage access configuration.
-
In the left sidebar of the dashboard, ensure that the project selector displays the project you want as the default.
-
In the left sidebar of the dashboard, click Google Cloud Storage , and then click Storage Access .