AWS timestream medium security documentation change
Summary
Removed important note about S3 VPC endpoint policy requirements for private cluster creation and note about InfluxDB Explorer limitations
Security assessment
The removed note explicitly warned about S3 VPC endpoint policy requirements to avoid cluster creation failures. Removing this security guidance could lead to misconfigurations where users create clusters with overly restrictive S3 policies, potentially causing operational failures or unintended access patterns. This constitutes a security documentation regression.
Diff
diff --git a/timestream/latest/developerguide/creating-a-cluster.md b/timestream/latest/developerguide/creating-a-cluster.md index 38614cc62..1dedb07ce 100644 --- a//timestream/latest/developerguide/creating-a-cluster.md +++ b//timestream/latest/developerguide/creating-a-cluster.md @@ -81,4 +80,0 @@ Multi-node configurations beyond 3 nodes will be available in future releases vi -###### Note - -**Important:** When creating a private Timestream for InfluxDB 3 cluster, ensure your S3 VPC endpoint policy allows full access. The cluster creation will fail if the S3 endpoint has restrictive policies. - @@ -196,4 +191,0 @@ After your cluster is created and available: -###### Note - -InfluxDB 3 Explorer is intended for **basic data exploration and administration with limited query support**. For performance testing or complex query constructions, please use the CLI or API instead -