AWS omics documentation change
Summary
Updated engine logs documentation to clarify that CloudWatch now captures logs for all runs (both successful and failed) in near real-time, while S3 receives logs after run completion. Removed conditional logging distinctions.
Security assessment
The change improves operational transparency by expanding log availability but doesn't address a specific security vulnerability or weakness. Enhanced logging indirectly supports security monitoring but isn't explicitly security-focused.
Diff
diff --git a/omics/latest/dev/troubleshooting.md b/omics/latest/dev/troubleshooting.md index bcdf83c96..bf98dd5ce 100644 --- a//omics/latest/dev/troubleshooting.md +++ b//omics/latest/dev/troubleshooting.md @@ -34 +34 @@ The following topics can help you troubleshoot issues that you encounter when us - * Where do I find the engine logs for successfully completed runs? + * Where do I find the engine logs? @@ -51 +51 @@ Review the error code from the task failure message to understand the failure. R -### Where do I find the engine logs for successfully completed runs? +### Where do I find the engine logs? @@ -53 +53 @@ Review the error code from the task failure message to understand the failure. R -HealthOmics publishes logs to CloudWatch for failed runs only. If a run completes successfully, HealthOmics delivers the engine logs to your Amazon S3 bucket. For more information, see [Logs in Amazon S3](./monitoring-cloudwatch-logs.html#s3-logs). +HealthOmics publishes engine logs to CloudWatch in near real-time for all runs (successful and failed). Engine logs are also delivered to your Amazon S3 bucket after the run completes. For more information, see [Monitoring HealthOmics with CloudWatch Logs](./monitoring-cloudwatch-logs.html) and [Logs in Amazon S3](./monitoring-cloudwatch-logs.html#s3-logs). @@ -97 +97 @@ In the `/aws/omics/WorkflowLog` CloudWatch log group, open the log stream for th - 4. If the compute requirements for both tasks match, verify that the inputs have not changed between the tasks. To do this, open the engine logs. If the run has a status of FAILED, the logs will be in Cloudwatch Log Group /aws/omics/WorkflowLog. Otherwise the engine logs can be found in the output directory of the run. + 4. If the compute requirements for both tasks match, verify that the inputs have not changed between the tasks. To do this, open the engine logs. Engine logs are available in CloudWatch Log Group /aws/omics/WorkflowLog for all runs. They are also available in the output directory of the run after completion.