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

Vertex AI Pipelines Uses Default Project Compute ServiceAccount #43

Open
sosoihd opened this issue Feb 16, 2024 · 1 comment
Open

Vertex AI Pipelines Uses Default Project Compute ServiceAccount #43

sosoihd opened this issue Feb 16, 2024 · 1 comment

Comments

@sosoihd
Copy link

sosoihd commented Feb 16, 2024

Capture d’écran 2024-02-16 à 16 26 54

Description:

I'm currently using the Alphafold Portal on GCP with Vertex AI inference pipelines. However, I noticed that the pipelines consistently use the default compute service account, which is disabled in our organization. This raises security concerns and violates best practices.

Proposed Solution:

I propose adding an environment variable to the Alphafold Portal configuration that allows users to specify a different service account for running Vertex AI inference pipelines. This would enable users to utilize authorized and managed service accounts, enhancing security and compliance.

Benefits:

Improved Security: Users can leverage designated service accounts with restricted permissions, minimizing potential damage in case of compromise.
Compliance Adherence: Organizations can enforce granular access control aligned with their security policies.
Flexibility: Users gain the ability to manage and rotate service accounts independently, catering to various security needs.

@sosoihd
Copy link
Author

sosoihd commented Feb 18, 2024

Hello @yudyhendry
I would like to submit a pull request to add this feature.

I'm not able to push my branch to the repo, how can I get access ?

Thank you

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

1 participant