Page MenuHomeElementl

Include ENI infornmation in ECS task stubs
ClosedPublic

Authored by jordansanders on Jun 18 2021, 8:08 PM.
Tags
None
Referenced Files
Unknown Object (File)
Sat, Jul 2, 3:32 AM
Unknown Object (File)
Tue, Jun 28, 7:20 PM
Unknown Object (File)
Tue, Jun 28, 7:10 PM
Unknown Object (File)
Sun, Jun 26, 1:16 PM
Unknown Object (File)
Fri, Jun 24, 10:10 AM
Unknown Object (File)
Sun, Jun 12, 7:12 PM
Unknown Object (File)
Fri, Jun 10, 6:05 AM
Unknown Object (File)
Mon, Jun 6, 7:44 PM
Subscribers
None

Details

Summary

To run a new awsvpc Fargate task, we need to provide it with networking
configuration at launch. Providing just a subnet passes validation and
launches the task but you can't do a whole lot with it without also
passing at least one security group.

We're currently following a strategy where we inherit networking
configuration from a "parent" task and create a new task using the same
information. Unfortunately, security groups aren't part of the task
metadata. Instead, we have to get the security group from the network
interface.

However, ECS infers the network interface from the subnet. So we need
to:

  1. Pass in a subnet to launch a task
  2. Our stub then needs to look up the network interface associate with that subnet. Hence the EC2 client being added to the ECS stub. It will then tag the network interface on the task stub.
  3. Our EcsRunLauncher then needs to look up the security group from the network interface. Hence the EC2 client being added to the EcsRunLauncher.
Test Plan

unit

Diff Detail

Repository
R1 dagster
Lint
Lint Not Applicable
Unit
Tests Not Applicable