AWS omics medium security documentation change
Summary
Removed 'Caching requirements for tasks' section and added warning about non-deterministic outputs with caching. Added reference to shared responsibility model documentation.
Security assessment
Added explicit guidance about avoiding caching for non-deterministic tasks, which could lead to incorrect cached results and data integrity issues. References the shared responsibility model, which typically addresses security controls.
Diff
diff --git a/omics/latest/dev/workflow-cache-startrun.md b/omics/latest/dev/workflow-cache-startrun.md index 5cf680f85..e80ecc216 100644 --- a/omics/latest/dev/workflow-cache-startrun.md +++ b/omics/latest/dev/workflow-cache-startrun.md @@ -5 +5 @@ -Configuring a run with run cache using the consoleConfiguring a run with run cache using the CLITracking your run cache hitsCaching requirements for tasksError cases for run caches +Configuring a run with run cache using the consoleConfiguring a run with run cache using the CLITracking your run cache hitsError cases for run caches @@ -12,0 +13,2 @@ After a run completes, you can invoke the GetRunTask and ListRunTask API operati +If one or more tasks in a run generate non-deterministic outputs, we strongly recommend that you don’t use call caching for the run, or you opt out these specific tasks from caching. For more information, see [Shared responsibility model](./how-run-cache.html#run-cache-srm). + @@ -25,2 +26,0 @@ You provide an IAM service role when you start a run. To use call caching, the s - * Caching requirements for tasks - @@ -57 +57 @@ From the console, you configure the run cache for a run when you start the run. -To start a run that uses a run cache, add the cache-id parameter to the **start-run** CLI command. Optionally, use the `cache-behavior` parameter to override the default behavior that you configured for the run cache. +To start a run that uses a run cache, add the cache-id parameter to the **start-run** CLI command. Optionally, use the `cache-behavior` parameter to override the default behavior that you configured for the run cache. The following example shows only the cache fields for the command: @@ -61 +61 @@ To start a run that uses a run cache, add the cache-id parameter to the **start- - --run-id "xx" \ + ... @@ -83,15 +82,0 @@ For more information about these logs, see [Logs in CloudWatch ](./monitoring-cl -## Caching requirements for tasks - -HealthOmics caches task outputs for tasks that meet the following requirements: - - * The task must define a container. HealthOmics won't cache outputs for a task with no container. - - * The task must produce one or more outputs. You specify task outputs in the workflow definition. - - * The workflow definition must not use dynamic values. For example, if you pass a parameter to a task with a value that increments with every run, HealthOmics doesn't cache the task outputs. - - - - -If you update the CPU, GPU, or memory allocation in a task definition, HealthOmics doesn't try to find a cache match for the task. Instead, it recomputes the task using the new values for the compute and memory resources. If the task completes successfully, HealthOmics adds these task outputs to the cache. This approach lets you test new resource allocations as part of the run optimization process. - @@ -121 +106 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please -Engine-specific features +Engine-specific caching features