If you need to assign different permissions to personnel in your enterprise to access your images, Identity and Access Management (IAM) is a good choice for fine-grained permissions management. IAM provides identity authentication, fine-grained permissions management, and access control. IAM helps you secure access to your resources.
With IAM, you can create IAM users and assign permissions to control their access to specific resources. For example, if you want some software developers in your enterprise to use images but do not want them to delete the images or perform any other high-risk operations, you can create IAM users and grant permission to use the images but not permission to delete them.
If your account does not require individual IAM users for permissions management, you can skip this section.
IAM is a free service. You pay only for the resources in your account. For more information about IAM, see IAM Service Overview.
New IAM users do not have any permissions assigned by default. You need to first add them to one or more groups and attach policies or roles to these groups. The users then inherit permissions from the groups and can perform specified operations on cloud services based on the permissions they have been assigned.
IMS is a project-level service deployed for specific regions. When you set Scope to Region-specific projects and select the specified projects in the specified regions, the users only have permissions for images in the selected projects. If you set Scope to All resources, the users have permissions for images in all region-specific projects. When accessing IMS, the users need to switch to the authorized region.
You can grant permissions by using roles and policies.
Role | Description | Dependencies |
|---|---|---|
IMS Administrator | Administrator permissions for IMS | This role depends on the Tenant Administrator role. |
Server Administrator | Permissions for creating, deleting, querying, modifying, and uploading images | This role depends on the IMS Administrator role in the same project. |
A majority of fine-grained policies contain permissions for specific APIs, and permissions are defined using API actions. For the API actions supported by IMS, see Permissions and Supported Actions.
Policy | Description | Dependencies |
|---|---|---|
IMS FullAccess | All permissions for IMS | None |
IMS ReadOnlyAccess | Read-only permissions for IMS. Users with these permissions can only view IMS data. | None |
Table 3 lists the common operations supported by system-defined permissions for IMS.
Operation | IMS FullAccess | IMS ReadOnlyAccess | IMS Administrator (Depending on Tenant Administrator) |
|---|---|---|---|
Creating images | √ | x | √ |
Deleting images | √ | x | √ |
Querying images | √ | √ | √ |
Updating image information | √ | x | √ |