create_workflow
async
¶
create_workflow(
request_id: WorkflowRequestId,
*,
config_overrides: Optional[AsyncOmicsClientConfig] = None,
name: Optional[WorkflowName] = None,
description: Optional[WorkflowDescription] = None,
engine: Optional[WorkflowEngine] = None,
definition_zip: Optional[bytes] = None,
definition_uri: Optional[WorkflowDefinition] = None,
main: Optional[WorkflowMain] = None,
parameter_template: Optional[WorkflowParameterTemplate] = None,
storage_capacity: Optional[int] = None,
tags: Optional[TagMap] = None,
accelerators: Optional[Accelerators] = None,
storage_type: Optional[StorageType] = None,
container_registry_map: Optional[ContainerRegistryMap] = None,
container_registry_map_uri: Optional[Uri] = None,
readme_markdown: Optional[ReadmeMarkdown] = None,
parameter_template_path: Optional[ParameterTemplatePath] = None,
readme_path: Optional[ReadmePath] = None,
definition_repository: Optional[DefinitionRepository] = None,
workflow_bucket_owner_id: Optional[WorkflowBucketOwnerId] = None,
readme_uri: Optional[S3UriForObject] = None,
) -> CreateWorkflowResponse
Creates a private workflow. Before you create a private workflow, you must create and configure these required resources:
-
Workflow definition file: A workflow definition file 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
.zipformat. For more information, see Workflow definition files in Amazon Web Services HealthOmics.-
You can use Amazon Q CLI to build and validate your workflow definition files in WDL, Nextflow, and CWL. For more information, see Example prompts for Amazon Q CLI and the Amazon Web Services HealthOmics Agentic generative AI tutorial on GitHub.
-
-
(Optional) Parameter template file: A parameter template file written in JSON. Create the file to define the run parameters, or Amazon Web Services HealthOmics generates the parameter template for you. For more information, see Parameter template files for HealthOmics workflows.
-
ECR container images: Create container images for the workflow in a private ECR repository, or synchronize images from a supported upstream registry with your Amazon ECR private repository.
-
(Optional) Sentieon licenses: Request a Sentieon license to use the Sentieon software in private workflows.
For more information, see Creating or updating a private workflow in Amazon Web Services HealthOmics in the Amazon Web Services HealthOmics User Guide.
Parameters:
-
name(Optional[WorkflowName], default:None) –Name (optional but highly recommended) for the workflow to locate relevant information in the CloudWatch logs and Amazon Web Services HealthOmics console.
-
description(Optional[WorkflowDescription], default:None) –A description for the workflow.
-
engine(Optional[WorkflowEngine], default:None) –The workflow engine for the workflow. By default, Amazon Web Services HealthOmics detects the engine automatically from your workflow definition. Provide a value if you have workflow definition files from more than one engine in your zip file, or to use WDL lenient.
WDL lenient is designed to handle workflows migrated from Cromwell. It supports customer Cromwell directives and some non-conformant logic. For details, see Implicit type conversion in WDL lenient in the Amazon Web Services HealthOmics User Guide.
-
definition_zip(Optional[bytes], default:None) –A ZIP archive containing the main workflow definition file and dependencies that it imports for the workflow. You can use a file with a ://fileb prefix instead of the Base64 string. For more information, see Workflow definition requirements in the Amazon Web Services HealthOmics User Guide.
-
definition_uri(Optional[WorkflowDefinition], default:None) –The S3 URI of a definition for the workflow. The S3 bucket must be in the same region as the workflow.
-
main(Optional[WorkflowMain], default:None) –The path of the main definition file for the workflow. This parameter is not required if the ZIP archive contains only one workflow definition file, or if the main definition file is named “main”. An example path is:
workflow-definition/main-file.wdl. -
parameter_template(Optional[WorkflowParameterTemplate], default:None) –A parameter template for the workflow. If this field is blank, Amazon Web Services HealthOmics will automatically parse the parameter template values from your workflow definition file. To override these service generated default values, provide a parameter template. To view an example of a parameter template, see Parameter template files in the Amazon Web Services HealthOmics User Guide.
-
storage_capacity(Optional[int], default:None) –The default static storage capacity (in gibibytes) for runs that use this workflow or workflow version. The
storageCapacitycan be overwritten at run time. The storage capacity is not required for runs with aDYNAMICstorage type. -
tags(Optional[TagMap], default:None) –Tags for the workflow. You can define up to 50 tags for the workflow. For more information, see Adding a tag in the Amazon Web Services HealthOmics User Guide.
-
request_id(WorkflowRequestId) –An idempotency token to ensure that duplicate workflows are not created when Amazon Web Services HealthOmics submits retry requests.
-
accelerators(Optional[Accelerators], default:None) –The computational accelerator specified to run the workflow.
-
storage_type(Optional[StorageType], default:None) –The default storage type for runs that use this workflow. The
storageTypecan be overridden at run time.DYNAMICstorage dynamically scales the storage up or down, based on file system utilization.STATICstorage allocates a fixed amount of storage. For more information about dynamic and static storage types, see Run storage types in the Amazon Web Services HealthOmics User Guide. -
container_registry_map(Optional[ContainerRegistryMap], default:None) –(Optional) Use a container registry map to specify mappings between the ECR private repository and one or more upstream registries. For more information, see Container images in the Amazon Web Services HealthOmics User Guide.
-
container_registry_map_uri(Optional[Uri], default:None) –(Optional) URI of the S3 location for the registry mapping file.
-
readme_markdown(Optional[ReadmeMarkdown], default:None) –The markdown content for the workflow's README file. This provides documentation and usage information for users of the workflow.
-
parameter_template_path(Optional[ParameterTemplatePath], default:None) –The path to the workflow parameter template JSON file within the repository. This file defines the input parameters for runs that use this workflow. If not specified, the workflow will be created without a parameter template.
-
readme_path(Optional[ReadmePath], default:None) –The path to the workflow README markdown file within the repository. This file provides documentation and usage information for the workflow. If not specified, the
README.mdfile from the root directory of the repository will be used. -
definition_repository(Optional[DefinitionRepository], default:None) –The repository information for the workflow definition. This allows you to source your workflow definition directly from a code repository.
-
workflow_bucket_owner_id(Optional[WorkflowBucketOwnerId], default:None) –The Amazon Web Services account ID of the expected owner of the S3 bucket that contains the workflow definition. If not specified, the service skips the validation.
-
readme_uri(Optional[S3UriForObject], default:None) –The S3 URI of the README file for the workflow. This file provides documentation and usage information for the workflow. Requirements include:
-
The S3 URI must begin with
s3://USER-OWNED-BUCKET/ -
The requester must have access to the S3 bucket and object.
-
The max README content length is 500 KiB.
-
Raises:
-
AccessDeniedException–You do not have sufficient access to perform this action.
-
ConflictException–The request cannot be applied to the target resource in its current state.
-
InternalServerException–An unexpected error occurred. Try the request again.
-
RequestTimeoutException–The request timed out.
-
ResourceNotFoundException–The target resource was not found in the current Region.
-
ServiceQuotaExceededException–The request exceeds a service quota.
-
ThrottlingException–The request was denied due to request throttling.
-
ValidationException–The input fails to satisfy the constraints specified by an Amazon Web Services service.
-
UnknownServiceError–The service returned an error code this client does not model.
Source code in docs_src/capo_omics/_services/async_omics.py
7134 7135 7136 7137 7138 7139 7140 7141 7142 7143 7144 7145 7146 7147 7148 7149 7150 7151 7152 7153 7154 7155 7156 7157 7158 7159 7160 7161 7162 7163 7164 7165 7166 7167 7168 7169 7170 7171 7172 7173 7174 7175 7176 7177 7178 7179 7180 7181 7182 7183 7184 7185 7186 7187 7188 7189 7190 7191 7192 7193 7194 7195 7196 7197 7198 7199 7200 7201 7202 7203 7204 7205 7206 7207 7208 7209 7210 7211 7212 7213 7214 7215 7216 7217 7218 7219 7220 7221 7222 7223 7224 7225 7226 7227 7228 7229 7230 7231 7232 7233 7234 7235 7236 7237 7238 7239 7240 7241 7242 7243 7244 7245 7246 7247 7248 7249 7250 7251 7252 7253 7254 7255 7256 7257 7258 7259 7260 7261 7262 7263 7264 7265 7266 7267 7268 7269 7270 7271 7272 7273 7274 7275 7276 7277 7278 7279 | |