You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When configuring AWS via Metaflow, the only instruction is to configure the AWS CLI:
Metaflow relies on AWS access credentials present on your computer to access resources on AWS.
Before proceeding further, please confirm that you have already configured these access credentials on this computer. [Y/n]: n
There are many ways to setup your AWS access credentials. You can get started by following this guide: https://docs.aws.amazon.com/cli/latest/userguide/cli-chap-configure.html
--
Edit: After spending some more time working with this repository, it seems that this file is a starting point. My approach is to also create aws_iam_policy resources that can be leveraged by both the AWS Batch job role and a developer role.
I would still find more documentation on the AWS IAM permissions model to be incredibly useful -- there's a lot of roles at play in this implementation.
The text was updated successfully, but these errors were encountered:
I'm working on deploying a Metaflow instance to AWS and would find it useful to see an example of what a developer role would look like.
To be honest, I couldn't find much about what IAM policies need to be in-place for a Metaflow developer to carry out various tasks.
For example, to reproduce production issues locally, I'm assuming the user would need S3 read access to the production artifact store.
When configuring AWS via Metaflow, the only instruction is to configure the AWS CLI:
--
Edit: After spending some more time working with this repository, it seems that this file is a starting point. My approach is to also create
aws_iam_policy
resources that can be leveraged by both the AWS Batch job role and a developer role.I would still find more documentation on the AWS IAM permissions model to be incredibly useful -- there's a lot of roles at play in this implementation.
The text was updated successfully, but these errors were encountered: