Provide helper materials for AWS Batch deployments #33
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…efinitions to run cloudbuster tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
If CB is intended to be deployed on AWS Batch, it might be nice to provide some clues as to how to set up the infrastructure. This is as much a discussion piece as a specific proposal, so I'm putting it up in this initial rough (and non-functioning) state, so that if it's deemed worthwhile, we can collectively guide the work towards something useful, but not too expansive.
The general outlines are to provide some baseline templates for job queue and job definition setup that can provide a minimal working environment, specify a docker image that includes
cloudbuster, and scripts to build and upload that image to ECR as well as deploy the template job def with a reference to the published image.