I’m trying to use the ECS Launcher. In my

dagster.yaml

I have the launcher setup like below

run_launcher:
  module: dagster_aws.ecs.launcher
  class: ECSRunLauncher
  config:
    key_id:
      env: AWS_ACCESS_KEY_ID
    access_key:
      env: AWS_SECRET_ACCESS_KEY
    region_name:
      env: AWS_DEFAULT_REGION
    imagename:
      env: ECR_IMAGE
    family: dagit
    memory: 256
    cpu: 512
    grab_logs: False

I’m running into this error

Error 1: Invalid scalar at the root. Value "FARGATE" of type "<class 'str'>" is not valid for expected type "Bool".

which I’m guessing is due to the default for grab_logs is a string rather than a boolean. https://github.com/dagster-io/dagster/blob/master/python_modules/libraries/dagster-aws/dagster_aws/ecs/launcher.py#L140 That minor issue aside I’m not sure when I run

dagit

it picks up I want to use a non standard launcher but isn’t overriding the default value since I have that set.

ya … the construction path isn’t test in master at all - ill get a fix in for the release on thursday

Question. I saw that you pushed some changes for the

ECSRunLauncher

. If I update to 0.9.15 would this be enough for this to be working or as the commit suggests is this just a step

if you have time you could try it out and report back any errors - it will go out in the release tomorrow but you could also just make a local copy to load from or pip install from git hash or something @max was hoping to get some time early next week to get it over the line

Thanks again for the ECS launcher updates in 0.9.15. I made a few tweaks and got it to launch Fargate tasks (I still need to work out some AWS permissions for them to run correctly). However I’m getting this error that I’m less sure how to deal with

AttributeError: 'NoneType' object has no attribute 'run_id'
  File "/Users/dennishume/code/dagster/env/lib/python3.7/site-packages/dagster_graphql/implementation/utils.py", line 14, in _fn
    return fn(*args, **kwargs)
  File "/Users/dennishume/code/dagster/env/lib/python3.7/site-packages/dagster_graphql/implementation/execution/launch_execution.py", line 19, in launch_pipeline_execution
    return _launch_pipeline_execution(graphene_info, execution_params)
  File "/Users/dennishume/code/dagster/env/lib/python3.7/site-packages/dagster_graphql/implementation/execution/launch_execution.py", line 52, in _launch_pipeline_execution
    run=graphene_info.schema.type_named("PipelineRun")(run)
  File "/Users/dennishume/code/dagster/env/lib/python3.7/site-packages/dagster_graphql/schema/runs.py", line 131, in __init__
    runId=pipeline_run.run_id, status=pipeline_run.status, mode=pipeline_run.mode

Also is this something better suited for Github discussions?

ahh ok i think i know whats going on here - so

the scheme is that it is assumed that the launch destination and source are using the same dagster instance - have access to the same database

so in your launch destination - the far gate task container - needs to have

DAGSTER_HOME

&

dagster.yaml

set up to point at the same instance you are launching form - configured to use an RDS database or whatever

any luck?