tencent cloud

Virtual Private Cloud

Release Notes and Announcements
Release Notes
Announcements
Tencent Cloud Network Overview
Product Introduction
Overview
Strengths
Use Cases
Concepts
Quota Limit
Service Regions and Service Providers
Purchase Guide
Billing Overview
Payment Overdue
Quick Start
Network Planning
VPC Connections
Building Up an IPv4 VPC
Operation Guide
Network Topology
Network performance dashboard
Virtual Private Cloud (VPC)
Subnets
Route Tables
Elastic IP
HAVIPs
Elastic Network Interface
Bandwidth Package
Network Connection
Security Management
Diagnostic Tools
Alarming and Monitoring
Practical Tutorial
View the Total Bandwidth for Single-Region Traffic-Based Billing
Migrating from the Classic Network to VPC
Best Practices of Security Group Change
Configuring CVM Instance as Public Gateway
Building HA Primary/Secondary Cluster with HAVIP + Keepalived
Hybrid Cloud Primary/Secondary Communication (DC and VPN)
Hybrid Cloud Primary/Secondary Communication (CCN and VPN)
CVM Access to Internet Through EIP
Troubleshooting
VPCs or Subnets Cannot Be Deleted
Network Disconnection After Connecting Two VPCs over CCN
Failed to Ping CVMs in the Same VPC
API Documentation
History
Introduction
API Category
Making API Requests
VPC APIs
Route Table APIs
Elastic Public IP APIs
Elastic IPv6 APIs
Highly Available Virtual IP APIs
ENI APIs
Bandwidth Package APIs
NAT Gateway APIs
Direct Connect Gateway APIs
Cloud Connect Network APIs
Network ACL APIs
Network Parameter Template APIs
Network Detection-Related APIs
Flow Log APIs
Gateway Traffic Monitor APIs
Private Link APIs
Traffic Mirroring APIs
Other APIs
Subnet APIs
VPN Gateway APIs
Security Group APIs
Snapshot Policy APIs
Error Codes
Data Types
FAQs
General
Connection
Security
Contact Us
Glossary

Cloning a Security Group

PDF
포커스 모드
폰트 크기
마지막 업데이트 시간: 2024-10-22 16:10:34

Operation Scenario

You may need to clone a security group in the following scenarios:
You have created a security group named sg-A in region A and want to apply sg-A rules to instances in region B. In this case, you can clone sg-A to region B instead of creating another security group in region B.
Your business needs to execute a new security group rule. In this case, you can clone the original security group for backup.

Notes

By default, only the inbound and outbound rules of a security group are cloned, but not the instances associated with the security group.
Security groups can be cloned between projects or regions.

Steps

1. Log in to Security Group Console, enter the security group management page.
2. On the security group management page, choose Region and locate the row of the security group to be cloned.
3. In the operation column, click More > Clone.
4. In the "Clone Security Group" window that appears, select Target Project and Target Region for the cloning, enter a New Name for the security group, and click OK.

도움말 및 지원

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

피드백