Group Structure for AML Workspace Access
Overview
Access to the AML workspace is granted through two main organization-based groups:
- Neoxia (nx) Groups: Located in
NIP-Lakehouse-Infra/terraform/terragrunt/neoxia_groups.yml
- Natural State (ns) Groups: Internal groups defined in
NIP-Lakehouse-Infra/terraform/terragrunt/nip_ns_groups.yml
Group Details
Neoxia (nx) Groups
- Each
nx_users
entry includes user-specific information, such as email and object ID. Here is an example of an nx user structure:yaml nx_users: asi: email: "asaadi@neoxia.deloitte.fr" object_id: "0cf00337-d7c3-4971-be68-7784b05d067f"
ML Groups for AML Workspace Access
The Machine Learning (ML) groups provide specific access levels within the AML workspace:
-
nip_nx_ml_dev
: Access group for development team members working on ML projects. Members of this group have the necessary permissions to develop and test ML models within the AML workspace. -
nip_nx_ml_lead
: Access group for team leads on ML projects. This group is granted higher-level permissions, allowing leads to manage projects, review configurations, and oversee ML development tasks within the AML workspace.
Each group contains user assignments, such as:
nip_nx_ml_lead:
name: nx_ml_lead
users:
- aba
- ear
Group Setup Location
The specific configuration for the Machine Learning (ML) groups is defined within the Terraform/Terragrunt structure, which manages role-based access to ensure only designated users have the necessary permissions for ML resources.
- Configuration Path: ```plaintext terraform/terragrunt/dev/security_groups/org_neoxia/ml_lead
This setup provides role-based access across projects, ensuring only designated users have access to ML resources.