aiven · wojcik-dorota · Dec 1, 2025 · Dec 2, 2025
@@ -5,10 +5,6 @@ platform:
   - changed-files:
       - any-glob-to-any-file: 'docs/platform/**'
 
-service/alloydbomni:
-  - changed-files:
-      - any-glob-to-any-file: 'docs/products/alloydbomni/**'
-
 service/cassandra:
   - changed-files:
       - any-glob-to-any-file: 'docs/products/cassandra/**'

@@ -83,9 +83,3 @@ jobs:
     uses: ./.github/workflows/update-adv-params.yaml
     with:
       service-name: valkey
-
-  update-adv-params-alloydbomni:
-    name: Update parameters - AlloyDB Omni
-    uses: ./.github/workflows/update-adv-params.yaml
-    with:
-      service-name: alloydbomni
@@ -2,7 +2,7 @@ SCRIPTS         = ./scripts
 INCLUDESDIR      = ./static/includes
 
 # Generate config listing for a service type
-all-service-type-configs: service-type-config-cassandra service-type-config-clickhouse service-type-config-flink service-type-config-grafana service-type-config-kafka_mirrormaker service-type-config-kafka_connect service-type-config-kafka service-type-config-mysql service-type-config-opensearch service-type-config-caching service-type-config-pg service-type-config-dragonfly service-type-config-valkey service-type-config-alloydbomni
+all-service-type-configs: service-type-config-cassandra service-type-config-clickhouse service-type-config-flink service-type-config-grafana service-type-config-kafka_mirrormaker service-type-config-kafka_connect service-type-config-kafka service-type-config-mysql service-type-config-opensearch service-type-config-caching service-type-config-pg service-type-config-dragonfly service-type-config-valkey
 
 service-type-config-cassandra:
 	node "$(SCRIPTS)/service_type_parser.js" "cassandra" "$(INCLUDESDIR)/config-cassandra.md"
@@ -43,9 +43,6 @@ service-type-config-caching:
 service-type-config-valkey:
 	node "$(SCRIPTS)/service_type_parser.js" "valkey" "$(INCLUDESDIR)/config-valkey.md"
 
-service-type-config-alloydbomni:
-	node "$(SCRIPTS)/service_type_parser.js" "alloydbomni" "$(INCLUDESDIR)/config-alloydbomni.md"
-
 cloud-list:
 	node "$(SCRIPTS)/clouds_parser.js" "$(INCLUDESDIR)/clouds-list.md"
 

@@ -92,7 +92,7 @@ These permissions apply to the
 | View services                | `project:services:read`       | <ul> <li> View all details for services in a project, except the service logs. </li> </ul>                                                                                                                                                                                                                                                                  |
 | Manage services              | `project:services:write`      | <ul> <li> Create and delete services. </li> <li> Power on and off services. </li> <li> Add and remove dynamic disk sizing and tiered storage. </li> <li> Change service plans. </li> <li> Change deployment models. </li> <li> Change clouds and regions. </li> <li> Update IP allowlists. </li> <li> Change the network configuration options. </li> <li> Add, edit, and delete service tags. </li> <li> Enable and disable termination protection. </li> <li> Configure backup settings. </li> <li> Add and remove service contacts. </li> <li> Create a fork of a service. </li> </ul>                                                                                                       |
 | Manage service configuration | `service:configuration:write` | <ul> <li> Change clouds and regions. </li> <li> Change deployment models. </li> <li> Update IP allowlists. </li> <li> Change the network configuration options. </li> <li> Add and remove service tags. </li> <li> Enable and disable termination protection. </li> <li> Configure backup settings. </li> <li> Add and remove service contacts. </li> </ul> |
