Question: How to associate a bucket for a future FSx for Lustre file system to quickly repopulate the reference data?

[LanceWesterhoff]

Great job with this environment! It is [almost] exactly what we need. This may be a basic question, but we only need occasional folding predictions. If I understand the FSx for Lustre file system pricing, we're paying for the Lustre filesystem regardless of whether we're actually running any folding predictions. In your instructions, you note the following:

To remove the stack and stop further charges, first slect the root stack from the CloudFormation console and then the Delete button. This will remove all resources EXCEPT for the S3 bucket containing job data and the FSx for Lustre backup. You can associate this bucket as a data repository for a future FSx for Lustre file system to quickly repopulate the reference data.

What is the best practice to accomplish this? It would seem we need to:

• Run Launch the Stack once to create run the default download for the database and populate the FSx for Lustre file system.
• Then we need to some how get the data in the Lustre file system to S3. How do we do that?
• Then we need to remove the stack (which as per the note above, should remove everything except for the S3 bucket containing the above noted data).
• Finally, when we want to perform another prediction, we should run something to create the Stack again (perhaps the batch-protein-folding-cfn-packaged.yaml again?) but instead of performing the 5hr download, it should pull from the S3 bucket, right? How do we communicate this to the YAML script? Is there already an option to perform this step (which I'm missing)?

Thanks for your help!