forked from docs/doc-exports
geminidb_umn_20240905
Reviewed-by: Wagner, Fabian <fabian.wagner@t-systems.com> Co-authored-by: Ru, Li Yi <liyiru7@huawei.com> Co-committed-by: Ru, Li Yi <liyiru7@huawei.com>
This commit is contained in:
@ -2,9 +2,9 @@
|
||||
|
||||
<h1 class="topictitle1">Configuring Security Group Rules</h1>
|
||||
<div id="body1568079458237"><div class="section" id="nosql_02_0004__section3152058916230"><h4 class="sectiontitle"><strong id="nosql_02_0004__b16218454114513">Scenarios</strong></h4><p id="nosql_02_0004__p199191161250">The default security group rule allows all outgoing data packets. <span id="nosql_02_0004__text84651218553">ECS</span><span id="nosql_02_0004__text154659184517"></span>s and <span id="nosql_02_0004__text346516182514">GeminiDB</span> instances in the same security group can access each other. After a security group is created, you can create different rules for that security group, which allows you to control access to the <span id="nosql_02_0004__text24651218954">GeminiDB</span> instances that in it.</p>
|
||||
<p id="nosql_02_0004__p43222116204125">The following describes how to set security groups.</p>
|
||||
<p id="nosql_02_0004__p43222116204125">The following describes how to configure security groups.</p>
|
||||
</div>
|
||||
<div class="section" id="nosql_02_0004__section9456131432010"><h4 class="sectiontitle"><strong id="nosql_02_0004__b622952211485">Precautions</strong></h4><ul id="nosql_02_0004__ul10612183218515"><li id="nosql_02_0004__li8531887277">If the ECS and DB instance are in the same security group, they can communicate with each other by default. No security group rule needs to be configured.</li><li id="nosql_02_0004__li06121321516">If the ECS and DB instance are in different security groups, you need to configure security group rules for the ECS and DB instance separately.<ul id="nosql_02_0004__ul13612732951"><li id="nosql_02_0004__li4571145411248">To allow access to the <span id="nosql_02_0004__text20661161562618">GeminiDB Cassandra</span> instance, you need to configure an inbound rule for the security group that the instance nodes belong to.</li><li id="nosql_02_0004__li14612163220515">By default, the security group allows all outbound data packets, so you do not need to configure a security rule for the ECS. If not all access from the ECS is allowed, you need to configure an outbound rule for the ECS.</li></ul>
|
||||
<div class="section" id="nosql_02_0004__section9456131432010"><h4 class="sectiontitle"><strong id="nosql_02_0004__b622952211485">Precautions</strong></h4><ul id="nosql_02_0004__ul10612183218515"><li id="nosql_02_0004__li8531887277">If the ECS and DB instance are in the same security group, they can communicate with each other by default. No security group rule needs to be configured.</li><li id="nosql_02_0004__li06121321516">If the ECS and DB instance are in different security groups, you need to configure security group rules for the ECS and DB instance separately.<ul id="nosql_02_0004__ul13612732951"><li id="nosql_02_0004__li4571145411248">To allow access to a <span id="nosql_02_0004__text20661161562618">GeminiDB Cassandra</span> instance, you need to configure an inbound rule for the security group that the instance nodes belong to.</li><li id="nosql_02_0004__li14612163220515">By default, the security group allows all outbound data packets, so you do not need to configure a security rule for the ECS. If not all access from the ECS is allowed, you need to configure an outbound rule for the ECS.</li></ul>
|
||||
</li></ul>
|
||||
<ul id="nosql_02_0004__ul11655735142317"><li id="nosql_02_0004__li18793238132312">By default, you can create up to 500 security group rules. However, too many rules increase network latency for initial access, so it is recommended that you add no more than 50 rules for each security group.</li></ul>
|
||||
</div>
|
||||
|
||||
Reference in New Issue
Block a user