AWS timestream documentation change
Summary
Added notes recommending that the S3 VPC endpoint for Timestream for InfluxDB private clusters be associated with a VPC hosting only those databases and stating that shared VPCs are not currently supported for Timestream for InfluxDB 3.
Security assessment
These notes provide security guidance for network isolation (preferring dedicated VPCs) and clarify a current limitation (no shared VPC support). This promotes security best practices like network segmentation to reduce attack surface and potential lateral movement, but there is no mention of a specific vulnerability being patched.
Diff
diff --git a/timestream/latest/developerguide/s3-vpc-endpoint-private-clusters.md b/timestream/latest/developerguide/s3-vpc-endpoint-private-clusters.md index 127a8662f..fc6997e68 100644 --- a//timestream/latest/developerguide/s3-vpc-endpoint-private-clusters.md +++ b//timestream/latest/developerguide/s3-vpc-endpoint-private-clusters.md @@ -12,0 +13,8 @@ When deploying private clusters, you must configure an S3 VPC endpoint with appr +###### Note + +The S3 endpoint should preferably be associated with a VPC that hosts only Timestream for InfluxDB private databases. + +###### Note + +Shared VPCs are not currently supported for Timestream for InfluxDB 3. +