Product updates

Get the latest updates on features, fixes and improvements.

RSS feed

911 results

  • May 15, 2026

      New
      Aiven for PostgreSQL®

    Aiven for PostgreSQL® upgraded to 18.4, 17.10, 16.14, 15.18, and 14.23

    Aiven for PostgreSQL® has been upgraded to latest minor versions 18.4, 17.10, 16.14, 15.18, and 14.23, which contain a variety of fixes to previous versions. Removing bugs and security vulnerabilities increases database performance, improves service availability, and helps ensure business continuity. Existing instances will be scheduled for a rolling upgrade as part of our standard maintenance cycle.

    See PostgreSQL release notes for more details about the PostgreSQL minor releases.

  • May 15, 2026

      Improved
      Aiven for Apache Kafka® Connect

    BigQuery connector for Aiven for Apache Kafka® Connect version 2.13.0

    The BigQuery connector has been upgraded to version 2.13.0. This release improves reliability for connector deployments that write to BigQuery tables from multiple tasks or connector instances.
    This version includes:

    • Added retry-and-reconcile handling for concurrent schema update failures in GCS to BigQuery load jobs.
    • Added write-attempt metadata with putAttemptId, which helps downstream systems distinguish rows written by different Kafka Connect put() attempts.
    • Updated dependency versions, including Jackson, Jetty, and Apache Kafka clients.

    For more information, refer to the GitHub release notes for the BigQuery connector for Apache Kafka.

  • May 12, 2026

      Improved
      Aiven for PostgreSQL®

    Deprecation: Aiven for PostgreSQL® 14

    Aiven for PostgreSQL® version 14 will reach its end-of-life (EOL) on 12 November 2026. Starting from this EOL date, any services remaining on version 14 will be automatically upgraded to the latest version when possible, or to another supported version. As of today, service creation is no longer supported on version 14.

    Recommended actions

    Manually upgrade your services before the EOL date to ensure a controlled transition:

    1. Test via forking: Use the Aiven fork feature to clone your 14 service into a target-version instance. This allows you to verify application compatibility without affecting production data.
    2. Check for breaking changes: Review breaking changes between the versions, if any.
    3. Perform manual upgrade: Follow the upgrade guide to trigger the version change at your convenience.

  • May 11, 2026

      New
      Aiven Terraform provider

    Aiven Provider for Terraform version 4.56.0 now available

    Version 4.56.0 brings major updates for encryption management, service lifecycle changes, and Kafka and ClickHouse configuration support.

    Customer managed keys are now supported across all service resources through the new cmk_id field. This makes it easier to apply bring-your-own-key encryption consistently across services.

    This release also introduces important compatibility updates:

    • BYOC on AWS plans are now more accurate: changes that require new infrastructure will recreate the resource instead of attempting an in-place update.
    • Expanded service configuration support:
      • ClickHouse, MySQL, and DataHub integrations have new configuration support.
      • Kafka and Kafka Connect now have IPv6 connector resolution, Vault certificates, and safer handling of environment secrets.

    Cassandra and Redis resources and data sources have also been removed in this release.

    For full details, see the complete changelog.

  • May 6, 2026

      New
      Aiven for Apache Kafka® Connect

    AMQP source connector for Apache Kafka® Connect

    Aiven for Apache Kafka® Connect now supports the AMQP source connector.

    The AMQP source connector reads messages from AMQP-compatible queues, such as RabbitMQ, and writes them to Apache Kafka® topics. Each source message is serialized as JSON and written as a Kafka record with a generated ULID key.

    Key considerations:

    • Supports AMQP queues only.
    • key.converter must use StringConverter.
    • value.converter must use StringConverter or JsonConverter.
    • For single-queue deployments, tasks.max=1 is recommended unless multiple consumers are intentionally configured.
    • Messages available while the connector is offline can be missed.

    For configuration and usage details, see the AMQP source connector documentation.

  • May 6, 2026

      Improved
      Aiven for Valkey™

    Aiven for Valkey™: Version 9 is now the default for new services

    We are excited to announce that Valkey 9 is now the default version for all new Aiven for Valkey™ services.

    What this means for you:

    • New services: When creating a new Aiven for Valkey™ service, the platform will now automatically select version 9 as the default.
    • Existing services: Your currently running services on version 8.1 remain unaffected and will continue to operate normally.

    See our documentation for the Aiven for Valkey service version lifecycle.

  • May 6, 2026

      New
      Oracle Cloud

    More OCI cloud regions supported on Aiven

    The Aiven Platform now supports the following Oracle Cloud Infrastructure (OCI) regions:

    • ap-melbourne-1: Australia, Melbourne
    • eu-milan-1: Italy, Milan
    • eu-turin-1: Italy, Turin
    • me-jeddah-1: Saudi Arabia, Jeddah
    • me-riyadh-1: Saudi Arabia, Riyadh

    The OCI regions support is a limited availability feature. For more information or access, contact your account team.

    See all the supported OCI regions or all cloud providers and regions supported on the Aiven Platform.

  • May 5, 2026

      Improved
      Aiven API

    Project API endpoints are deprecated

    The following project API endpoints are deprecated:

    • GET /v1/project: Use GET /v1/organization/{organization_id}/projects instead.
    • DELETE /v1/project/{project}: Use DELETE /v1/organization/{organization_id}/project/{project_id} instead.
    • GET /v1/project/{project}: Use GET /v1/organization/{organization_id}/project/{project_id} instead.
    • PUT /v1/project/{project}: Use PATCH /v1/organization/{organization_id}/project/{project_id} instead. The replacement is a PATCH endpoint, which changes this from full replace to partial update.
    • GET /v1/account/{account_id}/projects: Use GET /v1/organization/{organization_id}/projects instead.

    If you previously relied on a single global listing call using GET /v1/project, you now need to iterate organizations and call the organization-scoped listing endpoint per organization.

    For more information, see the Aiven API documentation.

  • Apr 30, 2026

      New
      Aiven for OpenSearch®

    Learning to Rank now available for Aiven for OpenSearch®

    The Learning to Rank (LTR) plugin is now available for Aiven for OpenSearch®. Use your own click and user engagement data to train ranking models, deploy them to your cluster, and re-rank search results for greater relevance. You can combine LTR with BM25, vector, or hybrid search to power higher-quality application, ecommerce, and enterprise search experiences and improve click-through and conversion.

    LTR is available for Aiven for OpenSearch® 2.19+ and 3.3+.