Hi team, hope all is well. When configuring Metaflow using the output json from the Terraform stack like so: "metaflow configure import <point to the output file from Terraform>", why does another config file get created? and which config file is being used? Please see screenshot below, seems like the metaflow CLI duplicates the config

it uses

config.json

by default but you can use

config_poc.json

by specifying

METAFLOW_PROFILE=poc

Hi there, list permission denied error. I have the env var METAFLOW_PROFILE=poc. Is there something specific I need to setup on profile ~/.aws/credentials? On this I've setup aws credentials with a profile poc too, but is there a specific role, since I'm just using an admin role. It is here where I'm having the confusion between what metaflow config is required and what aws config is required and how metaflow authenticates to the provisioned AWS stack

thanks for the context. Here's a simple way to think about it: • Metaflow doesn't do any authorization and authentication by itself. Hence

METAFLOW_PROFILE

only configures things pertaining to Metaflow, like where its data should be stored, where to find the metadata service etc • To make Metaflow work, you need to have IAM roles and credentials set up so that you can access the buckets and other resources specified in the Metaflow config (through

METAFLOW_PROFILE

). This is where

AWS_PROFILE

comes in.

thank you