AWS omics documentation change
Summary
Added documentation for enabling/disabling ephemeral storage using --scratch-storage-mode parameter
Security assessment
While ephemeral storage can have security implications, this change only documents feature usage without addressing vulnerabilities or security configurations. No security risks or protective measures are discussed.
Diff
diff --git a/omics/latest/dev/starting-a-run.md b/omics/latest/dev/starting-a-run.md index 783d042a1..64a11514e 100644 --- a//omics/latest/dev/starting-a-run.md +++ b//omics/latest/dev/starting-a-run.md @@ -168,0 +169,16 @@ You can override the default run storage type that was set in the workflow. +### Enabling ephemeral storage + +To enable ephemeral storage for a run, set `--scratch-storage-mode` to `LOCAL` when you start the run. HealthOmics mounts a dedicated local storage volume at `/tmp` for each workflow task instance. + + + aws omics start-run \ + --workflow-id workflow-id \ + --role-arn arn:aws:iam::123456789012:role/OmicsServiceRole \ + --output-uri s3://amzn-s3-demo-bucket/output-folder/ \ + --parameters file:///path/to/parameters.json \ + --scratch-storage-mode LOCAL + +To disable ephemeral storage for a specific run (for example, to isolate a failure), set `--scratch-storage-mode` to `SHARED`. + +For more information, see [Ephemeral storage for HealthOmics workflow tasks](./workflows-ephemeral-storage.html). +