Design considerations - Guidance for Multi-Omics and Multi-Modal Data Integration and Analysis on AWS

Design considerations

This guidance fully leverages infrastructure as code principles and best practices that allow you to rapidly evolve the guidance. Storing your Extract Transform and Load (ETL) job, crawler, and data lake definitions as code makes them easier to share, inspect for compliance, and reproduce. Additionally, each change you make is tracked by the CI/CD pipeline, facilitating change control management, rollbacks, and auditing.

Regional deployment

This guidance uses the AWS CodePipeline service, which is currently available in specific AWS Regions only. Therefore, you must launch this guidance in an AWS Region where this service is available. For the most current service availability by AWS Region, refer to the AWS Regional Services List. The guidance has been tested in all Regions.