Hi, just doing some exploration work on Metaflow. I'm finding that to successfully run a flow, I needs to be logged in with an aws user/role that has write permission to the Metaflow s3 bucket, else I get an

S3 access denied

error. Just wondering if this is by design or if I have missed something... was under the impression that all the permissions to interact with s3, dynamodb, rds etc are handled by Metaflow as these are part of the Metaflow Infrastructure, and not rely on the user's permission?