Product updates

Get the latest updates on features, fixes and improvements.

RSS feed

936 results

  • Jun 26, 2026

      New
      Aiven for OpenSearch®

    Dedicated node roles for Aiven for OpenSearch® (general availability)

    Dedicated node roles for Aiven for OpenSearch® are now in general availability for clusters running version 2.19 and later. You can deploy or upgrade to a cluster using a service plan with node roles. Node roles isolate workloads across specialized node groups, reducing resource contention while improving stability, scalability, and query performance. For details, see Dedicated node roles in Aiven for OpenSearch®.

  • Jun 26, 2026

      New
      Aiven for OpenSearch®

    Cross-cluster replication for Aiven for OpenSearch® (limited availability)

    Aiven for OpenSearch® now supports cross-cluster replication (CCR). This feature is in limited availability. Contact Aiven to request access.
    CCR lets you replicate indices, mappings, and metadata from a leader cluster to one or more follower clusters across regions or cloud providers. Use it to place data closer to your users for lower query latency and to spread query-heavy workloads across follower clusters for better availability.
    Set up CCR from the Cross cluster replication section on the service Overview page in the Aiven Console or with the Aiven API. You can promote an existing OpenSearch service to a follower or create a new one. This sets up the connection between the follower and the leader. Then you start replication from the follower using the OpenSearch replication APIs either per index or with an auto-follow rule that replicates every index matching a pattern. See Set up cross-cluster replication for Aiven for OpenSearch® for details.

  • Jun 23, 2026

      Improved
      Aiven for ClickHouse®

    End-of-life schedule for Aiven for ClickHouse® 25.3

    Aiven for ClickHouse® 25.3 has scheduled end of availability (EOA) and end of life (EOL) dates.

    • End of availability: July 1, 2026. New service creation is no longer available for version 25.3.
    • End of life: September 30, 2026. Services running version 25.3 are automatically upgraded to version 25.8 after this date.

    Upgrade services before the EOL date to avoid disruption. Fork a service before upgrading to test compatibility.

    To learn more, see Aiven for ClickHouse version lifecycle policy and Aiven for ClickHouse version dates.

  • Jun 23, 2026

      New
      Aiven for Apache Kafka®

    Audit logging for Aiven for Apache Kafka®

    You can now enable and configure audit logging for Aiven for Apache Kafka® services from your service configuration.

    Audit logging records Kafka client activity to help support security reviews and compliance workflows. Audit logs can include authenticated activity, unauthenticated access attempts, and allowed or denied Kafka operations, depending on the configuration.

    Enabling or updating audit logging causes a rolling restart of the Kafka brokers in the service.

    For more information, see Audit logging for Aiven for Apache Kafka®.

  • Jun 23, 2026

      New
      Aiven for OpenSearch®

    Upgrade to OpenSearch® 3.6 LTS

    OpenSearch® long-term support (LTS) version 3.6 is now available for Aiven for OpenSearch services. Apply this version on your services to benefit from the 3.6 improvements.

    Highlights

    • 32x vector storage compression: 1-bit Scalar Quantization delivers 32x compression across Faiss and Lucene engines with 24% better recall and 15% lower latency. Cost and performance win on semantic search or RAG pipelines.
    • Built-in APM via OpenTelemetry: A new APM solution built on OpenTelemetry provides end-to-end visibility into distributed systems, useful if you're already shipping traces and metrics into your Aiven for OpenSearch service for observability.
    • Improved Dashboards — in-context visualization editing: You can now create and edit visualizations directly within a dashboard without navigating away.
    • Better log analytics with PPL: PPL search result highlighting and new commands improve the day-to-day experience for teams using Aiven for OpenSearch for log analytics.
    • Security fix: The release upgrades dependencies to address CVE vulnerabilities.

    Learn more

  • Jun 23, 2026

      New
      BYOC
      Amazon Web Services

    Self-service enhanced compliance BYOC clouds for AWS

    You can now set up enhanced compliance bring your own cloud (BYOC) clouds yourself, without help from Aiven. When you create an AWS custom cloud, choose a compliance deployment model to run Aiven services in your own AWS account under specific compliance requirements:

    • hipaa for healthcare workloads that handle protected health information (PHI) under the Health Insurance Portability and Accountability Act (HIPAA)
    • pci_dss for payment workloads that require cardholder data environment (CDE) isolation under the Payment Card Industry Data Security Standard (PCI DSS)

    These clouds keep your data in your AWS account: services have no public internet access and are reachable only over VPC peering or AWS PrivateLink, outbound traffic is proxied through a bastion host, backups and cold data are stored in your own object storage, all resources are tagged with their compliance model for governance and audit traceability, and services cannot be forked or migrated to another cloud.

    For more information, see Enhanced compliance BYOC clouds.

  • Jun 23, 2026

      New
      Aiven Terraform provider

    Aiven Provider for Terraform version 4.59.0 now available

    This version of the Aiven Terraform Provider adds support for Apache Kafka share groups, audit logging, and enhanced database configuration options.

    • New fields in the Aiven for Apache Kafka resource support configuration for Kafka share groups: controlling group membership limits, heartbeat intervals, session timeouts, record locking, and delivery counts.
    • Kafka audit logging is now available through the new kafka_user_config.kafka.audit_log field.
    • Support for Apache Kafka version 4.2.
    • New aiven_kafka_schema field references enables management of schema references to other registered subjects.
    • Aiven for MySQL services now support InnoDB adaptive hash indexing and IOPS capacity configuration through the new innodb_adaptive_hash_index and innodb_io_capacity fields. A new relay_log_space_limit field provides better control over replication storage usage.
    • Rate throttling options for Aiven for Opensearch restore and snapshot operations are available across Azure, GCS, and S3 migrations, allowing better control over cluster resource utilization during migrations.
    • Rsyslog integration is now supported with configurable settings for log processing and formatting.

    For full details, see the complete changelog.

  • Jun 22, 2026

      Improved
      Aiven for Apache Kafka® Connect

    BigQuery connector for Aiven for Apache Kafka® Connect version 2.14.0

    The BigQuery connector is upgraded to version 2.14.0, which improves write reliability when the connector retries BigQuery writes or runs GCS batch load jobs.

    This version includes the following change:

    • Makes putAttemptId unique across BigQuery internal write retries and GCS batch idempotent load jobs to prevent duplicate processing during write operations.

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

  • Jun 22, 2026

      New
      Aiven API

    Billing group, invoice, and card endpoints are deprecated

    These endpoints will be sunset in 3 months on 22 September 2026:

    • GET /v1/account/{account_id}/billing-group: Use GET /v1/organization/{organization_id}/billing-groups instead.
    • GET /v1/billing-group: Use GET /v1/organization/{organization_id}/billing-groups instead.
    • POST /v1/billing-group: Use POST /v1/organization/{organization_id}/billing-groups instead.
    • PUT /v1/billing-group/{billing_group_id}: Use PUT /v1/organization/{organization_id}/billing-group/{billing_group_id} instead.
    • DELETE /v1/billing-group/{billing_group_id}: Use DELETE /v1/organization/{organization_id}/billing-group/{billing_group_id} instead.
    • GET /v1/billing-group/{billing_group_id}/invoice: Use GET /v1/organization/{organization_id}/invoices instead.
    • GET /v1/billing-group/{billing_group_id}/invoice/{invoice_number}/csv: Use GET /v1/organization/{organization_id}/invoice/{invoice_number}/csv instead.
    • GET /v1/billing-group/{billing_group_id}/projects: Use GET /v1/organization/{organization_id}/projects instead.
    • GET /v1/card: Use GET /v1/organization/{organization_id}/payment-method/credit-cards instead.
    • DELETE /v1/card/{card_id}: Use DELETE /v1/organization/{organization_id}/payment-method/credit-card/{payment_method_id} instead.
    • GET /v1/billing-group/{billing_group_id}: Use GET /v1/organization/{organization_id}/billing-group/{billing_group_id} instead.
    • GET /v1/billing-group/{billing_group_id}/invoice/{invoice_number}/lines: Use GET /v1/organization/{organization_id}/invoice/{invoice_number}/lines instead.
    • GET /v1/invoices/{invoice_number}: Use GET /v1/organization/{organization_id}/invoice/{invoice_number} instead.

    For more information, see the Aiven API documentation.