Exposed ModelArts functions are controlled through IAM permissions. For example, if you as an IAM user need to create a training job on ModelArts, you must have the modelarts:trainJob:create permission.
ModelArts must access other services for AI computing. For example, ModelArts must access OBS to read your data for training. For security purposes, ModelArts must be authorized to access other cloud services. This is agency authorization.
ModelArts provides one-click auto authorization. You can quickly configure agency authorization on the Global Configuration page of ModelArts. Then, ModelArts will automatically create an agency for you and configure it in ModelArts.
In this mode, the authorization scope is specified based on the preset system policies of dependent services to ensure sufficient permissions for using services. The created agency has almost all permissions of dependent services. If you want to precisely control the scope of permissions granted to an agency, use custom authorization. For details about permissions management, see Basic Concepts.
This section introduces one-click auto authorization. This mode allows you to grant permissions to IAM users, federated users (virtual IAM users), agencies, and all users with one click.
Parameter |
Description |
---|---|
Authorized User |
Options: IAM user, Federated user, Agency, and All users
|
Authorized To |
This parameter is not displayed when Authorized User is set to All users.
|
Agency |
|
Add agency > Agency Name |
The system automatically creates a changeable agency name. |
Add agency > Permissions > Common User |
Common User provides the permissions to use all basic ModelArts functions. For example, you can access data, and create and manage training jobs. Select this option generally. Click View permissions to view common user permissions. |
Add agency > Permissions > Custom |
If you need refined permissions management, select Custom to flexibly assign permissions to the created agency. You can select permissions from the permission list as required. |
You can view the configured authorizations on the Global Configuration page. Click View Permissions in the Authorization Content column to view the permission details.
When setting the minimum authorization scope, you can select either Global services or All resources. If you select All resources, the selected permissions will be applied to all resources.
To better manage your authorization, you can delete the authorization of an IAM user or delete the authorizations of all users in batches.
On the Settings page, the authorizations configured for IAM users under the current account are displayed. You can click Delete in the Operation column to delete the authorization of a user. After the deletion takes effect, the user cannot use ModelArts functions.
On the Settings page, click Delete Authorization above the authorization list to delete all authorizations of the current account. After the deletion, the account and all IAM users under the account cannot use ModelArts functions.
On the Add Authorization page, set Agency to Add agency and select Common User, which provides the permissions to use all basic ModelArts functions. For example, you can access data, and create and manage training jobs. Select this option generally.
Access key authorization on the global configuration page has been discontinued. If you used an access key for authorization before, switch to agency authorization. To do so, click Clear Authorization on the Global Configuration page and use an agency for authorization.
You will need to obtain an access key if you are using access key authentication to access certain functions like logging in to PyCharm Toolkit or VS Code, or using real-time services. For details, see How Do I Obtain an Access Key?
Go to the IAM console, click Agencies in the navigation pane, and delete the target agency.