检测到您已登录华为云国际站账号，为了您更好的体验，建议您访问国际站服务网站 https://www.huaweicloud.com/intl/zh-cn
不再显示此消息
检测到您已登录华为云国际站账号，为了您更好的体验，建议您访问国际站服务网站 https://www.huaweicloud.com/intl/zh-cn
不再显示此消息
Why Cannot IAM Users Configure Image Synchronization? Currently, only accounts and IAM users with administrator permissions can configure image synchronization. IAM users without administrator permissions will be able to configure image synchronization in later versions.
IAM user IAM users are created with an account to use cloud services. Each IAM user has their own identity credentials (passwords and access keys) and uses cloud resources based on assigned permissions. IAM users cannot make payments themselves.
With IAM, you can: Create IAM users or user groups for personnel based on your enterprise's organizational structure. Each IAM user has their own identity credentials for accessing SWR resources.
IAM helps you secure access to your Huawei Cloud resources. With IAM, you can create IAM users and grant them permission to access only specific resources.
For example, to obtain an IAM token in the CN-Hong Kong region, obtain the endpoint of IAM (iam.ap-southeast-1.myhuaweicloud.com) for this region and the resource-path (/v3/auth/tokens) in the URI of the API used to obtain a user token.
Figure 1 Changing the access type Authorization Methods IAM users in SWR can have permissions by using either of the following methods: Grant permissions of a specific image to allow IAM users to read, write, and manage the image.
In addition to assigning permissions to users in IAM, the administrator can add, modify, and delete permissions for IAM users in the image details page on SWR console.
With IAM, you can: Create IAM users for employees based on your enterprise's organizational structure. Each IAM user will have their own security credentials for accessing SWR resources. Grant only the permissions required for users to perform a specific task.
On the displayed API Credentials page, view the IAM username and IAM user ID. Figure 1 API credentials Parent Topic: Appendixes
For security purposes, create Identity and Access Management (IAM) users and grant them permissions for routine management. User An IAM user is created by an account in IAM to use cloud services. Each IAM user has its own identity credentials (password and access keys).
Before logging in to the IAM console, ensure that you have the permission for accessing IAM service. For details about the authorization mode, see Creating a User Group and Assigning Permissions.
Why Cannot IAM Users Configure Image Synchronization? Can Existing Images Be Automatically Synchronized? Why Cannot I See Images Synchronized to the Target Region After Configuring Image Synchronization?
The same IAM user can access different organizations as long as the user has sufficient permissions, as shown in Figure 1. You can grant different permissions, namely, read, write, and manage, to IAM users under the same account. For details, see User Permissions.
If the IAM user does not have the permission of the target organization, log in using the cloud account and grant the permission to the IAM user. Then, try again.
Before pulling an image, contact the administrator to grant the SWR pull permission on the IAM console. For details, see Permissions Management.
A maximum of two consecutive underscores are allowed. creator_name String IAM username. auth Integer User role. 7: admin. 3: edit. 1: view.
The token can be obtained by calling the IAM API used to obtain a user token. The value of X-Subject-Token in the response header is the user token.
Only IAM users authorized to manage the private images can share images. The users with whom you share your images only have the read-only permission, which only allows them to pull the images. You can share images only with accounts in the same region.
The token can be obtained by calling the IAM API used to obtain a user token. The value of X-Subject-Token in the response header is the user token.
The token can be obtained by calling the IAM API used to obtain a user token. The value of X-Subject-Token in the response header is the user token.
