Product updates

Get the latest updates on features, fixes and improvements.

RSS feed

1015 results

  • Nov 6, 2026

      New
      Aiven API
      Aiven Terraform provider
      Aiven CLI

    Bring your own key (BYOK) now generally available on Aiven-managed infrastructure

    You can now use your own encryption keys to protect Aiven service data at rest on Aiven-managed infrastructure. Bring your own key (BYOK) was previously available only with bring your own cloud (BYOC), and is now generally available for all Aiven projects at no additional cost.

    Register a customer managed key (CMK) from your own key management service, and associate it with your services:

    • AWS KMS, Google Cloud KMS, Oracle Cloud Infrastructure (OCI) Vault, and Azure Key Vault are supported.
    • Your CMK is used as a KEK (Key Encryption Key) to encrypt the actual DEK (Data Encryption Key) used to protect service data at rest, all backups, and data in transit between the service and its backups.
    • Set a default CMK for new services, use a different CMK for each service, or change and remove the CMK for an existing service.
    • You get complete control over your encryption keys, which means you can independently manage the key lifecycle and access policies in your own cloud account.

    Manage your CMKs with the Aiven API, the Aiven CLI, or the Aiven Provider for Terraform.

    For setup steps for each key management service and the full list of operations, see Bring your own key (BYOK) in the Aiven docs.

    With BYOC, BYOK remains an enterprise feature that is available on request.

  • Nov 6, 2026

      Improved
      Aiven for MySQL

    Aiven for MySQL® free tier is being retired on 21 December 2026

    Changes to the Aiven for MySQL® free tier

    The Aiven for MySQL® free tier is being discontinued:

    • End of availability (EOA): From 6 November 2026, you can no longer create new free Aiven for MySQL services. Existing free services keep running until the end of life (EOL) date.
    • End of life (EOL): On 21 December 2026, remaining free Aiven for MySQL services will be powered off, and their data and backups will be deleted. This can’t be undone.

    Aiven for MySQL remains available on all paid plans, and only the free tier is affected.

    What you can do next

    Choose one of the following paths before the EOL date:

    • Keep using MySQL: upgrade your free service to the Aiven for MySQL Developer plan. Your data stays in place and your connection details do not change.
    • Keep a free database: migrate your data to the Aiven for PostgreSQL® free tier.
    • Take your data with you: export your data to a file with mysqldump or mydumper.

    For the migration paths and steps, see Aiven for MySQL® free tier: migration options.

  • Nov 5, 2026

      New
      Aiven for MySQL

    More advanced configuration parameters for Aiven for MySQL®

    Aiven for MySQL® now supports 14 new advanced configuration parameters, and adds guardrails to four parameters you can already set. You can set persistent, service-wide defaults for connection limits, InnoDB flushing and purge behavior, InnoDB index builds, the data dictionary cache, the default collation, and the event scheduler.

    The new parameters are available through the Aiven Console, CLI, and API, and span six categories:

    • Connection limits: max_connections, max_user_connections
    • InnoDB flushing and purge: innodb_max_dirty_pages_pct, innodb_max_dirty_pages_pct_lwm, innodb_max_purge_lag, innodb_max_purge_lag_delay
    • InnoDB sorting and full-text index builds: innodb_sort_buffer_size, innodb_ft_sort_pll_degree, innodb_ft_cache_size, innodb_ft_total_cache_size
    • Data dictionary cache: schema_definition_cache, tablespace_definition_cache
    • Server defaults: collation_server, event_scheduler

    Four parameters that were already available now have guardrails. The new limits apply to new values only, so values you have already stored keep working:

    • innodb_log_buffer_size: You can set up to 15% of your plan's RAM
    • sort_buffer_size: You can set up to 2% of your plan's RAM
    • wait_timeout: You can set 30 seconds or more
    • long_query_time: You can set 0.05 seconds or more

    For more information, see Advanced parameters for Aiven for MySQL®.

  • Nov 4, 2026

      New
      Aiven for ClickHouse®

    Aiven for ClickHouse® Developer tier now available

    Build prototypes, develop side projects, and run small analytics workloads at a predictable cost with the new Aiven for ClickHouse® Developer tier. For $43/month, billed hourly, you get a fully managed, always-on, single-node ClickHouse service with storage, backups, and networking included.

    The Developer tier includes:

    • 2 shared vCPUs, 4 GB RAM, and 25 GB storage.
    • Daily backups, with one backup retained.
    • Aiven and third-party service integrations.
    • Metrics, logs, and Basic support.

    To get started, see the Aiven for ClickHouse® Developer tier documentation.

  • Nov 4, 2026

      New
      Aiven for Valkey™

    Aiven for Valkey™ clustering now generally available

    Aiven for Valkey™ clustering is now generally available (GA). Clustering distributes your data across multiple shards so your service can handle larger datasets and higher throughput than a single node can support. It includes high availability with automatic failover, replicas on each shard, and automatic resharding when you change the number of primary nodes.

    Clustered services are backed up automatically. Each shard is backed up independently, so a restored cluster isn't point-in-time consistent across shards, and you can only restore to a plan with the same shard count. You can't convert an existing service to or from a cluster plan, or migrate data into a cluster from an external Redis or Valkey server. Applications that connect with a standalone-mode client need to switch to a cluster-aware Valkey or Redis client.

    To get started, choose a cluster-N plan when you create an Aiven for Valkey service, where N is the per-node memory in GiB (for example cluster-4 or cluster-8). Set the shard_count and replicas configuration options to size your cluster. replicas defaults to 0, so set it to at least 1 if you want automatic failover. Resharding requires Valkey 9.x or later. For more details, see Aiven for Valkey clustering.

  • Nov 2, 2026

      New
      Aiven for Apache Kafka® Connect

    Snowflake v4 Sink connector available in early availability

    Snowflake Kafka connector version 4.2.1 is now available in early availability for Aiven for Apache Kafka® Connect. It uses the Snowpipe Streaming high-performance architecture.

    The existing Snowflake Sink connector (3.x) remains available and isn't automatically upgraded to 4.x.

    Version 4.x isn't backward compatible with 3.x. To migrate, review the migration requirements, create a new connector, and test the migration on a non-production service before moving production workloads.

    For setup and migration instructions, see Create and configure a Snowflake sink connector. For upstream changes, see the Snowflake Kafka connector release notes.

  • Oct 26, 2026

      New
      Aiven for Managed agents

    Create and run AI agents on Aiven (limited availability)

    You can now create and run AI agents on Aiven with Managed Agents, available in limited availability.

    Use agents to gather information, investigate issues, and perform tasks across Aiven and other systems without managing the underlying infrastructure.

    For example, you can create an agent that monitors Kafka consumer lag and posts a daily summary to Slack, or an SRE agent that investigates the health of your Aiven services.

    With Managed Agents, you can:

    • Create agents using templates, task descriptions, or manual configuration.
    • Choose an AI model and configure agent instructions.
    • Connect agents to Aiven services and external systems using built-in tools and Model Context Protocol (MCP) integrations.
    • Chat with agents and schedule recurring tasks.

    To get started, open your project in the Aiven Console, go to Agents, and request access to Managed Agents.

  • Oct 26, 2026

      New
      Aiven Operator for Kubernetes

    Aiven Operator for Kubernetes version 0.49.0 now available

    This release adds connection Secret routing for PrivateLink, new service configuration options, and several reliability fixes. Important updates include:

    • Choose which service endpoint is published to your connection Secret with the new connInfoSecretRoute field on ServiceUser and ServiceUserRotation. Leaving it unset keeps existing behavior, so Secrets are not rewritten on upgrade.
    • Added Kafka consumer group fields such as userConfig.kafka.group_consumer_session_timeout_ms and the related heartbeat and session timeout limits.
    • Added MySQL InnoDB tuning fields, including innodb_max_dirty_pages_pct and innodb_max_purge_lag.
    • Added OpenSearch ML Commons and KNN cache fields.
    • Added Valkey cluster fields userConfig.shard_count and userConfig.replicas.
    • Added the pg_lake PostgreSQL variant and Kafka Connect custom plugin support.

    For complete details on all changes, check out the full release notes.

  • Oct 26, 2026

      New
      Aiven for Apache Kafka®

    Apache Kafka® broker version available as a metric

    The kafka_server_app_info_info metric on the Prometheus endpoint reports the version of each Apache Kafka® broker in your Aiven for Apache Kafka® service. Use it to show the broker version on a dashboard or alert when it differs from the version you expect.

    On Apache Kafka 4.x, use the KafkaVersion label to get the upstream Apache Kafka version. The metric is available after you apply a maintenance update to your service.

    For more information, see Broker version information.