---
title: "Backing Up Elastic Cloud Snapshots to Wasabi"
slug: "backing-up-elastic-cloud-snapshots-to-wasabi"
updated: 2026-10-24T20:47:01Z
published: 2026-10-24T20:47:01Z
canonical: "docs.wasabi.com/backing-up-elastic-cloud-snapshots-to-wasabi"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.wasabi.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Backing Up Elastic Cloud Snapshots to Wasabi

This solution was tested with Elastic Cloud version 8.15.1 deployed on Linux, although the operating system details are hidden from users.

## Requirements

- Active Wasabi Cloud Storage account
- Wasabi bucket without Object Lock or Versioning
- Wasabi access keys
- Active Elastic Cloud subscription
- Access to the Wasabi console and Elastic Cloud console

## Store Wasabi Access Keys in Elastic Cloud

In the Elastic Cloud console, navigate to your deployment and select Security. The deployment used in the example below is labeled My deployment. It is recommended to use a sub-user’s Wasabi keys instead of the root user and assign the sub-user programmatic-only access, not console access. See [Creating a User Account and Access Key](https://docs.wasabi.com/docs/en/creating-a-user-account-and-access-key) for details.

![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/image-1726667295504.png)

Scroll down to the Elastic keystore, click **Add settings**.

![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/image-1726667523652.png)

Under Setting name, enter the following

s3.client.default.access_key

For the Secret, enter your Wasabi access key. Click **Save**.

![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/image-1726668484164.png)

Click **Add setting**.

Under Setting name, enter the following:

s3.client.default.secret_key

For the Secret, enter your Wasabi secret key. Click **Save**.

**If you need to store data in multiple Wasabi repositories, see** [**Appendix A**](/v1/docs/draft-backing-up-elastic-cloud-snapshots-to-wasabi#appendix-a-multiple-wasabi-repositories) **after completing all the steps below.**

![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/image-1726668613438.png)

The access and secret key settings will now appear under Security keys.

![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/image-1726668708906.png)

## Create a Snapshot Wasabi Repository

Navigate to the home screen on the Elastic Cloud console.

![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/image-1726669294534.png)Select the menu (3 horizontal bars at the top left of the screen). Under **Management,** click **Dev Tools**.

![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/image-1726669464855.png)

Under the **Console** section, copy and paste the following JSON document at the bottom of the document. Replace "mt-elastic-cloud-repository" with the name of your Wasabi bucket, and use the domain name for the Wasabi region your bucket is located in for the endpoint.

This configuration example discusses the use of Wasabi's us-east-1 storage region. To use other Wasabi storage regions, use the appropriate Wasabi service domain name, as described in >[**Service URLs for Wasabi's Storage Regions**](https://docs.wasabi.com/v1/docs/what-are-the-service-urls-for-wasabis-different-storage-regions).

```json
PUT _snapshot/wasabi_repository
{
  "type": "s3",
  "settings": {
    "bucket": "mt-elastic-cloud-repository",
    "endpoint": "s3.us-east-1.wasabisys.com"
  }
}
```

Highlight the pasted text, then press the play triangle icon to send the request.

![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/image-1726670003666.png)

Verify that **acknowledged: true** is displayed in the results section.

![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/image-1726670300907.png)

Navigate to your deployment in the Elastic Cloud console, then click **Snapshots** under **Elasticsearch**. Click **Snapshot and Restore**.

![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/image-1726669095343.png)

Click on **Repositories** and then on **wasabi_repository**.

![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/image-1726670521874.png)

Click **Verify Repository**.

![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/image-1726670614756.png)

Ensure the Verification status shows **Connected**. Click **Close**.

![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/image-1726670894518.png)

## Create a Policy to Backup Snapshots to Wasabi

Click **Policies** and **Create Policy**.

![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/image-1726671140121.png)

Enter a name for the policy, a Snapshot name, Frequency, and Time that meet your backup requirements. In the example below, the following was used for the Snapshot name.

```plaintext
<daily-snap-{now/d}>
```

Select **wasabi_repository** from the drop-down **Repository** menu.

![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/image-1726671434736.png)

Click **Next**.

![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/image-1726671808475.png)

Select the appropriate options for your organization and click **Next**.

![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/image-1726671906956.png)

Enter the appropriate Snapshot retention options. Click **Next**.

![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/image-1726672058819.png)

Click **Create Policy**.

![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/image-1726672163884.png)

Click **Manage policy** and **Run now**.

![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/image-1726672332384.png)

Click **Run policy**.

![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/image-1726672478062.png)

After the policy runs, a new snapshot will appear.

![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/image-1726672657956.png)

Verify the snapshot data appears in your Wasabi bucket using the Wasabi [Console](https://console.wasabisys.com).

![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/image-1726672912550.png)

## Appendix A - Multiple Wasabi Repositories

If you need multiple Wasabi Repositories, proceed to this appendix after completing the steps above.

Add your Wasabi access and secret keys with the new client name. Repeat the [Store Wasabi Access Keys in Elastic Cloud](/v1/docs/draft-backing-up-elastic-cloud-snapshots-to-wasabi#store-wasabi-access-keys-in-elastic-cloud) section above, except with the following modifications:

s3.client.<client_name>.access_key s3.client.<client_name>.secret_key

For example, if you have a client named demo, use the following.

s3.client.demo.access_key s3.client.demo.secret_key

Next, repeat the "Create a Snapshot Wasabi Repository" section above using the following JSON document. Change the bucket name, endpoint to match your bucket’s location, and the client name to match the name of your client. You can use wasabi_new_repo as your repository name, or give it your own name.

```json
PUT _snapshot/wasabi_new_repo
{
  "type": "s3",
  "settings": {
    "bucket": "mt-elastic-cloud-repository",
    "endpoint": "s3.us-east-1.wasabisys.com",
    "client": "demo"
  }
}
```

Continue with the [Create a Snapshot Wasabi Repository](/v1/docs/backing-up-elastic-cloud-snapshots-to-wasabi#create-a-snapshot-wasabi-repository) and [Create a Policy to Backup Snapshots to Wasabi](/v1/docs/backing-up-elastic-cloud-snapshots-to-wasabi#create-a-policy-to-backup-snapshots-to-wasabi) sections above using the new repository name.