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.

Maintenance windows for Timestream for InfluxDB 3

Amazon Timestream for InfluxDB performs periodic maintenance on your resources. Maintenance most often involves updates to the underlying hardware, operating system, or database engine. These updates are mandatory. If maintenance is not performed during the designated window, it may be applied during a subsequent window.

How maintenance windows work

Every Timestream for InfluxDB resource has a weekly maintenance window during which maintenance is performed.

You can set your preferred maintenance window when creating a resource or change it later using the update APIs.

Management types

Maintenance windows can be managed in two ways:

Preferred maintenance window

The preferred maintenance window defines the weekly time slot during which maintenance can occur.

Format: ddd:HH:MM-ddd:HH:MM

Examples:

Constraints:

Maintenance begins within the first 30 minutes of your specified window. The exact start time is determined by the system and is consistent week to week for the same resource.

Timezone

You can specify a timezone for your maintenance window using the timezone field. When set, window times are interpreted in the specified timezone.

The timezone field is required in all maintenance schedule requests.

Format: IANA timezone identifier. Most timezones in the IANA Time Zone Database are supported, including common identifiers such as America/New_York, Europe/London, Asia/Tokyo, Asia/Kolkata, and Pacific/Auckland.

Daylight Saving Time: The system handles DST transitions automatically. If your window falls within a skipped DST hour (spring forward), maintenance is skipped that week. To avoid DST-related issues, schedule maintenance outside the 1:00 AM to 3:00 AM range, or use UTC.

Supported timezones:

During maintenance

When maintenance is being performed, the resource status changes to MAINTENANCE. During this time, the resource may be temporarily unavailable. After completion, the status returns to AVAILABLE.

API response fields

CLI examples

Setting a maintenance window when creating a resource

Service managed (default — no maintenance schedule specified):

aws timestream-influxdb create-db-cluster \
  --name "my-influxdb3-cluster" \
  --db-instance-type db.influx.2xlarge \
  --vpc-subnet-ids subnet-12345abc subnet-67890def \
  --vpc-security-group-ids sg-12345abc \
  --region us-west-2

Customer managed with UTC (default timezone):

aws timestream-influxdb create-db-cluster \
  --name "my-influxdb3-cluster" \
  --db-instance-type db.influx.2xlarge \
  --vpc-subnet-ids subnet-12345abc subnet-67890def \
  --vpc-security-group-ids sg-12345abc \
  --maintenance-schedule '{
    "preferredMaintenanceWindow": "Sun:02:00-Sun:04:00"
  }' \
  --region us-west-2

Customer managed with a specific timezone:

aws timestream-influxdb create-db-cluster \
  --name "my-influxdb3-cluster" \
  --db-instance-type db.influx.2xlarge \
  --vpc-subnet-ids subnet-12345abc subnet-67890def \
  --vpc-security-group-ids sg-12345abc \
  --maintenance-schedule '{
    "timezone": "America/New_York",
    "preferredMaintenanceWindow": "Sun:02:00-Sun:04:00"
  }' \
  --region us-west-2

Customer managed with an overnight window:

aws timestream-influxdb create-db-cluster \
  --name "my-influxdb3-cluster" \
  --db-instance-type db.influx.2xlarge \
  --vpc-subnet-ids subnet-12345abc subnet-67890def \
  --vpc-security-group-ids sg-12345abc \
  --maintenance-schedule '{
    "timezone": "Europe/London",
    "preferredMaintenanceWindow": "Sat:22:00-Sun:02:00"
  }' \
  --region us-west-2

Updating a maintenance window

Set a custom maintenance window on an existing resource:

aws timestream-influxdb update-db-cluster \
  --identifier "my-influxdb3-cluster" \
  --maintenance-schedule '{
    "timezone": "Asia/Tokyo",
    "preferredMaintenanceWindow": "Wed:03:00-Wed:06:00"
  }' \
  --region us-west-2

Revert to service managed:

aws timestream-influxdb update-db-cluster \
  --identifier "my-influxdb3-cluster" \
  --maintenance-schedule '{
    "timezone": "UTC",
    "preferredMaintenanceWindow": ""
  }' \
  --region us-west-2

Considerations