AWS timestream documentation change
Summary
Simplified explanation of default permissions by removing redundant details about access methods (Console/CLI/API)
Security assessment
The change removes mention of specific access methods (Console/CLI/API) being blocked by default permissions, but maintains the core security principle of least privilege. This appears to be a documentation simplification rather than addressing a specific vulnerability or security incident.
Diff
diff --git a/timestream/latest/developerguide/security_iam_id-based-policy-examples-influxb.md b/timestream/latest/developerguide/security_iam_id-based-policy-examples-influxb.md index 4049773ca..05a3bf79a 100644 --- a//timestream/latest/developerguide/security_iam_id-based-policy-examples-influxb.md +++ b//timestream/latest/developerguide/security_iam_id-based-policy-examples-influxb.md @@ -11 +11 @@ For similar capabilities to Amazon Timestream for LiveAnalytics, consider Amazon -By default, users and roles don't have permission to create or modify Timestream for InfluxDB resources. They also can't perform tasks by using the AWS Management Console, AWS Command Line Interface (AWS CLI), or AWS API. To grant users permission to perform actions on the resources that they need, an IAM administrator can create IAM policies. The administrator can then add the IAM policies to roles, and users can assume the roles. +By default, users and roles don't have permission to create or modify Timestream for InfluxDB resources. To grant users permission to perform actions on the resources that they need, an IAM administrator can create IAM policies.