tencent cloud

Tencent Cloud Distributed Cache (Redis OSS-Compatible)

Release Notes and Announcements
Release Notes
Announcements
User Tutorial
Product Introduction
Overview
Product Strengths
Use Cases
Storage Engine
Product Series
Product Versions
Specifications and Performance
Read/Write Separation
Multi-AZ Deployment
Regions and AZs
Terms
Service Regions and Service Providers
Purchase Guide
Billing Overview
Pricing Center
Instance Purchasing
Renewal (Yearly/Monthly Subscription)
Refund (Yearly/Monthly Subscription)
Overdue Payments
Switching from Pay-as-You-Go to Yearly/Monthly Subscription
Getting Started
Quickly Creating an Instance
Connecting to Redis Instance
Operation Guide
Operation Overview
Connecting to a Database Instance
Managing Instances
Upgrade Instance
Management Node (Redis/ValKey Edition)
Multi-AZ Deployment Management
Backup and Restoration
Managing Accounts
Parameter Configuration
Slow Query
Access Management
Network and Security
Monitoring and Alarms
Event Management (Redis/ValKey Edition)
Data Migration
Global Replication for Redis Edition
Database Audit
Performance Optimization
Sentinel Mode
Development Guidelines
Naming Rules
Basic Usage Guidelines
Design Principles of Key and Value
Command Usage Guidelines
Design Principles of Client Programs
Connection Pool Configuration
Command Reference
Command Reference Overview
Redis Edition and Valkey Edition Command Compatibility
Version Command Usage Differences
Differences Between the Proxy Architecture and Direct Connection Mode
More Command Operations (Redis/Valkey Edition)
Memcached Edition Command Compatibility
Practical Tutorial
Building TencentDB for Redis® Client Monitoring Based on Spring Boot
Redis Client Connection Configuration Policy and Practice
Global SCAN Guide for Cluster Architecture
Eliminating Instances Securely
Hot Key and Big Key
AZ Migration Scheme
Troubleshooting
Connection Exception
Exception Analysis and Solution of Redisson Client Timeout Reconnection
Performance Troubleshooting and Fine-Tuning
API Documentation
History
Introduction
API Category
Making API Requests
Instance APIs
Parameter Management APIs
Other APIs
Backup and Restoration APIs
Region APIs
Monitoring and Management APIs
Log APIs
Data Types
Error Codes
FAQs
General
Connection and Login
Purchase
Service Agreement
Service Level Agreement
Terms of Service
Glossary
Contact Us

Overview

PDF
포커스 모드
폰트 크기
마지막 업데이트 시간: 2026-03-17 17:45:59

Issues

If you have multiple users managing different Tencent Cloud services such as CVM, VPC, and TencentDB, and they all share your Tencent Cloud account access key, you may face the following problems:
Your key will be easily compromised because it is shared by several users.
Your users might introduce security risks from misoperations due to the lack of user access control.

Solution

You can avoid the above problems by using sub-accounts to allow different individuals to manage different services. By default, sub-accounts have no access to cloud services or related resources. You need to create policies to grant sub-accounts the required resources or permissions. CAM (Cloud Access Management) supports creating sub-users, user groups, and roles, and allows controlling their access scope through policies. You can configure customized access to Tencent Cloud services for enterprise users based on specific management scenarios.
Note:
The Tencent Cloud root account you initially created has full access to all services and resources under the account. It is recommended to protect the credentials of the root account, use sub-users or roles for daily access, enable multi-factor authentication, and periodically rotate keys.

Getting started

CAM policies must grant permissions for one or more Distributed Cache operations or deny permissions for one or more Distributed Cache operations. They must also specify the resources (which may include all resources or partial resources for certain operations) that can be used for the operations, and may include conditions set for the operations on these resources.
Note:
It is recommended that users use CAM policies to manage Distributed Cache resources and authorize Distributed Cache operations. For existing users with project-based permissions, the experience remains consistent; however, it is not recommended to continue using project-based permissions for resource management and operation authorization.
Distributed Cache currently does not support the configuration of effective conditions.
Related Content
Links
Operation definition in a policy
Resource definition in a policy
Resource-level permissions


도움말 및 지원

문제 해결에 도움이 되었나요?

피드백