Skip to main content

Service forking

Fork your Aiven service to make a copy of the service, for example to create a snapshot to analyze an issue.

Other typical use cases include creating a development copy of your production environment, upgrade testing, or creating an instance in a different cloud/geographical location/under a different plan.

When you fork a service, the following items are copied into the new service:

  • Configurations
  • Databases
  • Service users
  • Connection pools

Forks are independent and do not increase the load on the original service. The data is restored from the latest backup stored separately from the service.


The service integrations are not copied over to the forked version, and need to be re-established for each new copy.

You can fork the following Aiven services:

  • PostgreSQL®

  • MySQL

  • Caching

  • Apache Cassandra® (Limitation: you cannot fork to a lower amount of nodes)

  • Elasticsearch

  • OpenSearch®


    When you fork an Aiven for OpenSearch® service, any Single Sign-On (SSO) methods configured at the service level, such as SAML, must be explicitly reconfigured for the forked service. SSO configurations are linked to specific URLs and endpoints, which change during forking. Failing to reconfigure SSO methods for the forked service can lead to authentication problems and potentially disrupt user access.

  • M3DB

  • Grafana®

Fork a service

When forking a service with Point in Time Recovery (PITR), you can choose to fork from the latest transaction or select a specific point in the past to fork from. Fork your Aiven service to make a copy of the service.


You can only fork services that have at least one backup.

  1. Log in to Aiven Console.
  2. In your project, click Services and click the service to fork.
  3. Click Backups and click Fork & restore.
  4. In the New Database Fork window, set the details for the new service.
  5. Click Create fork.

Apply any integrations required by the fork.

Rename a service

A service cannot be renamed after creation. Instead, use a fork:

  1. Stop service writes on the service to rename.
  2. Fork the service under a different name.
  3. Point clients to the new service.
  4. Delete the original service when you are ready.

Elasticsearch is a trademark of Elasticsearch B.V., registered in the U.S. and in other countries.