- What's new
- Function Overview
- Service Overview
- Getting Started
-
User Guide
- Introduction
- Permissions Management
- Basics of the Container Engine
-
Image Management
- Uploading an Image Through a Container Engine Client (Recommended)
- Obtaining a Long-Term Valid Login Command
- Uploading an Image Through SWR Console
- Pulling an Image
- Setting Image Attributes
- Sharing a Private Image
- Adding a Trigger
- Adding an Image Retention Policy
- Configuring Automatic Image Synchronization Between Regions
- Image Center
- Organization Management
- User Permissions
- Auditing
- Change History
- Best Practices
-
API Reference
- Before You Start
- Calling APIs
- API Overview
-
API
- Organization Management
- Managing Image Repositories
- Image Tag Management
- Shared Account Management
- API Version
- Organization Permission Management
- Image Permission Management
- Image Synchronization Management
- Trigger Management
- Image Retention Policy Management
- Temporary Login Command
- Quota Management
- Other
- Example Applications
- Appendixes
- SDK Reference
-
FAQs
- General FAQs
- Login Issues
- Synchronizing Images
- Pushing an Image
- Pulling an Image
-
Troubleshooting
- Why Does the Login Command Fail to Be Executed?
- Why Does an Image Fail to Be Pushed Through a Container Engine Client?
- Why Does an Image Fail to Be Uploaded Through SWR Console?
- Why Does the docker pull Command Fail to Be Executed?
- What Should I Do If Images Cannot Be Downloaded from Private Networks?
- What Do I Do If an Error Occurs When I Call an API?
-
Other FAQs
- Why Does a CCE Workload Cannot Pull an Image from SWR and a Message "Not Logged In" Is Displayed?
- How Many Tenants Can I Share an SWR Private Image With?
- Why Is an Image Pushed Using a Container Engine Client to SWR Different in Size From One Uploaded Through the SWR Console?
- Can I Pull Images on the SWR Console to a Local PC?
- Videos
- Glossary
-
More Documents
- User Guide
- API Reference
- User Guide (Paris Regions)
- API Reference (Paris Regions)
- User Guide (Kuala Lumpur Region)
- API Reference (Kuala Lumpur Region)
-
User Guide (Ankara Region)
- Service Overview
- Overview
- Permissions Management
- Basics of Docker
-
Image Management
- Pushing an Image Through a Container Engine Client
- Obtaining a Long-Term Valid Docker Login Command
- Obtaining a Long-Term Valid containerd Pull/Push Command
- Uploading an Image Through the SWR Console
- Pulling an Image
- Setting Image Attributes
- Sharing Private Images
- Adding a Trigger
- Adding an Image Retention Policy
- Organization Management
- User Permissions
- FAQs
-
API Reference (Ankara Region)
- Before You Start
- API Overview
- Calling APIs
- API
- Appendixes
- Permissions and Supported Actions
- General Reference
Show all
Copied.
Permissions
If you need to grant your enterprise personnel permission to access your SWR resources, use Identity and Access Management (IAM). IAM provides identity authentication, fine-grained permissions management, and access control. 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, if you want some software developers in your enterprise to be able to use SWR resources but not be able to delete the resources or perform any other high-risk operations, you can create IAM users and grant permission to use SWR resources but not permission to delete them.
If your Huawei Cloud account does not require individual IAM users for permissions management, you can skip this section.
IAM is a free service. You only pay for the resources in your account.
For more information about IAM, see IAM Service Overview.
SWR Permissions
New IAM users do not have any permissions assigned by default. You need to first add them to one or more groups and then 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.
SWR is a project-level service deployed for specific regions. When you set Scope to Region-specific projects and select the specified projects (for example, ap-southeast-1) in the specified regions (for example, CN-Hong Kong), the users only have permissions for SWR resources in the selected projects. When accessing SWR, the users need to switch to the authorized region.
You can grant permissions by using roles and policies.
- Roles: A coarse-grained authorization strategy that defines permissions by job responsibility. Only a limited number of service-level roles are available for authorization. Huawei Cloud services often depend on each other. When you grant permissions using roles, you also need to attach any existing role dependencies. Roles are not ideal for fine-grained authorization and least privilege access.
- Policies: A fine-grained authorization strategy that defines permissions required to perform operations on specific cloud resources under certain conditions. This type of authorization is more flexible and is ideal for least privilege access. For example, you can grant users only permission to manage a certain type of ECSs.
SWR has two editions: Shared and Enterprise.
Table 1 and Table 2 describe all system-defined policies and roles of SWR Shared Edition.
Policy |
Description |
Type |
---|---|---|
SWR FullAccess |
Full permissions for SWR. |
System-defined policy |
SWR OperateAccess |
Operation permissions for SWR. |
System-defined policy |
SWR ReadOnlyAccess |
Read-only permission for SWR. |
System-defined policy |
Role |
Description |
Type |
---|---|---|
SWR Admin |
Administrator permissions for SWR. Users with this role can perform all operations on SWR resources. |
System-defined role |
Tenant Administrator |
Administrator permissions for all services except IAM. Users with this role can perform all operations on SWR resources. |
System-defined role |
ServiceStage Developer |
ServiceStage developer permissions. For example, users with this role can pull images. |
System-defined role |
Table 3 lists the common operations supported by system-defined permissions for SWR.
Operation |
SWR FullAccess |
SWR OperateAccess |
SWR ReadOnlyAccess |
SWR Admin |
Tenant Administrator |
---|---|---|---|---|---|
Uploading/Pushing an Image |
√ |
√ |
x |
√ |
√ |
Downloading/Pulling an Image |
√ |
√ |
√ |
√ |
√ |
Adding a trigger |
√ |
√ |
x |
√ |
√ |
Modifying an image |
√ |
√ |
x |
√ |
√ |
Sharing an image |
√ |
√ |
x |
√ |
√ |
Assigning permissions |
√ |
√ |
x |
√ |
√ |
Deleting an image or a tag |
√ |
√ |
x |
√ |
√ |
Replicating images |
√ |
√ |
x |
√ |
√ |
Creating an organization |
√ |
√ |
x |
√ |
√ |
Deleting an organization |
√ |
√ |
x |
√ |
√ |
You can grant permissions (read, write, and manage permissions), to different users for them to access either a specific image or images in a specific organization.
Feedback
Was this page helpful?
Provide feedbackThank 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