Container Registry
Container Registry
Container Registry
Document
Container Registry (CR)
What's new
Overview
Billing
Billing item
Getting started
User guide
User authorization
Authorization management
Robot account management
Instance management
Namespace management
OCI artifact repository management
OCI artifact management
Version management
Tag immutability rule management
Tag retention rules management
Access configuration
Access control
Distribution acceleration
P2P acceleration
Image lazy loading
Registry replication
Audit log management
Alerts and notifications
Best practices
Image push and pull
Image migration and synchronization
DevOps delivery
FAQ
Authorization
VPC
Image push and pull
Limits
Registry replication
P2P acceleration
Access control
API
Calling Method
Instance Management
Namespace Management
OCI Artifact Repository Management
OCI Artifact Version Management
Domain Management
Access Endpoint Management
Temporary Access Key
Robot Account Management
General Data Structure
Artifact repository AR
What's new
Product overview
Getting started
User guide
Instance management
Repository Management
Access control
Permanent access credentials
Temporary access credentials
Maven package management
Generic package management
PyPI package management
NPM package management
Uploading packages
Downloading packages
AI package management
Permission management
API Reference
Repository Management
Package management
Version Management
File Management
Temporary Key Management
General Data Structure
- Documentation
Container RegistryContainer Registry (CR)FAQAuthorizationHow do I fix the "AccessDenied Code:403" error?
Copy page
Download PDFAuthorization
How do I fix the "AccessDenied Code:403" error?
Copy pageDownload PDFHow do I fix the "AccessDenied Code:403" error?
Issue description
When an IAM user first logs in to CR, an insufficient permissions error may appear. Example error message:
- Error code: AccessDenied Code:403 Error messages are similar.
- Error description: User is not authorized to perform: cr:SetUser on resource:trn cn-****:instance/****.
Solution
Before using CR, an IAM user must be granted the required resource management permissions by the root user.
- System policies: These are created by Volcano Engine. You can use them, but you cannot modify them. Volcano Engine maintains policy version updates. For details, see Adding system policies.
- Custom policies: You can create, update, and delete them yourself. You maintain policy version updates. For details, see Adding custom policies.
Last updated: 2026.10.19 15:46:49
All rights reserved © Beijing Volcano Engine Technology Co., Ltd2024
