Security Group Configuration Examples

Resources on a BMS in a security group need to be copied to a BMS in another security group. The two BMSs are in the same VPC. Then, you can enable internal network communication between the two BMSs and copy resources.

In the same VPC, BMSs associated with the same security group can communicate with one another by default, and no additional configuration is required. However, BMSs in different security groups cannot communicate with each other by default. You must add security group rules to enable the BMSs to communicate with each other through an internal network.

However, BMSs in different security groups cannot communicate with each other by default. You must add security group rules to enable the BMSs to communicate with each other through an internal network.

To prevent BMSs from being attacked, you can change the port number for remote login and configure security group rules that allow only specified IP addresses to remotely access the BMSs.

To allow IP address 192.168.20.2 to remotely access Linux BMSs in a security group over the SSH protocol and port 22, you can configure the following security group rule.

To remotely connect to a Linux BMS through SSH, you need to add a security group rule.

The default security group comes with this rule. If you use the default security group, you do not need to configure the rule again.

To remotely connect to a Windows BMS through RDP, you need to add a security group rule.

The default security group comes with this rule. If you use the default security group, you do not need to configure the rule again.

To ping BMSs from each other to check connectivity, you need to add a security group rule.