Update a cluster in Timestream for InfluxDB 3 - Amazon Timestream
Update a cluster using the Amazon Web Services Management ConsoleUpdate a cluster using the Amazon CLIConsiderations when updating a cluster
Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China (PDF).

For similar capabilities to Amazon Timestream for LiveAnalytics, consider Amazon Timestream for InfluxDB. It offers simplified data ingestion and single-digit millisecond query response times for real-time analytics. Learn more here.

Update a cluster in Timestream for InfluxDB 3

After your cluster is created, you can modify certain configuration parameters to adapt to changing workload requirements in Amazon Timestream. Note that some modifications may cause temporary downtime during the update process.

Update a cluster using the Amazon Web Services Management Console

  1. Sign in to the Amazon Management Console and open the Amazon Timestream for InfluxDB console.

  2. In the navigation pane, choose InfluxDB Databases.

  3. Select the cluster you want to modify.

  4. Choose  Modify.

  5. Update available settings:

    • Instance class: Scale compute resources up or down (applies to all nodes in the cluster and requires cluster restart).

    • Parameter group: Associate a different parameter group (requires cluster restart).

    • Log delivery configuration: Enable or modify CloudWatch Logs export.

  6. Choose Continue and review your changes.

  7. Select when to apply changes:

    • Apply immediately: Changes are applied right away (may cause brief downtime).

  8. Choose Modify cluster.

Update a cluster using the Amazon CLI

To update an existing cluster using the Amazon CLI:

aws timestream-influxdb update-db-cluster \
  --region us-east-1 \
  --identifier "my-influxdb3-cluster" \
  --db-instance-type db.influxIOIncluded.2xlarge \
  --db-parameter-group-identifier "new-parameter-group" \
  --apply-immediately

Considerations when updating a cluster

Modifiable parameters

The following parameters can be modified after cluster creation:

Parameter Description Impact
Instance class Scale compute/memory resources up or down Requires rolling restart of nodes
Parameter group Change database engine configuration Requires cluster restart
Log delivery Configure CloudWatch Logs export Applied immediately

Non-modifiable parameters

The following parameters cannot be modified after cluster creation:

  • VPC and Subnets: Network location is fixed.

  • Security Groups: Network access controls cannot be changed.

  • Public Accessibility: Internet accessibility setting is permanent.

  • DB Cluster Identifier: Cluster name cannot be changed.

  • Edition: Cannot change between Core and Enterprise.

Downtime impact:

  • Instance class changes: Rolling restart (minimal downtime with multi-node clusters).

  • Parameter group changes: Full cluster restart required.

  • Log configuration changes: No downtime.

Best practices:

  • Plan network configuration carefully before cluster creation as it cannot be changed.

  • Test changes in non-production environments first.

  • Monitor metrics during and after updates to verify performance.

  • Use cluster endpoints to ensure transparent failover during rolling updates.

  • Avoid node-specific endpoints during update operations.

Validation:

  • The system validates all changes before applying them.

  • Invalid configurations are rejected with descriptive error messages.

  • Some parameter combinations may not be compatible.

Rollback:

  • Keep previous parameter group configurations for easy rollback.

  • Document current settings before making changes.

  • For critical changes, create cluster snapshots before updating.

Monitor update progress

Track the update status through:

  1. Console: The cluster status shows "Modifying" during updates.

  2. CLI: Query cluster status: 

    aws timestream-influxdb describe-db-cluster \
  --identifier "my-influxdb3-cluster"

    The possible status for a cluster are:

    • CREATING

    • UPDATING

    • DELETING

    • AVAILABLE

    • FAILED

    • DELETED

    • UPDATING_INSTANCE_TYPE

    • PARTIALLY_AVAILABLE (Applicable only only multi-node cluster when some nodes are still being created)

  3. CloudWatch Metrics: Monitor performance metrics during updates.

Limitations

Current limitations for cluster updates:

  • Cannot modify VPC, subnets, security groups, or public accessibility after creation.

  • Cannot change from Core to Enterprise edition (or vice versa).

  • Cannot rename the cluster (DB cluster identifier is immutable).

  • All nodes must use the same instance class.

  • Parameter groups are immutable (must create new ones for changes).

By understanding these update capabilities and limitations, you can effectively manage and scale your InfluxDB 3 clusters to meet evolving workload requirements while planning appropriately for settings that must be configured at cluster creation time.