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

executor: setup credentials #6269

Closed
Tracked by #6440
dberenbaum opened this issue Jul 1, 2021 · 4 comments
Closed
Tracked by #6440

executor: setup credentials #6269

dberenbaum opened this issue Jul 1, 2021 · 4 comments
Labels
A: executors Related to the executors feature

Comments

@dberenbaum
Copy link
Collaborator

Meta-issue. Please link related tickets back to this one.

User story

I want my executor to have all the credentials and configurations I need to access my data and run my code.

Requirements

  • The executor has credentials to access the remote through some pattern that is documented and doesn't require manual intervention on the executor instance.
  • All reasonable security precautions are taken and risks are noted for docs.

Out of scope

It's not yet necessary to handle all possible authorization patterns, although design flexibility for the future should be considered.

@dberenbaum dberenbaum added the A: executors Related to the executors feature label Jul 1, 2021
@dberenbaum dberenbaum changed the title Setup credentials executor: setup credentials Jul 1, 2021
@dberenbaum
Copy link
Collaborator Author

Conversation between @pmrowla and me:

@pmrowla:

By credentials here, do we specifically mean a users --local DVC remote config settings?

If a user is setting credentials in an aws profile, and is only configuring the --local profile field for their S3 remote, that profile won't actually exist in the remote machine without the associated .aws/config

(but copying an entire .aws/config and the associated access keys seems like it would be beyond the scope of what DVC should be doing here)

@dberenbaum:

We need to think about all of that. How would you envision getting .aws/config and .aws/credentials set up in the executor?

@pmrowla:

So in this example, users should be running an in amazon ec2 instance configured with the right IAM role for accessing their S3 bucket (so that when the instance boots, it is automatically configured with the appropriate S3 credentials/aws profile without DVC being involved in the process at all)

AFAIK azure and google have equivalent configurations, (and all of this assumes that the user is using matching cloud storage + cloud execution platforms)

In the event that a user wants to run DVC on an azure machine but use S3 for storage, they should be required to configure a container with appropriate auth credentials themselves

@casperdcl
Copy link
Contributor

FYI template which is useful for implementation: https://github.com/iterative/dvc-tpi/blob/main/run.py

@dberenbaum
Copy link
Collaborator Author

If we start with transfer over ssh, we can deprioritize this story for now.

@dberenbaum dberenbaum mentioned this issue Aug 16, 2021
8 tasks
@dberenbaum
Copy link
Collaborator Author

Needs rescoping

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A: executors Related to the executors feature
Projects
None yet
Development

No branches or pull requests

2 participants