search

awslabs / genomics-secondary-analysis-using-aws-step-functions-and-aws-batch

This solution provides a framework for Next Generation Sequencing (NGS) genomics secondary-analysis pipelines using AWS Step Functions and AWS Batch.
https://aws.amazon.com/solutions/implementations/genomics-secondary-analysis-using-aws-step-functions-and-aws-batch/
Apache License 2.0
38 stars 22 forks source link

Where in the code can I increase the size of the persistant EC2 volume? #8

Open spitfiredd opened 3 years ago

spitfiredd commented 3 years ago

The ec2 volume is currently 1000 GB in size and it's insufficient to run some of my jobs, I am trying to see in the code where I can increase it.

sachalau commented 3 years ago

I think you mean 100GB not 1000GB ? This is defined on the LaunchTemplate associated with the Batch Compute Environment in cfn/batch.yaml.

I think you will need to associate the latest version of the LaunchTemplate instead of the default one if you want your EC2 instances using the updated version automatically

Also did you have a look at the AWS Genomics CLI tool released last week ?

sachalau commented 3 years ago

Actually sorry I forgot that you can't change a launchtemplate associated with a compute environment.

https://docs.aws.amazon.com/batch/latest/userguide/launch-templates.html

AWS Batch doesn't support updating a compute environment with a new launch template version. If you update your launch template, you must create a new compute environment with the new template for the changes to take effect.

You have to create a new compute env after you have updated your template versions. No need to create a new queue however, you can just replace the compute env.