Use custom launch container

Note

This feature requires Tower 20.10.2 or later.

Tower automatically registers an AWS Batch Job definition to launch pipelines with the required Nextflow runtime pulling the container image on demand.

If you need to manage this manually, create a Job definition in your AWS Batch environment, using the following settings:

  • name: any of your choice
  • image: the nf-launcher image reported in the Availability section in the file.
  • vcpus: 1
  • memory: 1000
  • command: true

Once the job definition is registered, set in the Tower environment configuration the following variable:

1
TOWER_LAUNCH_CONTAINER=job-definition://YOUR_JOB_DEF_NAME

Replacing the YOUR_JOB_DEF_NAME placeholder with the name or your Batch Job definition.

Back to top