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
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: