AWS timestream high security documentation change

Service: timestream · 2026-01-19 · Security-related high

File: timestream/latest/developerguide/configuring-a-influxdb-3-instance.md

Summary

Added critical note about S3 policies for private clusters with documentation link. Updated instance class references from 'db.influxIOIncluded' to 'db.influx' with billing clarification.

Security assessment

Added requirement for S3 policies in private clusters directly addresses potential security misconfiguration. Without proper VPC endpoint policies, private clusters could have unintended data exposure risks.

Diff

diff --git a/timestream/latest/developerguide/configuring-a-influxdb-3-instance.md b/timestream/latest/developerguide/configuring-a-influxdb-3-instance.md
index 56a7dd1aa..b89aeabb4 100644
--- a//timestream/latest/developerguide/configuring-a-influxdb-3-instance.md
+++ b//timestream/latest/developerguide/configuring-a-influxdb-3-instance.md
@@ -14,0 +15,2 @@ Using the AWS Management Console:
+**Important:** If creating a private cluster, make sure you add the [ required S3 policies to create your Timestream for InfluxDB 3 cluster](https://docs.aws.amazon.com/timestream/latest/developerguide/s3-vpc-endpoint-private-clusters.html)
+
@@ -41 +43 @@ Single node deployments use Single-AZ compute resources. In case of an issue, a
-    1. **Instance class** : Select the appropriate `db.influxIOIncluded` instance size (applies to all nodes). 
+    1. **Instance class** : Select the appropriate `db.influx` instance size (applies to all nodes). Worth noting your bill will show `db.influxIOIncluded` on your records. 
@@ -59 +61 @@ Using the AWS CLI:
-         --db-instance-type db.influxIOIncluded.4xlarge \
+         --db-instance-type db.influx.4xlarge \