Workspace
ModelArts allows you to create multiple workspaces to develop algorithms and manage and deploy models for different service objectives. In this way, the development outputs of different applications are allocated to different workspaces for simplified management.
Workspace supports the following types of access control:
- PUBLIC: publicly accessible to tenants (including both the tenant account and all its IAM accounts)
- PRIVATE: accessible only to the creator and the tenant account
- INTERNAL: accessible to the creator, the tenant account, and specified IAM users. When the authorization type is set to INTERNAL, specify one or more accessible IAM users.
A default workspace is allocated to each IAM project of each account. The access control of the default workspace is PUBLIC.
Workspace access control allows the access of only certain users. This function can be used in the following scenarios:
- Education: A teacher allocates an INTERNAL workspace to each student and allows the workspaces to be accessed only by specified students. In this way, students can separately perform experiments on ModelArts.
- Enterprises: An administrator creates a workspace for production tasks and allows only O&M personnel to use the workspace, and creates a workspace for routine debugging and allows only developers to use the workspace. In this way, different enterprise roles can use resources only in a specified workspace.
The permission modelarts:workspace:list only works if a resource space is set up. It cannot be used with enterprise projects.
What is your overall rating for this page?
Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot