Carlo
10/11/2022, 8:28 PMKalise Richmond
10/11/2022, 8:44 PMCarlo
10/11/2022, 8:50 PMJeff Hale
10/11/2022, 8:50 PMCarlo
10/11/2022, 8:54 PMECSAgent
Kalise Richmond
10/11/2022, 9:05 PMCarlo
10/13/2022, 6:54 PMrun_task_kwargs_path
which we used to specify a list of subnets. We would run 2 agents in 1 subnet. When an agent submitted a task, each submitted w/ a different set of subnets (private vs public) all in the same vpc. In the current model, I see how to set subnets for the agent, but not for where the agent launches a task. Looking at the source for EcsTask, I think it's only configurable via vpcId, but these subnet sets share the same vpc
2. If the agent requires the AwsCredentials block to launch the task, and the environment requires a sessionToken does this mean we need to run a process to periodically refresh the session token stored on disk for the block. I believe in the past this wasn't necessary because the ecs agent was long lived, and authenticated on startup. Now it seems the agents pick up flow runs from deployments which carry along a block with aws info like creds, so I'm not sure if the agent would remain aws authenticated
3. For different ecs task combinations of memory and cpu, we would need to have an ecs block for each, then bind that to the deployment. correct?Jeff Hale
10/17/2022, 5:51 PMZanie
10/17/2022, 5:55 PMCarlo
10/17/2022, 6:39 PM