AWS timestream documentation change
Summary
Updated maintenance window documentation with detailed configuration options, CLI examples, timezone support, and operational considerations including security patching requirements
Security assessment
The change adds documentation about maintenance windows and explicitly states that maintenance is required at least once per month for security and reliability patching. It also mentions that deferred maintenance beyond 25 days may result in forced maintenance to ensure security. However, this is routine operational documentation rather than addressing a specific security vulnerability.
Diff
diff --git a/timestream/latest/developerguide/timestream-for-influx-managing-maintaining-db.md b/timestream/latest/developerguide/timestream-for-influx-managing-maintaining-db.md index 87c157383..2cc9cb223 100644 --- a//timestream/latest/developerguide/timestream-for-influx-managing-maintaining-db.md +++ b//timestream/latest/developerguide/timestream-for-influx-managing-maintaining-db.md @@ -7 +7 @@ For similar capabilities to Amazon Timestream for LiveAnalytics, consider Amazon -# Maintaining a DB instance +# Maintenance windows @@ -24 +24 @@ Some maintenance items require that Amazon Timestream for InfluxDB take your DB - * Maintenance windows are configured to take place everyday between 12 AM and 4 AM local time for the Region your instance is being hosted. +**Maintenance window** @@ -26 +26,95 @@ Some maintenance items require that Amazon Timestream for InfluxDB take your DB - * Customer resources might be patched once a week in any one of the seven maintenance windows in the week. +Every Amazon Timestream for InfluxDB DB instance has a weekly maintenance window during which maintenance is performed. You can configure your maintenance window in two ways: + + * **Service managed (default)** : Amazon Timestream for InfluxDB determines the optimal maintenance window for your resource. + + * **Customer managed** : You specify a preferred maintenance window using the format `ddd:HH:MM-ddd:HH:MM` (for example, `Sun:02:00-Sun:04:00`). The window must be at least 2 hours and no more than 24 hours. Cross-midnight windows are supported. + + + + +You can set your preferred maintenance window when creating a DB instance or change it later using the `update-db-instance` API. + +**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. Use IANA timezone identifiers such as `America/New_York` or `Asia/Tokyo`. The system handles Daylight Saving Time transitions automatically. + +**CLI examples** + +Create a DB instance with a custom maintenance window: + + + aws timestream-influxdb create-db-instance \ + --name "my-influxdb" \ + --db-instance-type db.influx.medium \ + --allocated-storage 50 \ + --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 + + +Update the maintenance window on an existing DB instance: + + + aws timestream-influxdb update-db-instance \ + --identifier <instance-identifier> \ + --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-instance \ + --identifier <instance-identifier> \ + --maintenance-schedule '{ + "timezone": "UTC", + "preferredMaintenanceWindow": "" + }' \ + --region us-west-2 + + +###### Important + +If a required maintenance action has been deferred for more than 25 days, the service may apply maintenance outside of your preferred window to ensure the security and reliability of your resource. + +During maintenance, the DB instance status changes to `MAINTENANCE`. After completion, the status returns to `AVAILABLE`. + +**Supported timezones** + +Use IANA timezone identifiers. Timezone abbreviations such as `EST`, `PST`, and `GMT+5` are not supported. + +**Timezone** | **Description** +---|--- +`UTC`| Coordinated Universal Time (default) +`America/New_York`| US Eastern +`America/Chicago`| US Central +`America/Denver`| US Mountain +`America/Los_Angeles`| US Pacific +`America/Sao_Paulo`| Brazil +`Europe/London`| UK +`Europe/Paris`| Central Europe +`Europe/Berlin`| Germany +`Asia/Tokyo`| Japan +`Asia/Shanghai`| China +`Asia/Singapore`| Singapore +`Asia/Mumbai`| India +`Asia/Dubai`| UAE +`Australia/Sydney`| Australia Eastern +`Pacific/Auckland`| New Zealand + +**Considerations** + + * Maintenance windows define when maintenance _can_ occur, not when it _will_ occur. Maintenance is performed as needed, typically no more than once per week. + + * Maintenance is required at least once per month for security and reliability patching. + + * For Multi-AZ deployments, maintenance is performed on the standby first, then a failover occurs, minimizing downtime. + + * If you use a timezone with DST transitions, avoid scheduling maintenance between 1:00 AM and 3:00 AM to prevent skipped windows during spring forward.