Bring Your Own Bucket

This feature is only related to saving Dragen output files in your own bucket when using Dragen through Emedgene (without ICA).

If you are looking to:

• Import data from AWS S3 to Emedgene go to Manage data storages

• Integrating any data storage to Emedgene go to Manage data storages

• Download any data from Emedgene go to Manage S3 credentials

---

Bring your own bucket is only available for Enterprise level support accounts and require Illumina support for setup

---

Bring Your Own Bucket

Bring Your Own Bucket, also known as BYOK, enables you to control your DRAGEN file outputs.

Emedgene managed DRAGEN solution saves the DRAGEN output files in a detected AWS S3 bucket that you have access to using your S3 credentials.

However, if you have an Enterprise account and you would like Emedgene managed dragen solution to save the DRAGEN output files in your own bucket, reach out to [e-mail] and follow this steps:

1. Create an AWS bucket

Emedgene requires access to the root folder, which means a dedicated bucket might be appropriated.

2. Edit Bucket policy

Bucket policy should allow Emedgene user access to the bucket.

Example bucket policy:

{
    Coming Soon
}

3. Allow illumina.com and emedgene.com for CORS

Emedgene visualizes data in IGV directly from your AWS S3 bucket. In order to do it, you should enable CORS for the emedgene application URLs.

Example CORS policy:

{
    Coming Soon
}

4. Test and validate the configuration with Illumina support

We will require to run a case and validate the managed DRAGEN pipeline finish successfully and all features are available in the platform.

The BYOB solution means you managed your own data, meaning if you accidentally deleted or moved the data the integration with Emedgene might break. You are responsible for your DRP and data backup solutions.

---

Managing AWS S3 Lifecycle policy

If a customer enables an AWS S3 Lifecycle policy in order to archive or change the S3 tiers for different files, they might create an adverse effect on the platform.

Case Type	File Type	Expected effect
FASTQ	FASTQ/BAM/CRAM (input)	Reanalysis will fail (will be fixed)
FASTQ	CRAM (Output)	Reanalysis will fail
FASTQ	VCFs	Reanalysis will fail
FASTQ	CSV, etc	Reanalysis will fail
VCF	BAM/CRAM (visualizations)	Visualization will fail
VCF	VCF (input)	Reanalysis will fail
VCF	CSV, etc	Reanalysis will fail (will be fixed)