Snapshots to your own S3 bucket

OpenSearch clusters can now snapshot to an S3 bucket you control, on AWS or any S3-compatible store such as MinIO. Authentication is an IAM role or static keys.

Why into your bucket and not ours

Clusters here are backed up already. That protects you from a cluster problem. It does not protect you from us.

A snapshot repository you own is a copy of your indices sitting somewhere we have no control over, in the standard OpenSearch snapshot format, restorable into any OpenSearch cluster including one that has nothing to do with ClusterNest. It is the difference between a backup and an exit.

What you can do with it

• Schedule snapshots of chosen indices into your own bucket.
• Restore after an accidental delete, into the same cluster or a different one.
• Point at AWS S3 or an S3-compatible store, including one you run yourself.

Configuring it

An IAM role, which is the one to reach for on AWS because there is no long-lived secret to rotate or leak:

resource "clusternest_opensearch" "logs" {
  name            = "logs"
  tier            = "standard"
  organization_id = 1

  repo_config = {
    enable_iam_role = true
  }
}

The cluster gets its own role ARN back, which is what you trust in the bucket policy on your side.

Static access keys, for an S3-compatible store that has no IAM:

resource "clusternest_opensearch" "logs" {
  name            = "logs"
  tier            = "standard"
  organization_id = 1

  repo_config = {
    enable_access_keys = true
    access_key_id      = var.snapshot_access_key_id
    secret_access_key  = var.snapshot_secret_access_key
  }
}

The two are alternatives, so set one or the other. The setup guide walks through both, and the upstream snapshot repository documentation covers the API if you would rather drive it directly.

Help configuring it: hello@clusternest.com.