AWS omics documentation change
Summary
Added documentation section 'Using Amazon Q CLI with HealthOmics' explaining integration with generative AI tool and IAM requirements
Security assessment
The change adds documentation about configuring IAM permissions for Amazon Q CLI to access HealthOmics and other services, which relates to security best practices for access control. However, there is no evidence of addressing a specific security vulnerability.
Diff
diff --git a/omics/latest/dev/setting-up-new.md b/omics/latest/dev/setting-up-new.md index 41aa2326c..1b480992c 100644 --- a//omics/latest/dev/setting-up-new.md +++ b//omics/latest/dev/setting-up-new.md @@ -5 +5 @@ -Sign up for an AWS accountCreate a user with administrative accessCreate IAM permissions for HealthOmics +Sign up for an AWS accountCreate a user with administrative accessCreate IAM permissions for HealthOmicsUsing Amazon Q CLI with HealthOmics @@ -18,0 +19,2 @@ To set up AWS HealthOmics, sign up for an AWS account, create an administrative + * Using Amazon Q CLI with HealthOmics + @@ -107,0 +110,6 @@ For more information about configuring IAM permissions for HealthOmics, see [IAM +## Using Amazon Q CLI with HealthOmics + +Amazon Q CLI provides natural language interactions with AWS HealthOmics, allowing you to perform complex genomic workflows and analysis tasks using conversational commands. To use Amazon Q CLI, be sure to configure IAM permissions for HealthOmics and other services (such as CloudWatch, Amazon ECR, or Amazon S3) for Amazon Q to access their resources. + +The [HealthOmics Agentic generative AI tutorial](https://github.com/aws-samples/aws-healthomics-tutorials/tree/main/generative-ai) provides a step-by-step guidance for configuring context files and enabling Amazon Q CLI to create, run, and optimize your AWS HealthOmics workflows. +