For posterity’s sake, I thought I might mention that I managed to get an instance of dagster running locally that does not require setting AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY. I bring this up because I was running into (like many others) a

Unable to locate credentials

error when using the provided example code at https://docs.dagster.io/deployment/guides/docker#multi-container-docker-deployment. When using docker-compose to test your dagster instance locally before pushing it to AWS and when you are making any assortment of boto3 calls, you can use the

docker-compose.override.yml

file described here to serve credentials to each one of executors in the cluster. This enables a “closer to production-like” test since this is how AWS serves credentials to ECS containers and the like. I kind of wish some of this was mentioned in the dagster docs or somewhere on the web …