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

Configuring Security Group

PDF
포커스 모드
폰트 크기
마지막 업데이트 시간: 2026-03-18 09:55:39

Overview

A security group is a stateful virtual firewall capable of filtering. As an important means for network security isolation provided by Tencent Cloud, it can be used to set network access controls for one or more TencentDB instances. Instances with the same network security isolation demands in one region can be put into the same security group, which is a logical group. TencentDB and CVM share the security group list and are matched with each other within the security group based on rules. For specific rules and limitations, see Security Groups Overview. You can bind a security group directly during instance purchase or bind one in the console after instance purchase.
Note:
Tencent Cloud Distributed Cachesecurity groups currently only support network access control for VPCs and public networks but not the classic network.
As Tencent Cloud Distributed Cache doesn't have any active outbound traffic, outbound rules don't apply to it.
Tencent Cloud Distributed Cache security groups support master instances, read-only instances, and disaster recovery instances.
When an instance is purchased, it must be bound to at least one security group. After purchase, you can edit or adjust the bound security groups in the console.

Configuring Security Groups for TencentDB

Step 1. Create a security group

1. Log in to the CVM console.
2. Select Security Group on the left sidebar, select a region above the instance list on the right, and click Create.
3. In the pop-up window, set the following configuration items, confirm that everything is correct, and click OK.
Template: Select a security group template in the drop-down list.
Open all ports: All ports are opened to the public and private networks. This may present security issues. Security group rules are added by default. You can click a security group template below to view its Outbound Rules* and Inbound Rules**.
- Open ports 22, 80, 443, and 3389 and the ICMP protocol: Ports 22, 80, 443, and 3389 and the ICMP protocol are opened to the internet. All ports are opened to the private network. Security group rules are added by default.
Custom: You can create a security group and then add custom rules.
Name: Custom name of the security group.
Project: Select a project for easier management. By default, Default Project is selected.
Notes: A short description of the security group for easier management.
Advanced Configuration: You can add tags for the security group.
4. If you select Custom for Template, click Set Now in the Note window and perform the following steps.

Step 2. Set inbound rules in the security group

Note:
After public network access is enabled, it will be controlled by the security group network access policy. Configure the source information for database access in the security group inbound rules, and open the protocol ports (both private and public network ports must be opened; the default private network port is 6379).
1. On the Inbound Rule tab of the Security Group Rules page, click Add Rules.
2. In the Add Inbound Rules window, set the rules.
Type: Select Custom as the default type.
Source: Set the source for database access, i.e., the inbound source, in the following formats:
Source Format
Format description
CIDR notation
Represented in CIDR notation (IPv4: for example, 203.0.113.0, 203.0.113.0/24, or 0.0.0.0/0, where 0.0.0.0/0 represents all IPv4 addresses. IPv6: for example, FF05::B5, FF05:B5::/60, ::/0, or 0::0/0, where ::/0 or 0::0/0 represents all IPv6 addresses).
Security group ID
Reference a security group ID to match the IP address of the server associated with the security group.
The current security group: Refers to the security group ID associated with the Cloud Virtual Machine.
Other security groups: Refers to another security group ID within the same region and same project.
Note:
Referencing a security group ID is an advanced feature that you can choose to use. The rules of the referenced security group will not be added to the current security group.
When configuring the security group rules, if you enter a security group ID in source/destination, it means that only the private network IP address of the Cloud Virtual Machine instance and Elastic Network Interface bound to this security group ID is used as the source/destination, excluding the public network IP address.
Parameter template
Reference an IP address object or IP address group object in a parameter template.
Parameter template - IP address group
Reference an IP address group object in the parameter template.
Current login IP address
The public IP address currently logged-in to the console.
Protocol Port: Enter the protocol type and port for the client to access Tencent Cloud Distributed Cache. You can view the port information in the Private IPv4 Address in the Network Info section on the Instance Details page. The default port is 6379. If the access protocol is TCP, you can enter TCP:6379.
Policy: Allow or Reject. Allow is selected by default.
Allow: Access requests of this port are allowed.
Reject: Data packets will be discarded without any response.
Notes: A short description of the rule for easier management.
3. Click Complete.

Step 3. Configure the security group for a database instance

Note:
When purchasing an instance, you can directly select the security group to be associated with the instance from the Security Group drop-down list on the purchase page. For more information, see Creating Tencent Cloud Distributed Cache Instance.
After purchase, you can change or add a security group for an instance based on the following steps.
2. Above the Instance List on the right, select the region.
3. In the instance list, find the target instance.
4. Click the instance ID to enter the instance management page.
5. On the Security Group tab, click Configure Security Group.
6. In the Configure Security Group pop-up window, select a created security group. You can filter security group by project name.

7. Click OK.
In the Associated Security Group section, you can view the list of security groups associated with the database instance.
You can click a security group ID to enter the Security Group Rules page and edit the rules as instructed in Modifying a Security Group Rule. For more operations, see Viewing a Security Group Rule.
In the Priority column, you can view the priorities of security groups. When two or more security groups are selected, click Edit above the security group list, click
img

or
img

to adjust the priorities of security groups.
Configure two or more security groups and click

to delete the bound security groups.

On the Preview Rules page, you can view the inbound source information of the security group on the Inbound Rules tab.



More operations

For more security group operations, see Viewing a Security Group.
For more security group rule operations, see Viewing a Security Group Rule.
For security group APIs, see DeleteSecurityGroup.

Related APIs

API Name
Description
Queries the security group information of a project
Queries the security group information of an instance
Modifies the security groups bound to an instance
Binds a security group
Unbinds a security group from instances in batches

도움말 및 지원

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

피드백