Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Example of Developer Role #7

Open
stevenhoelscher opened this issue Feb 15, 2022 · 0 comments
Open

Example of Developer Role #7

stevenhoelscher opened this issue Feb 15, 2022 · 0 comments
Assignees

Comments

@stevenhoelscher
Copy link

stevenhoelscher commented Feb 15, 2022

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:

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants