I'd like to understand dagster ECSrunlauncher and what it means by "task" - if I materialize an asset that depends on upstream assets A->B->C - if I have a singleton created in A - would C be able to access the state generated in A? Or is each asset materialization run on a different ECS task - and C can't know what A created in memory. How do we securely keep auth tokens generated in A's task for C? We can't auth too many times (the api we are working with will not permit it). Even if we made a resource rather than a singleton - the state wouldn't persist across ecs tasks. How are people solving this issue? Posted in #dagster-support