AWS timestream documentation change

Service: timestream · 2026-03-16 · Documentation low

File: timestream/latest/developerguide/creating-a-cluster.md

Summary

Added documentation for multi-node cluster configurations up to 15 nodes, including node role definitions, parameter group requirements, availability zone distribution notes, and updated CLI examples with configuration details.

Security assessment

The changes focus on cluster configuration options and operational guidance without addressing security vulnerabilities. The note about nodes being distributed across AZs relates to high availability rather than security. No security patches, vulnerability disclosures, or access control changes are mentioned.

Diff

diff --git a/timestream/latest/developerguide/creating-a-cluster.md b/timestream/latest/developerguide/creating-a-cluster.md
index 01fea411a..bc7eeec13 100644
--- a//timestream/latest/developerguide/creating-a-cluster.md
+++ b//timestream/latest/developerguide/creating-a-cluster.md
@@ -44,0 +45,8 @@ Creating a new InfluxDB 3 cluster in Amazon Timestream involves selecting the ap
+         * **Multi-node cluster (up to 15 nodes)** : Configure via custom parameter group with: 
+
+           * 1-4 writer/reader nodes (ingestQueryInstances) 
+
+           * 0-13 reader-only nodes (queryOnlyInstances) 
+
+           * 1 dedicated compactor (required for clusters with 3+ nodes) 
+
@@ -47 +55 @@ Creating a new InfluxDB 3 cluster in Amazon Timestream involves selecting the ap
-Multi-node configurations beyond 3 nodes will be available in future releases via parameter group updates
+To create a multi-node cluster with more than 3 nodes, you must first create a custom parameter group with your desired node configuration, then create the cluster using that parameter group.
@@ -65 +73 @@ Multi-node configurations beyond 3 nodes will be available in future releases vi
-       * Or create/select a custom parameter group 
+       * Or create/select a custom parameter group for multi-node configurations 
@@ -80,0 +89,8 @@ Multi-node configurations beyond 3 nodes will be available in future releases vi
+###### Note
+
+Shared VPCs are not currently supported for Timestream for InfluxDB 3.
+
+###### Note
+
+For multi-node clusters, nodes are automatically distributed across multiple Availability Zones for high availability.
+
@@ -156 +172 @@ Create a cluster with a custom parameter group:
-          "dataFusionNumThreads": 64
+          "dataFusionNumThreads": 8
@@ -160 +176 @@ Create a cluster with a custom parameter group:
-    # Then create the cluster using the custom parameter group
+    # Then create the cluster using the parameter group identifier
@@ -164 +180 @@ Create a cluster with a custom parameter group:
-      --db-parameter-group-identifier "custom-enterprise-pg" \
+      --db-parameter-group-identifier "<parameter-group-identifier>" \
@@ -169,0 +186,31 @@ Create a cluster with a custom parameter group:
+###### Note
+
+The `--db-parameter-group-identifier` requires the parameter group identifier (not the name). Set `dataFusionNumThreads` to match the number of vCPUs for your instance type (for example, 8 for `db.influx.2xlarge`). For a complete guide on parameter configuration, see [Parameter Groups for DB Clusters in Amazon Timestream](./parameter-groups.html).
+
+Create a multi-node cluster (up to 15 nodes) with a custom parameter group:
+    
+    
+    # First, create a custom parameter group with your desired node configuration
+    aws timestream-influxdb create-db-parameter-group \
+      --name "custom-multinode-pg" \
+      --engine-type "InfluxDBv3Enterprise" \
+      --parameters '{
+        "InfluxDBv3Enterprise": {
+          "ingestQueryInstances": 4,
+          "queryOnlyInstances": 10,
+          "dedicatedCompactor": true,
+          "bufferMemLimitMb": 32768,
+          "dataFusionNumThreads": 8
+        }
+      }'
+    
+    # Then create the cluster using the parameter group identifier
+    aws timestream-influxdb create-db-cluster \
+      --region us-east-1 \
+      --name "my-multinode-enterprise-cluster" \
+      --db-parameter-group-identifier "<parameter-group-identifier>" \
+      --db-instance-type db.influxIOIncluded.2xlarge \
+      --vpc-subnet-ids subnet-12345abc subnet-67890def \
+      --vpc-security-group-ids sg-12345abc
+    
+
@@ -176 +223 @@ After your cluster is created and available:
-        aws timestream-influxdb get-db-cluster
+        aws timestream-influxdb get-db-cluster \
@@ -179,0 +227,8 @@ After your cluster is created and available:
+For multi-node clusters, you will receive:
+
+     * **Cluster read/write endpoint** : Distributes traffic to writer/reader nodes 
+
+     * **Cluster read-only endpoint** : Distributes traffic to all nodes capable of read operations (available when reader-only nodes are configured) 
+
+     * **Node endpoints** : Direct access to specific nodes for workload isolation 
+