Snapshotting to Google Cloud Storage (GCS)

Snapshots to GCS are supported using an advanced repository configuration and service account credentials that can administer your GCS bucket.

Set up your service account credentials

edit

You’ll need to have an existing Google Cloud account and have the appropriate permissions to generate credentials:

Create service account credentials in your Google Cloud project where Elastic Cloud Enterprise is running.

The service account should be granted the role of storage.admin so that Elasticsearch clusters can read, write, and list the bucket objects.
Save the service account key in JSON file format. You are going to use it later to configure your Elasticsearch deployment for snapshotting.

Add the GCS repository

edit

Add your Google Cloud Storage bucket as a repository to the platform:

Log into the Cloud UI.
Go to Platform > Repositories and add the following snapshot repository configuration under the advanced mode:

Repository GCS (check: supported settings)
```
{
  "type": "gcs",
  "settings": {
    "bucket": "acme-snapshot-repo",
    "bucket": "acme-snapshots"
  }
}
```

Snapshots are stored in the bucket you provide. Use the repository name you define here to configure your Elasticsearch clusters for snapshotting to this repository.

Configure your deployment for GCS snapshots

edit

To save deployment snapshots to the custom GCS repository:

Add a secure setting named gcs.client.acme-snapshots.credentials_file as a JSON block. Make sure that the client name is the same one you provided when configuring the snapshot repository.

The contents within credentials_file must be the exact contents of your GCS credentials file.
Configure your deployment to snapshot to the GCS repository.

After you enable snapshots, snapshotting will begin within 30 minutes (the default snapshot interval).

« Manage snapshot repositories Snapshotting to Azure Storage »