AWS res documentation change
Summary
Fixed CloudWatch log group path syntax by adding leading slashes in three instances
Security assessment
The change corrects log path formatting but does not address security vulnerabilities or document security features. No security implications identified in path syntax correction.
Diff
diff --git a/res/latest/ug/res-troubleshooting-known-issues.md b/res/latest/ug/res-troubleshooting-known-issues.md index efa534b7a..ed4741a06 100644 --- a//res/latest/ug/res-troubleshooting-known-issues.md +++ b//res/latest/ug/res-troubleshooting-known-issues.md @@ -363 +363 @@ RES 2024.06 fails to apply snapshots from prior versions if the AD groups contai -The cluster-manager CloudWatch logs (under the `<environment-name>/cluster-manager` log group) will include the following error during AD sync: +The cluster-manager CloudWatch logs (under the `/<environment-name>/cluster-manager` log group) will include the following error during AD sync: @@ -722 +722 @@ Linux virtual desktops can get stuck in "RESUMING" status when restarting after -After the instance is rebooted, the AWS Systems Manager doesn't run any remote commands to create a new DCV session and the following log message is missing in the vdc-controller CloudWatch logs (under the `<environment-name>/vdc/controller` CloudWatch log group): +After the instance is rebooted, the AWS Systems Manager doesn't run any remote commands to create a new DCV session and the following log message is missing in the vdc-controller CloudWatch logs (under the `/<environment-name>/vdc/controller` CloudWatch log group): @@ -792 +792 @@ To prevent new virtual desktops from running into the same issue: -RES fails to sync AD users after SSO is set up for at least two hours (two AD sync cycles). The cluster-manager CloudWatch logs (under the `<environment-name>/cluster-manager` log group) include the following error during AD sync: +RES fails to sync AD users after SSO is set up for at least two hours (two AD sync cycles). The cluster-manager CloudWatch logs (under the `/<environment-name>/cluster-manager` log group) include the following error during AD sync: