AWS timestream documentation change
Summary
Updated cluster scaling guidance with node count limits and added section about Core-to-Enterprise edition upgrades including operational constraints.
Security assessment
These changes provide feature capability documentation and upgrade procedures. The one-way upgrade restriction is operational rather than security-related. No evidence of security vulnerability mitigation or security feature introduction exists in the diff.
Diff
diff --git a/timestream/latest/developerguide/faq-clusters.md b/timestream/latest/developerguide/faq-clusters.md index 2d3b25aed..2b79ad2c8 100644 --- a//timestream/latest/developerguide/faq-clusters.md +++ b//timestream/latest/developerguide/faq-clusters.md @@ -31 +31 @@ You can create a cluster using the AWS Management Console, the AWS CLI, or the A -Enterprise clusters distribute nodes across multiple Availability Zones with dedicated ingest-query, query-only, and compactor roles. AWS manages the cluster topology and node roles. Nodes communicate internally and use DNS-based traffic distribution for client connections. For details on setting up multi-node clusters, see the [InfluxDB 3 Enterprise clustering documentation](https://docs.influxdata.com/influxdb3/enterprise/admin/clustering/). +Enterprise clusters support up to 15 nodes distributed across multiple Availability Zones, with dedicated writer/reader (up to 4), reader-only (up to 13), and compactor roles. AWS manages the cluster topology and node roles. Nodes communicate internally and use DNS-based traffic distribution for client connections. For details, see [Scaling a cluster](./multi-node-scaling.html) and the [InfluxDB 3 Enterprise clustering documentation](https://docs.influxdata.com/influxdb3/enterprise/admin/clustering/). @@ -36 +36,6 @@ Enterprise clusters distribute nodes across multiple Availability Zones with ded -You can scale vertically by changing the instance type, or scale horizontally (Enterprise only) by adding query-only nodes. Use the `update-db-cluster` command or the AWS Management Console to modify your cluster configuration. +You can scale vertically by changing the instance type, or scale horizontally (Enterprise only) by adding writer/reader nodes (up to 4) or reader-only nodes (up to 13). To scale horizontally, create a new parameter group with your desired node configuration and apply it to your cluster. Use the `update-db-cluster` command or the AWS Management Console to apply changes. For more information, see [Scaling a cluster](./multi-node-scaling.html). + +**How do I upgrade from Core to Enterprise edition?** + + +You can upgrade an existing Core cluster to Enterprise through the AWS Management Console. If this is the first Enterprise activation on your AWS account, the upgrade must be done via the console. After that initial activation, subsequent upgrades can also be performed using the AWS CLI or API. Note that this is a one-way operation—you cannot downgrade from Enterprise to Core. After the upgrade, your existing data will be gradually compacted in the background while the cluster remains usable. For details, see [Upgrade from Core to Enterprise edition](./upgrading-core-to-enterprise.html).