AWS omics documentation change
Summary
Updated log access instructions: CloudWatch logs now only for failed runs, successful run logs delivered to S3
Security assessment
The change modifies log delivery mechanisms but doesn't reference security vulnerabilities, access controls, or data protection. It's an operational update without security implications.
Diff
diff --git a/omics/latest/dev/troubleshooting.md b/omics/latest/dev/troubleshooting.md index bf98dd5ce..bcdf83c96 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? + * Where do I find the engine logs for successfully completed runs? @@ -51 +51 @@ Review the error code from the task failure message to understand the failure. R -### Where do I find the engine logs? +### Where do I find the engine logs for successfully completed runs? @@ -53 +53 @@ Review the error code from the task failure message to understand the failure. R -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). +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). @@ -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. 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. + 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.