Product updates

Get the latest updates on features, fixes and improvements.

RSS feed

966 results

  • Sep 4, 2026

      Improved
      Aiven for Apache Kafka® Connect

    BigQuery sink connector updated to version 2.15.0

    Aiven for Apache Kafka® Connect now supports version 2.15.0 of the BigQuery sink connector. This version improves connector reliability:

    • Automatically retries 404 Not found: Dataset errors during streaming inserts.
    • Automatically retries 400 jobBackendError errors during merge queries.

    For configuration instructions, see Create a sink connector from Apache Kafka® to Google BigQuery. For the complete release history, see BigQuery connector releases.

  • Sep 4, 2026

      New
      Oracle Cloud

    OCI region ap-singapore-2 now on Aiven

    Oracle Cloud Infrastructure (OCI) region ap-singapore-2 (Singapore West) is now supported on the Aiven Platform.

    See all the supported OCI regions in the documentation.

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

    See the documentation for all cloud providers and regions supported on the Aiven Platform.

  • Sep 3, 2026

      New
      Aiven for Apache Kafka®

    OAuth 2.0/OIDC authentication for Karapace Schema Registry

    You can now use OAuth 2.0/OpenID Connect (OIDC) bearer tokens to authenticate requests to Karapace Schema Registry on Aiven for Apache Kafka®. Schema Registry validates JSON Web Tokens (JWTs) using the same OIDC provider settings as Apache Kafka.

    You can also enable role-based authorization to control Schema Registry operations based on roles in the JWT. Enabling JWT authentication does not disable basic authentication, so you can migrate clients gradually and disable basic authentication after the migration is complete.

    Requires Karapace 6.2.1 or later. Configure authentication and authorization in the Aiven Console or with the Aiven CLI.

    For more information, see Enable OAuth 2.0/OIDC authentication for Aiven for Apache Kafka® Schema Registry.

  • Sep 3, 2026

      New
      Aiven for ClickHouse®

    Aiven for ClickHouse® 26.3 is generally available

    Aiven for ClickHouse® 26.3, a long-term support (LTS) release, is now generally available. You can select version 26.3 when you create a service or upgrade an existing service from version 25.8.

    Version 25.8 remains the default for new services, and existing services are not upgraded automatically. If your service runs version 25.3, upgrade to version 25.8 before upgrading to version 26.3. Direct upgrades from version 25.3 to 26.3 and downgrades are not supported.

    Before upgrading, review the compatibility changes, removed features, and changed defaults. Test the upgrade on a fork of your service.

    For more information, see Upgrade to Aiven for ClickHouse 26.3 and Manage versions in Aiven for ClickHouse.

  • Sep 2, 2026

      New
      Microsoft Azure
      BYOC

    Bring your own cloud (BYOC) for Microsoft Azure

    Aiven now supports Microsoft Azure as a self-service cloud provider for bring your own cloud (BYOC). You can create custom clouds on AWS, Google Cloud, and Microsoft Azure through the Aiven Console or with the Aiven CLI. Azure supports two deployment models: private, with a bastion host proxying traffic to privately addressed workload nodes, and public, with service VMs directly accessible from the internet.

    To get started, you need an Azure subscription and a user or service principal with the required subscription permissions. As a one-time step per tenant, you install Aiven's pre-registered enterprise application on your Microsoft Entra tenant. The setup generates a Terraform template that you deploy to your Azure subscription. The template creates role assignments granting the Aiven enterprise application access to your subscription, a resource group, custom role definitions, and storage accounts. For the private model, it also creates two virtual networks (bastion and workload VNets), VNet peering, network security groups, and NAT gateways. For the public model, it creates a single workload VNet with a network security group.

    For more information, see Create a Microsoft Azure-integrated custom cloud.

  • Sep 1, 2026

      New
      Aiven for DataHub

    Aiven for DataHub upgraded to version 1.7

    This version includes improvements to the DataHub UI, new connectors, updates to search, and connector improvements.

    There are 7 new ingestion sources, including Cube, AWS Kinesis, Open Data Contract Standard, SAP Datasphere and Document DB platform. The UI has a new metrics home and sidebar experience, and first-class metric and semanticModel entities with dedicated pages. It’s also now possible to create, link, unlink, delete, and edit the columns of logical models in the UI.

    You can upgrade your DataHub services any time in the Aiven Console.

    Full details on the improvements and breaking changes are available in the DataHub release notes.

  • Sep 1, 2026

      Security
      Aiven API

    Secrets redacted in API responses

    Aiven is moving to a consistent secret redaction policy across all its APIs. Starting 1 March 2027, service user passwords, service user_config fields, and integration endpoint secrets in API responses will be redacted by default.

    This change ensures a more secure and consistent platform experience for all users. The following endpoints are impacted by this change. Their responses redact secrets by default:

    • GET /project/{project}/service/{service_name}/user/{service_username}
    • GET /project/{project}/service/{service_name}
    • GET /project/{project}/service
    • POST /project/{project}/service
    • PUT /project/{project}/service/{service_name}
    • PUT /project/{project}/service/{service_name}/user/{service_username}/credentials/reset
    • PUT /project/{project}/service/{service_name}/user/{service_username}
    • PATCH /project/{project}/service/{service_name}/service_type
    • GET /project/{project}/integration_endpoint/{integration_endpoint_id}
    • GET /project/{project}/integration_endpoint
    • POST /project/{project}/integration_endpoint
    • PUT /project/{project}/integration_endpoint/{integration_endpoint_id}

    The following GET endpoints can return secrets in plaintext when you include the include_secrets=true query parameter:

    • GET /project/{project}/service/{service_name}/user/{service_username}
    • GET /project/{project}/service/{service_name}
    • GET /project/{project}/service
    • GET /project/{project}/integration_endpoint/{integration_endpoint_id}

    The listed write endpoints redact secrets, except POST /project/{project}/service/{service_name}/user, which returns newly generated credentials in plaintext.

    What you need to do

    If you have integrations that require access to secrets, use the include_secrets=true query parameter to return secrets in plaintext. Only GET endpoints can reveal secrets. The caller must have the required permissions:

    • Service user passwords: admin, operator, developer, service:secrets:read, or service:users:write.
    • Service user_config secrets: admin, operator, or service:secrets:read.
    • Integration endpoint secrets: admin or project:integrations:write.

    The organization-level role role:organization:adminalso grants some of these permissions. See the permissions documentation for details.

    More information is available in the documentation for API secret redaction and the Aiven API.

  • Sep 1, 2026

      Improved
      Aiven MCP

    Restrict MCP connections to read-only operations

    Organization admins can now restrict all MCP connections in their organization to read-only operations. MCP clients such as Cursor and Claude Code can view services and other resources, but cannot create, modify, or delete them.

    The restriction applies to all MCP connections in the organization. Users cannot override it in their client configuration.

    To restrict MCP connections to read-only operations, go to Admin > Security > Authentication and select Restrict MCP connections to read-only operations.

    For more information, see Aiven MCP and Set authentication policies for organization users.

  • Aug 28, 2026

      Improved
      Aiven for Apache Kafka® Connect

    OpenSearch® sink connector for Aiven for Apache Kafka® Connect upgraded to version 3.2.0

    The OpenSearch® sink connector has been upgraded to version 3.2.0. You can now configure the connector to write directly to an existing OpenSearch index, index alias, or data stream instead of creating a new index for each Kafka topic.

    For setup instructions, see Create an OpenSearch sink connector. For more information about the release, see the connector release notes.