- Service Overview
- Getting Started
-
User Guide
- Using IAM to Grant Access to FlexusX
- Purchasing a FlexusX Instance
- Logging In to a FlexusX Instance
- Managing FlexusX Instances
- Managing Images
- Managing EVS Disks
-
VPC Management
- VPC Overview
- Attaching Extension Network Interfaces to a FlexusX Instance
- Detaching Extension Network Interfaces from a FlexusX Instance
- Changing the VPC for a FlexusX Instance
- Changing the Private IP Address of the Primary Network Interface for a FlexusX Instance
- Configuring a Virtual IP Address for a FlexusX Instance
- Managing EIPs
- Managing Server Security
- Managing Backups
- Viewing Monitoring Metrics and Configuring Alarms
- API Reference
-
FAQs
- Product Consulting
- Billing
- OS and Image
- Specification Modification FAQ
-
Performance Mode
- How Do I Know Whether Performance Mode Is Enabled for a FlexusX Instance?
- How Much Can Performance Be Improved If Performance Mode Is Enabled for a Flexus X Instance?
- Do I Need to Stop My FlexusX Instance If I Want to Enable or Disable Performance Mode for It?
- Can I Enable Performance Mode After a FlexusX Instance Is Created?
- Will I Continue to Be Billed If I Disable Performance Mode for My FlexusX Instance?
- Password
- General Reference
Copied.
Overview
Security Group
A security group is a collection of access control rules for cloud resources, such as cloud servers, containers, and databases, that have the same security protection requirements and that are mutually trusted. After a security group is created, you can configure access rules that will apply to all cloud resources added to this security group.
For more information about security groups, see security groups.
A security group works only when the network communication is normal. If two FlexusX instances are in the same security group but in different VPCs, the instances cannot communicate with each other. To enable communications between the two instances, connect the two VPCs first. For details, see Connecting VPCs.
Security Group Rules
After a security group is created, you can add rules to it. A rule applies either to inbound traffic (ingress) or outbound traffic (egress). Any FlexusX instances added to the security group are protected by the rules of that group. For details about more configuration examples, see Security Group Examples.
You can create a custom security group or use the default one provided by the system. The default security group allows all outbound traffic and denies inbound traffic. FlexusX instances in a security group can communicate with each other without adding any rules.
Direction |
Action |
Type |
Protocol & Port |
Source/Destination |
Description |
---|---|---|---|---|---|
Inbound |
Allow |
IPv4 |
All |
Source: default security group (default) |
Allows instances in the security group to communicate with each other over IPv4 protocols. |
Inbound |
Allow |
IPv6 |
All |
Allows instances in the security group to communicate with each other over IPv6 protocols. |
|
Outbound |
Allow |
IPv4 |
All |
Destination: 0.0.0.0/0 |
Allows access from instances in the security group to any IPv4 address over any port. |
Outbound |
Allow |
IPv6 |
All |
Destination: ::/0 |
Allows access from instances in the security group to any IPv6 address over any port. |
Security Group Constraints
- By default, you can create up to 100 security groups in your cloud account.
- By default, you can add up to 50 rules to a security group.
- For better network performance, you are advised to associate no more than five security groups with a FlexusX instance or supplementary network interface.
- You can add up to 20 instances to a security group at a time.
- You can add up to 1,000 instances to a security group.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot