Refactors SCHISM FIM workflow to use AWS Batch w/EC2 compute environment rather than Lambda to save costs #722
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The SCHISM FIM processing was previously designed to multi-process across Lambda functions. This was amounting to the single most costly line item in HydroVIS. Thus, we looked into different options and settled on switching to using AWS Batch to distribute the processing across a few EC2 machines.
At a high level, this PR does the following: