AWS AmazonCloudWatch documentation change
Summary
Expanded list of supported Regions for Amazon Q Developer operational investigations, removed redundant preview notices, updated cross-Region inference documentation, and clarified encryption key usage.
Security assessment
The change adds explicit documentation about encryption defaults (AWS-owned key usage if no customer key is specified), improving transparency about data protection practices. While this enhances security documentation, there is no evidence of addressing a specific vulnerability.
Diff
diff --git a/AmazonCloudWatch/latest/monitoring/Investigations-GetStarted.md b/AmazonCloudWatch/latest/monitoring/Investigations-GetStarted.md index 397f84ac3..2d03039c5 100644 --- a//AmazonCloudWatch/latest/monitoring/Investigations-GetStarted.md +++ b//AmazonCloudWatch/latest/monitoring/Investigations-GetStarted.md @@ -11 +11,28 @@ See a sample investigationSet up operational investigations -The Amazon Q Developer operational investigations feature is in preview release and is subject to change. It is currently available only in the US East (N. Virginia) and US West (Oregon) Regions. +The Amazon Q Developer operational investigations feature is in preview release and is subject to change. It is currently available in the following Regions: + + * US East (N. Virginia) + + * US East (Ohio) + + * US West (N. California) + + * Asia Pacific (Hong Kong) + + * Asia Pacific (Mumbai) + + * Asia Pacific (Singapore) + + * Asia Pacific (Sydney) + + * Asia Pacific (Tokyo) + + * Europe (Frankfurt) + + * Europe (Ireland) + + * Europe (Spain) + + * Europe (Stockholm) + + + @@ -26,4 +52,0 @@ To set up Amazon Q Developer operational investigations, you create an investiga -###### Note - -The Amazon Q Developer operational investigations feature is in preview release and is subject to change. It is currently available only in the US East (N. Virginia) and US West (Oregon) Regions. - @@ -47,4 +69,0 @@ The console displays the sample investigation, with suggestions and findings in -###### Note - -The Amazon Q Developer operational investigations feature is in preview release and is subject to change. It is currently available only in the US East (N. Virginia) and US West (Oregon) Regions. - @@ -72 +91 @@ To be able to choose the recommended option of creating a new IAM role for Amazo -Amazon Q Developer operational investigations uses cross region inference to distribute traffic across different AWS Regions in the United States. For more information see [Cross region inference in Amazon Q Developer](https://docs.aws.amazon.com/amazonq/latest/qdeveloper-ug/cross-region-inference.html) in the Amazon Q Developer user guide. +Amazon Q Developer operational investigations uses _cross-Region inference_ to distribute traffic across different AWS Regions. For more information, see [Cross-Region inference](./Investigations-Security.html#cross-region-inference). @@ -86 +105 @@ Amazon Q Developer operational investigations uses cross region inference to dis - 6. (Optional) To encrypt your investigation data with a customer managed AWS KMS key, choose **Customize encryption settings** and follow the steps to create or specify a key to use. For more information, see [Encryption of investigation data](./Investigations-Security.html#Investigations-KMS). + 6. (Optional) To encrypt your investigation data with a customer managed AWS KMS key, choose **Customize encryption settings** and follow the steps to create or specify a key to use. If you don't specify a customer managed key, Amazon Q Developer operational investigations uses an AWS owned key for encryption. For more information, see [Encryption of investigation data](./Investigations-Security.html#Investigations-KMS).