-| Access data                  | `service:data:write`          | <ul> <li> Perform service queries through the API and Console. </li> <li> View query statistics and current queries. </li> <li> Manage service-specific features like Kafka Topics and Schemas, PostgreSQL and AlloyDB Omni connection pools, and OpenSearch indexes. </li> </ul>                                                                           |
+| Access data                  | `service:data:write`          | <ul> <li> Perform service queries through the API and Console. </li> <li> View query statistics and current queries. </li> <li> Manage service-specific features like Kafka Topics and Schemas, PostgreSQL connection pools, and OpenSearch indexes. </li> </ul>                                                                           |
 | View service logs            | `service:logs:read`           | <ul> <li> View logs for all services in the project. </li> </ul> **Service logs may contain sensitive information.**                                                                                                                                                                                                                                        |
 | View configuration secrets   | `service:secrets:read`        | <ul> <li> Read service configuration secrets such as keys. </li> <li> View service users. </li> </ul>                                                                                                                                                                                                                                                                                      |
 | Manage service users         | `service:users:write`         | <ul> <li> Create and delete service users. </li> <li> View service users. </li> <li> View, update, and reset connection information for services. </li> <li> View service user credentials. </li> <li> Manage service user credentials. </li> <li> View all services in a project. </li> </ul>                                                                                                                                                                                           |
@@ -19,7 +19,6 @@ and Aiven for Grafana®.
 By default, Aiven-managed services allow up to 50 users.
 This limit does not apply to the following services:
 
-- Aiven for AlloyDB Omni
 - Aiven for Apache Cassandra®
 - Aiven for Caching
 - Aiven for Dragonfly
@@ -50,7 +49,6 @@ To increase the maximum number of users allowed for a service,
 
 Use the service user resource for your Aiven service:
 
-- Aiven for AlloyDB Omni: [`aiven_alloydbomni_user`](https://registry.terraform.io/providers/aiven/aiven/latest/docs/resources/alloydbomni_user)
 - Aiven for ClickHouse®: [`aiven_clickhouse_user`](https://registry.terraform.io/providers/aiven/aiven/latest/docs/resources/clickhouse_user)
 - Aiven for Apache Kafka®: [`aiven_kafka_user`](https://registry.terraform.io/providers/aiven/aiven/latest/docs/resources/kafka_user)
 - Aiven for MySQL®: [`aiven_mysql_user`](https://registry.terraform.io/providers/aiven/aiven/latest/docs/resources/mysql_user)

@@ -30,9 +30,6 @@ product portfolio.
 -   Aiven for PostgreSQL® with the TimescaleDB extension is your best
     choice if you already use PostgreSQL, require **SQL compatibility**
     and have a limited time series use case.
--   Aiven for AlloyDB Omni is a solid option for **PostgreSQL compatible**
-    workloads with a need for columnar analytical data and seamless AI
-    integration across any cloud.
 -   Aiven for Clickhouse® is your best choice when you need a high-prformance
     columnar time series database for OLAP workloads or a data analytics warehouse.
 

@@ -33,7 +33,6 @@ need [AWS Management Console](https://aws.amazon.com/console) or
 :::note
 AWS PrivateLink is not supported for:
 
-- Aiven for AlloyDB Omni
 - Aiven for Apache Cassandra®
 - Aiven for Apache Flink®
 - Aiven for Apache Kafka® MirrorMaker 2

@@ -55,18 +55,8 @@ before January 7, 2026. For further assistance, contact your account team.
 
 **EOL date**: December 5, 2025
 
-### Service impact
-
-- **End of availability (EOA)**: September 5, 2025
-
-  After this date, you can no longer create new Aiven for AlloyDB Omni services. Existing
-  services continue to operate until the end of life (EOL) date but you cannot change
-  plans for these services.
-
-- **End of life (EOL)**: December 5, 2025
-
-  On this date, all active Aiven for AlloyDB Omni services are powered off and deleted,
-  making data from these services inaccessible.
+Since December 5, 2025, Aiven for AlloyDB Omni services are no longer available,
+and data they hosted is inaccessible.
 
 ### Migration options