> For the complete documentation index, see [llms.txt](https://help.connected.illumina.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.connected.illumina.com/dragen/dragen-v4.6/getting-started/quickstart/cloud-fpga-byol.md).

# Cloud FPGA on AWS

Cloud FPGA on AWS runs FPGA-accelerated DRAGEN on a supported AWS FPGA instance in your AWS account.

Choose this deployment when you need FPGA turnaround time while retaining control of your AWS infrastructure and data.

{% hint style="info" %}
This deployment is technical in nature. It assumes you are comfortable working with AWS services, including EC2 instances, AMIs, EBS volumes, IAM permissions, and SSH access to Linux servers.
{% endhint %}

## Before you start

| You need         | Notes                                                                                             |
| ---------------- | ------------------------------------------------------------------------------------------------- |
| An AWS account   | You need permission and quota to launch supported FPGA instances and attach storage.              |
| DRAGEN software  | Download the DRAGEN software and FPGA hardware-driver RPMs from the DRAGEN - Getting Started app. |
| DRAGEN licensing | For new deployments, use a BioInsight Platform API key.                                           |
| Network access   | The instance must reach `license.dragen.illumina.com` and the AWS Instance Metadata Service.      |
| Fast storage     | Use local instance storage or attached EBS storage for references, temporary files, and output.   |

## Launch and run

The steps below are the short path to a first run. For the full reference on this deployment, see [DRAGEN on AWS](/dragen/dragen-v4.6/reference/dragen-multi-cloud/dragen-on-aws.md).

{% stepper %}
{% step %}

## Build your DRAGEN AMI

Create your own DRAGEN Amazon Machine Image (AMI) so that every instance you launch already has DRAGEN installed.

1. Launch an instance from a base AMI. Illumina recommends Rocky Linux 8.x.
2. Open the **DRAGEN - Getting Started** app from the Illumina BioInsight Platform home page, or go to [dragen.illumina.com](https://dragen.illumina.com). Download the DRAGEN software RPMs and FPGA hardware-driver RPMs for DRAGEN v4.6, or copy their download links to fetch the RPMs directly on the instance.
3. On the instance, import the Illumina DRAGEN GPG public key and install both RPMs.
4. Create an AMI from the instance.

See [Building your own DRAGEN AMI](/dragen/dragen-v4.6/reference/dragen-multi-cloud/dragen-on-aws.md#building-your-own-dragen-ami) for the full procedure, including the RPM names and base image selection.
{% endstep %}

{% step %}

## Launch an FPGA instance

Launch an FPGA-powered EC2 instance from the DRAGEN AMI you built.

Attach fast storage as well. Illumina recommends 2 TB of EBS storage as four 500 GB GP3 volumes in RAID 0.

See [Launch an Instance](/dragen/dragen-v4.6/reference/dragen-multi-cloud/dragen-on-aws.md#launch-an-instance) for instance type and storage guidance.
{% endstep %}

{% step %}

## Connect and mount storage

Connect over SSH. Use `rocky` for Rocky Linux images, or `ec2-user` for other EL8 images.

Mount your volumes at `/staging`. DRAGEN reads and writes intermediate files quickly, so this must be the fast file system.

See [Connect to and Configure Your Instance](/dragen/dragen-v4.6/reference/dragen-multi-cloud/dragen-on-aws.md#connect-to-and-configure-your-instance) for the exact `mdadm` commands, including a worked four-volume RAID 0 example.
{% endstep %}

{% step %}

## Set up licensing

API-key licensing is recommended, see [DRAGEN API Key Licensing](/dragen/dragen-v4.6/reference/licensing/api_key_licensing.md).
{% endstep %}

{% step %}

## Download a reference and run

Download the reference hash table for your DRAGEN version to `/staging`, then run `dragen` against your FASTQ files.

DRAGEN can also read large inputs straight from S3 or a presigned URL. See [Data Flow](/dragen/dragen-v4.6/reference/dragen-multi-cloud/dragen-on-aws.md#data-flow).

For a complete, copy-ready example that downloads a public reference and test sample, see [Simple Run Example](/dragen/dragen-v4.6/reference/dragen-multi-cloud/dragen-on-aws.md#simple-run-example).
{% endstep %}
{% endstepper %}

## Confirm success

DRAGEN exits with code 0 on success and writes output files to the directory you specified. Check that `<prefix>.hard-filtered.vcf.gz` and `<prefix>.metrics.json` are present in the output directory.

To confirm the FPGA hardware and bitstream are operating before your first run, run `self_test.sh`. See [Confirm the installation](/dragen/dragen-v4.6/reference/dragen-multi-cloud.md#confirm-the-installation).

## What a run costs

The cost depends on the licensing method:

* DRAGEN v4.6 API-key runs are priced based on DRAGEN Pricing and consume BioInsight Credits. For human samples, the charge is per sample.
* AWS compute, storage, and data-transfer charges are billed separately by AWS.

See [DRAGEN Pricing and Licensing](/dragen/dragen-v4.6/reference/licensing.md).

## Next steps

* Read the full deployment reference in [DRAGEN on AWS](/dragen/dragen-v4.6/reference/dragen-multi-cloud/dragen-on-aws.md).
* Automate many samples with [DRAGEN on AWS Batch](/dragen/dragen-v4.6/reference/dragen-multi-cloud/dragen-on-aws-batch.md).

For help, see [Support](/dragen/dragen-v4.6/reference/technical-assistance.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.connected.illumina.com/dragen/dragen-v4.6/getting-started/quickstart/cloud-fpga-byol.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.