Hey y'all - I've set up my

dagster.yaml

(attached) to include specifications for the run_launcher, run_storage, event_log_storage, schedule_storage, and compute_logs... but I still end up with a local folder called

storage

containing a folder named with the run ID in turn containing folders named for each op. Is there a config I'm missing that affects this?

That sounds like the

io_manager

creating those folders. See https://docs.dagster.io/deployment/dagster-instance#local-artifact-storage for more details.

Thanks, Stefan. I'll try this out.

Stefan is right on. You can also configure a different

io_manager

(e.g.

s3_pickle_io_manager

in

dagster-aws

) if you want to move this off of the local file system (the current default is

fs_io_manager

).

Yep setting up the

s3_pickle_io_manager

took care of this. Thanks y'all!