Skip to main content

End of life for major versions of Aiven services and tools

End of life (EOL) is the date after which Aiven services and tools are no longer supported or maintained.

Aiven services​

Aiven aims to follow the EOL schedule set by the original authors and maintainers of the open source software (the upstream projects). Once the upstream project retires a specific version, they do not receive security updates and critical bug fixes anymore by the maintainers.

Outdated services don't offer the level of protection our customers need, so Aiven follows the upstream project's EOL schedule to ensure that Aiven services are always running on supported versions.

Version numbering​

Aiven services inherit the upstream project's software versioning scheme. Depending on the service, a major version can be either a single digit (for example, PostgreSQL® 14) or in the format major.minor (for example, Kafka® 3.2). The exact version of the service is visible in the Aiven Console when the service is running.

Aiven for Elasticsearch®​

Aiven for Elasticsearch major versions will reach EOL on the same date as the upstream open source project's EOL. Aiven for OpenSearch® is Aiven's service offering for Elasticsearch.

VersionAiven EOLUpstream EOL
2.x2020-10-302018-02-28
5.x2020-10-302019-03-11
6.x2020-11-202020-11-20
7.x2022-03-232022-05-11 (v7.10)

Aiven for OpenSearch®​

Aiven for OpenSearch® is the open source continuation of the original Elasticsearch service. The EOL for Aiven for OpenSearch® is generally dependent on the upstream project.

VersionAiven EOLService creation supported untilUpstream EOL
1.xTo be announcedTo be announcedTo be announced
2.xTo be announcedTo be announcedTo be announced

Aiven for PostgreSQL®​

Aiven for PostgreSQL® major versions will reach EOL on the same date as the upstream open source project's EOL.

VersionAiven EOLService creation supported untilService creation supported from
9.52021-04-152021-01-262015-12-22
9.62021-11-112021-05-112016-09-29
102022-11-102022-05-102017-01-14
112023-11-092023-05-092017-03-06
122024-11-142024-05-142019-11-18
132025-11-132025-05-132021-02-15
142026-11-122026-05-122021-11-11
152027-11-112027-05-122022-12-12
162028-11-092028-05-092024-01-09

Aiven for Apache Kafka®​

Starting with v2.5, Aiven for Kafka® versions will reach EOL one year after they are made available on the Aiven platform.

VersionAiven EOLService creation supported untilService creation supported from
1.0.x2021-02-012017-11-01
1.1.x2021-02-012018-07-31
2.0.x2021-02-012018-07-30
2.1.x2021-02-012018-12-04
2.2.x2021-02-012019-04-19
2.3.x2021-08-132021-08-132019-09-05
2.4.x2021-08-132021-08-132019-10-21
2.5.x2021-08-132021-08-132020-05-05
2.6.x2021-08-132021-08-132020-08-13
2.7.x2022-01-242021-10-212021-01-21
2.8.x2022-06-022022-01-262021-04-26
3.02022-11-222022-07-042021-11-22
3.12023-02-142022-10-262022-02-14
3.22023-06-272023-03-282022-06-21
3.32023-12-122023-09-122022-12-23
3.42024-05-132024-02-132023-05-09
3.52024-07-312024-03-302023-07-31
3.62024-10-182024-09-012023-10-18
3.72025-04-172025-01-172024-04-17
3.82026-09-032026-06-032024-09-06

Aiven for Apache Cassandra®​

VersionAiven EOLService creation supported untilService creation supported from
32022-07-272022-04-272018-11-08
4.02024-09-302024-09-302021-12-09
4.12025-09-30To be announced2024-01-18

Aiven for M3DB​

Starting from v1.5, Aiven for M3DB versions will reach EOL six months after newer major and minor versions are made available on the Aiven platform.

VersionAiven EOLService creation supported untilService creation supported from
1.12023-09-012023-06-012021-02-23
1.22023-09-012023-06-012021-10-11
1.5N/AN/A2022-05-05
VersionAiven EOLService creation supported untilService creation supported from
1.162024-11-212024-08-212023-01-01
1.19N/AN/A2024-05-21

EOL policy for major versions​

The Aiven EOL policy is applicable only for services whose major versions are controlled until the customer.

It applies to both powered-on and powered-off services running the affected versions.

EOL notifications​

When Aiven sets the EOL date for a service major version:

  • Customers receive an email notification along with instructions on the next steps.
  • The Aiven Console shows an EOL alert for affected services.
  • Email reminders are sent to customers monthly.
  • In the month of the EOL date, the weekly reminders are sent to customers.

EOL best practices​

It's highly recommended to perform the version upgrade well before EOL so that you can test the compatibility for any breaking changes, plan for unforeseen issues, and migrate to the newer version on your own schedule. After the EOL date:

  1. If the service is powered on, it's automatically upgraded to the latest version.
  2. If the service is powered off, it's deleted.

Aiven offers database forking as an efficient tool to test the version upgrade before upgrading their production services.

Aiven tools​

Aiven offers multiple tools for interacting with the Aiven platform and services. These include the Aiven CLI, the Aiven Provider for Terraform, and the Aiven Operator for Kubernetes®.

Breaking changes in the Aiven API can result in new major versions of the Aiven tools. While backwards compatibility is typically maintained, certain changes require us to deprecate older versions of the tools.

Aiven CLI​

VersionAiven EOL
1.x2023-12-11
2.x2023-12-11
3.x2023-12-11
4.xTo be announced

Aiven Provider for Terraform​

Older versions will continue to work, but there will be no new features or bug fixes after the EOL date.

VersionAiven EOL
1.x2023-12-31
2.x2023-12-31
3.x2023-12-31
4.xTo be announced

Aiven Operator for Kubernetes​

VersionAiven EOL
0.xTo be announced