tencent cloud

Tencent Kubernetes Engine

Release Notes and Announcements
Release Notes
Announcements
Release Notes
Product Introduction
Overview
Strengths
Architecture
Scenarios
Features
Concepts
Native Kubernetes Terms
Common High-Risk Operations
Regions and Availability Zones
Service Regions and Service Providers
Open Source Components
Purchase Guide
Purchase Instructions
Purchase a TKE General Cluster
Purchasing Native Nodes
Purchasing a Super Node
Getting Started
Beginner’s Guide
Quickly Creating a Standard Cluster
Examples
Container Application Deployment Check List
Cluster Configuration
General Cluster Overview
Cluster Management
Network Management
Storage Management
Node Management
GPU Resource Management
Remote Terminals
Application Configuration
Workload Management
Service and Configuration Management
Component and Application Management
Auto Scaling
Container Login Methods
Observability Configuration
Ops Observability
Cost Insights and Optimization
Scheduler Configuration
Scheduling Component Overview
Resource Utilization Optimization Scheduling
Business Priority Assurance Scheduling
QoS Awareness Scheduling
Security and Stability
TKE Security Group Settings
Identity Authentication and Authorization
Application Security
Multi-cluster Management
Planned Upgrade
Backup Center
Cloud Native Service Guide
Cloud Service for etcd
TMP
TKE Serverless Cluster Guide
TKE Registered Cluster Guide
Use Cases
Cluster
Serverless Cluster
Scheduling
Security
Service Deployment
Network
Release
Logs
Monitoring
OPS
Terraform
DevOps
Auto Scaling
Containerization
Microservice
Cost Management
Hybrid Cloud
AI
Troubleshooting
Disk Full
High Workload
Memory Fragmentation
Cluster DNS Troubleshooting
Cluster kube-proxy Troubleshooting
Cluster API Server Inaccessibility Troubleshooting
Service and Ingress Inaccessibility Troubleshooting
Common Service & Ingress Errors and Solutions
Engel Ingres appears in Connechtin Reverside
CLB Ingress Creation Error
Troubleshooting for Pod Network Inaccessibility
Pod Status Exception and Handling
Authorizing Tencent Cloud OPS Team for Troubleshooting
CLB Loopback
API Documentation
History
Introduction
API Category
Making API Requests
Elastic Cluster APIs
Resource Reserved Coupon APIs
Cluster APIs
Third-party Node APIs
Relevant APIs for Addon
Network APIs
Node APIs
Node Pool APIs
TKE Edge Cluster APIs
Cloud Native Monitoring APIs
Scaling group APIs
Super Node APIs
Other APIs
Data Types
Error Codes
TKE API 2022-05-01
FAQs
TKE General Cluster
TKE Serverless Cluster
About OPS
Hidden Danger Handling
About Services
Image Repositories
About Remote Terminals
Event FAQs
Resource Management
Service Agreement
TKE Service Level Agreement
TKE Serverless Service Level Agreement
Contact Us
Glossary

Account Authorization

PDF
Focus Mode
Font Size
Last updated: 2025-03-19 18:30:11

Authorizing Accounts

To perform more granular permission control for businesses, Cloud Service for etcd was integrated with Cloud Access Management (CAM) on May 5, 2022. After the integration, both users and backend services need to be authorized to access the console and call APIs. You can follow the steps below to authorize sub-users and the service to operate other cloud resources.

Directions

Authorizing Sub-users

Cloud Service for etcd has predefined the QcloudCEtcdFullAccess and QcloudCEtcdReadOnlyAccess policies on CAM for full access and read-only access scenarios respectively. If a sub-user needs to access the etcd console and call APIs, use an account with administrator permissions to authorize the sub-user, so that the sub-user can use the etcd service. The steps are as follows:
1. Log in to the CAM console and choose Users > User List from the left sidebar.
2. Click Authorize on the right of a sub-account's username in the user list.
3. Select the following policies in the Associate Policy pop-up window:
QcloudCEtcdFullAccess
QcloudCEtcdReadOnlyaccess

4. Click OK. After the authorization is completed, the sub-account can access the etcd service normally. The administrator can create custom policies to set more specific permissions for users.

Authorizing the Service

Service authorization refers to granting permissions for the current service to operate other cloud resources. For example, when a user creates an etcd cluster, Cloud Service for etcd should have the corresponding operation permissions if the user chooses to create TMP resources and tags. In this case, the administrator needs to authorize Cloud Service for etcd.
1. Log in to the console of Cloud Service for etcd. The Service Authorization window will pop up if no authorization is performed previously, as shown in the figure below:

2. Click Grant and complete authentication for authorization.

Help and Support

Was this page helpful?

Help us improve! Rate your documentation experience in 5 mins.

Feedback