AWS omics documentation change
Summary
Added a new 'VPC networking' section that explains how to configure runs to use VPC networking, including an example command and a link to detailed documentation.
Security assessment
The change adds documentation for configuring VPC networking for runs, which is a security feature that enables network isolation and controlled access. This enhances security but does not address a specific vulnerability.
Diff
diff --git a/omics/latest/dev/starting-a-run.md b/omics/latest/dev/starting-a-run.md index 2c3c80807..f434c769b 100644 --- a//omics/latest/dev/starting-a-run.md +++ b//omics/latest/dev/starting-a-run.md @@ -5 +5 @@ -HealthOmics run parametersStarting a run using the consoleStarting a run using the APIGet information about a run +HealthOmics run parametersStarting a run using the consoleStarting a run using the APIGet information about a runVPC networking @@ -34,0 +35,2 @@ You specify an IAM service role when you start a run. Optionally, the console ca + * VPC networking + @@ -278,0 +281,15 @@ Run metadata isn't deleted if it's not present in the CloudWatch logs. +## VPC networking + +You can configure a run to use VPC networking, which allows runs to access resources over the public internet or private networks. Specify the networking mode and a configuration name when you start the run: + + + aws omics start-run \ + --workflow-id workflow-id \ + --role-arn role-arn \ + --output-uri s3://bucket-name/prefix/ \ + --networking-mode VPC \ + --configuration-name configuration-name \ + --region region + +For more information, see [Connecting HealthOmics workflows to a VPC](./workflows-vpc-networking.html). +