. 1. Can it just run an existing ECS task definition, or does it always register a new task definition based on the specified family/taskDefinition? 2. If it can just run an existing ECS task definition, what would the minimal necessary arguments be, something like
, assuming AWS credentials are accessible by boto3 via the environment? 3. If it always generates/registers a new task definition, what would the minimal set of required arguments? I could probably go through the process of figuring that out by running
until I get the desired task definition running and then translate that into
arguments. Curious if someone has gone through this process already.
was tricky to do on the command line so we did it via env var). Happy to provide more details if it’s helpful.