Product updates

863 results

• Feb 10, 2026

  • Improved
  • Aiven for Apache Kafka® Connect

  Google external account credential restrictions for Apache Kafka Connect

  Aiven for Apache Kafka Connect validates Google Cloud external account credentials to block unsupported credential sources and requires allow-listing authentication URLs using gcp_auth_allowed_urls. File- and command-based credential sources are not supported.

  Impact:

  If a connector uses credential_source.url, configure gcp_auth_allowed_urls at the Kafka Connect service level. Connectors using file- or command-based credential sources fail validation.
  
  More information:

  • Create a Google Cloud Storage sink connector for Apache Kafka®
  • Create a sink connector from Apache Kafka® to Google BigQuery

• Feb 5, 2026

  • New
  • Aiven for PostgreSQL®

  New high availability architecture for Aiven for PostgreSQL^®

  We are introducing a redesigned architecture for Aiven for PostgreSQL®. This is a limited availability (LA) feature focusing on improved resilience, faster maintenance, a better upgrade experience, service reliability and performance. Once enabled for a project or an organization, it becomes the default for all new Aiven for PostgreSQL services.

  Key changes include:

  • Improved backup and startup times: Faster backups lead to shorter maintenance windows and significantly reduced service startup times.
  • Enhanced HA handling: The architecture provides greater resilience against network partitions and outages, and a new API allows you to trigger manual switchovers.
  • Rapid multi-node deployment: Optimized processes allow for faster startup times for multi-node service plans.
  • Streamlined pg_upgrade experience: Standby nodes now upgrade in-place, eliminating the wait times for multi-node services to become fully available after an upgrade.
  • Maintenance efficiency: Parallel node provisioning reduces the total time required for maintenance and synchronization for multi-node service plans.

• Feb 5, 2026

  • New
  • Aiven for PostgreSQL®

  TimescaleDB 2.25.0 for Aiven for PostgreSQL^® released

  TimescaleDB extension version 2.25.0 is now available for Aiven for PostgreSQL®. This release introduces performance improvements and bug fixes. Upgrade to 2.25.0 at your earliest convenience to make sure you use the most robust and secure version available.

  For details on all TimescaleDB releases, see the release notes.

• Feb 2, 2026

  • New
  • Aiven for PostgreSQL®

  TimescaleDB 2.24.0 for Aiven for PostgreSQL^® released

  TimescaleDB extension version 2.24.0 is now available for Aiven for PostgreSQL®. This release introduces performance improvements and bug fixes. Upgrade to 2.24.0 at your earliest convenience to make sure you use the most robust and secure version available.

  For details on all TimescaleDB releases, see the release notes.

• Feb 2, 2026

  • New
  • Aiven for PostgreSQL®

  TimescaleDB 2.23.0 and 2.23.1 for Aiven for PostgreSQL^® released

  TimescaleDB extension versions 2.23.0 and 2.23.1 are now available for Aiven for PostgreSQL®. These release introduce performance improvements and bug fixes. Upgrade to 2.23.0 and 2.23.1 at your earliest convenience to make sure you use the most robust and secure version available.

  For details on all TimescaleDB releases, see the release notes.

• Jan 27, 2026

  • New
  • Aiven Terraform provider

  Aiven Provider for Terraform version 4.50.0 now available

  This version of the Aiven Provider for Terraform introduces automatic backup configuration for Kafka and PostgreSQL services, allowing you to set custom backup intervals and retention periods using the new backup_interval_hours and backup_retention_days fields.

  For Aiven for Apache Kafka® MirrorMaker 2, the follower_fetching_enabled field was added to the aiven_mirrormaker_replication_flow resource letting you enable rack awareness and follower fetching.

  For the complete list of changes and technical details, view the full Aiven Provider for Terraform changelog.

• Jan 27, 2026

  • New
  • Aiven for PostgreSQL®

  Aiven for PostgreSQL^® reads failover to primary now generally available

  Automatic failover to primary for read-only workloads is now generally available for all Aiven for PostgreSQL® users.

  When all standby nodes are unavailable, read traffic routed to the HA replica DNS endpoint is automatically redirected to the healthy primary node, ensuring uninterrupted access and minimizing downtime.

  Key highlights:

  • Seamless failover for read-only queries when standbys are unavailable
  • No application-side routing changes required
  • Single, stable connection endpoint for read traffic
  • Easy enable/disable via Console, CLI, API, Terraform, or Kubernetes

  To learn more, see the feature documentation.

• Jan 26, 2026

  • Improved
  • Aiven for OpenSearch®

  Deprecation: Aiven for OpenSearch^® 2.17

  Aiven for OpenSearch® version 2.17 will reach its end-of-life (EOL) on July 26, 2026. Following our multi-minor version support period, we are transitioning all services to version 2.19 to ensure your environment remains compatible with future releases.

  Key timeline

  • End-of-Life (EOL) date: July 26, 2026
  • Automatic upgrades: Starting July 26, 2026, any services remaining on version 2.17 will be automatically upgraded to version 2.19 during their next scheduled maintenance window.

  Why upgrade to 2.19?

  Upgrading to version 2.19 is a proactive step for your infrastructure:

  • Path to major version 3: Version 2.19 serves as the essential "jump version" required for the future upgrade to OpenSearch major version 3, which will bring significant performance improvements.
  • Long-term stability: Version 2.19 is the current stable standard on the Aiven platform, offering the latest bug fixes and features over 2.17.

  Recommended actions

  We recommend manually upgrading your services before the July deadline to ensure a controlled transition:

  1. Test via forking: Use the Aiven fork feature to clone your 2.17 service into a 2.19 instance. This allows you to verify application compatibility without affecting production data.
  2. Review documentation: Check the OpenSearch breaking changes guide for any minor breaking changes between 2.17 and 2.19.
  3. Perform manual upgrade: Follow our upgrade guide to trigger the version change at your convenience.

• Jan 26, 2026

  • Improved
  • Aiven for OpenSearch®

  Deprecation: Aiven for OpenSearch^® version 1

  Aiven for OpenSearch® version 1.x will reach its end-of-life (EOL) on July 26, 2026, following its deprecation upstream. All services running version 1.x must be upgraded to version 2.x to ensure continued support, security, and performance.

  Key timeline

  • End-of-life (EOL) date: July 26, 2026
  • Automatic upgrades: Starting July 26, 2026, any services remaining on version 1.x will be automatically upgraded to version 2.19 during their next scheduled maintenance window.

  Why upgrade?

  Upgrading to OpenSearch 2.x provides significant technical advantages:

  • Enhanced performance: Version 2.x is approximately 6x faster than version 1.3.
  • Reduced storage footprint: Zstandard compression reduces on-disk storage requirements by 15% to 30%.

  Recommended Actions

  To ensure a smooth transition and verify application compatibility, we recommend taking the following steps before the July deadline:

  1. Review breaking changes: Consult the OpenSearch 2.0 breaking changes guide to identify potential impacts.
  2. Test via forking: We suggest forking your service at its current version, then upgrading the fork to version 2.19 to test for incompatibilities in a safe environment.
  3. Perform manual upgrade: Upgrade your services at your convenience before the EOL date.