AWS Security ChangesHomeSearch

AWS AWSCloudFormation documentation change

Service: AWSCloudFormation · 2025-07-18 · Documentation low

File: AWSCloudFormation/latest/TemplateReference/aws-resource-omics-workflow.md

Summary

Clarified prerequisites for private workflow creation, including workflow definition formats, parameter templates, and storage capacity details.

Security assessment

These changes improve documentation clarity about workflow setup requirements but do not address security issues or document security-specific features. No evidence of security vulnerability mitigation.

Diff

diff --git a/AWSCloudFormation/latest/TemplateReference/aws-resource-omics-workflow.md b/AWSCloudFormation/latest/TemplateReference/aws-resource-omics-workflow.md
index 763b29189..2968e5be7 100644
--- a//AWSCloudFormation/latest/TemplateReference/aws-resource-omics-workflow.md
+++ b//AWSCloudFormation/latest/TemplateReference/aws-resource-omics-workflow.md
@@ -9 +9 @@ This is the new _AWS CloudFormation Template Reference Guide_. Please update you
-Creates a private workflow.Private workflows depend on a variety of resources that you create and configure before creating the workflow:
+Creates a private workflow. Before you create a private workflow, you must create and configure these required resources:
@@ -11 +11 @@ Creates a private workflow.Private workflows depend on a variety of resources th
-  * _Input data_ : Input data for the workflow, stored in an S3 bucket or a AWS HealthOmics sequence store. 
+  * _Workflow definition files_ : Define your workflow in one or more workflow definition files, written in WDL, Nextflow, or CWL. The workflow definition specifies the inputs and outputs for runs that use the workflow. It also includes specifications for the runs and run tasks for your workflow, including compute and memory requirements. The workflow definition file must be in .zip format.
@@ -13,3 +13 @@ Creates a private workflow.Private workflows depend on a variety of resources th
-  * _Workflow definition files_ : Define your workflow in one or more workflow definition files, written in WDL, Nextflow, or CWL. The workflow definition specifies the inputs and outputs for runs that use the workflow. It also includes specifications for the runs and run tasks for your workflow, including compute and memory requirements.
-
-  * (Optional) _Parameter template_ \- You can create a parameter template file that defines the run parameters, or AWS HealthOmics can generate the parameter template for you. 
+  * (Optional) _Parameter template_ : You can create a parameter template file that defines the run parameters, or AWS HealthOmics can generate the parameter template for you.
@@ -19 +17 @@ Creates a private workflow.Private workflows depend on a variety of resources th
-  * (Optional) _Sentieon licenses_ : Request a Sentieon license if you plan to use Sentieon software in a private workflow.
+  * (Optional) _Sentieon licenses_ : Request a Sentieon license if using the Sentieon software in a private workflow.
@@ -24 +22 @@ Creates a private workflow.Private workflows depend on a variety of resources th
-For more information, see [Creating or updating a private workflow in AWS HealthOmics](https://docs.aws.amazon.com/omics/latest/dev/creating-private-workflows.html) in the AWS HealthOmics User Guide.
+For more information, see [Creating or updating a private workflow in AWS HealthOmics](https://docs.aws.amazon.com/omics/latest/dev/creating-private-workflows.html) in the _AWS HealthOmics User Guide_.
@@ -187 +185 @@ _Required_ : No
-The default static storage capacity (in gibibytes) for runs that use this workflow or workflow version.
+The default static storage capacity (in gibibytes) for runs that use this workflow or workflow version. The `storageCapacity` can be overwritten at run time. The storage capacity is not required for runs with a `DYNAMIC` storage type.