AWS omics documentation change
Summary
Reorganized content, added 'Subscribing to shared workflow' section, and warned about version-level access control limitations in shared workflows
Security assessment
Explicitly advises using separate workflows instead of versions for access control, which improves security guidance. However, this appears preventative rather than addressing a known exploit.
Diff
diff --git a/omics/latest/dev/sharing-workflows.md b/omics/latest/dev/sharing-workflows.md index 6663cd1c2..70061c4cf 100644 --- a//omics/latest/dev/sharing-workflows.md +++ b//omics/latest/dev/sharing-workflows.md @@ -5 +5 @@ -Monitoring status of a workflow shareSharing a private workflow using the consoleSharing a private workflow using the CLIAccepting a shared workflow using the consoleRunning a shared workflow using the consoleRunning a shared workflow using the API +Subscribing to a shared workflow Monitoring status of a workflow shareSharing a private workflow using the consoleSharing a private workflow using the CLIAccepting a shared workflow using the consoleRunning a shared workflow using the consoleRunning a shared workflow using the API @@ -16,0 +17,23 @@ HealthOmics automatically allows a shared workflow to access the Amazon ECR repo +When you share a workflow, the subscriber can use any of the workflow versions. If you need version-level access control for a shared workflow, we recommend that you create separate workflows rather than using workflow versions. + +###### Topics + + * Subscribing to a shared workflow + + * Monitoring status of a workflow share + + * Sharing a private workflow using the console + + * Sharing a private workflow using the CLI + + * Accepting a shared workflow using the console + + * Running a shared workflow using the console + + * Running a shared workflow using the API + + + + +## Subscribing to a shared workflow + @@ -55,17 +77,0 @@ See [Cross-account resource sharing in AWS HealthOmics](./resource-sharing.html) -###### Topics - - * Monitoring status of a workflow share - - * Sharing a private workflow using the console - - * Sharing a private workflow using the CLI - - * Accepting a shared workflow using the console - - * Running a shared workflow using the console - - * Running a shared workflow using the API - - - -