forked from docs/doc-exports
fanqinying
d2f00b744a
Reviewed-by: Szirovicza Gergő <a94652429@noreply.gitea.eco.tsi-dev.otc-service.com> Reviewed-by: Sarda, Priya <prsarda@noreply.gitea.eco.tsi-dev.otc-service.com> Co-authored-by: fanqinying <fanqinying@huawei.com> Co-committed-by: fanqinying <fanqinying@huawei.com>
14 lines
1.1 KiB
HTML
14 lines
1.1 KiB
HTML
<a name="vpc_Concepts_0004"></a><a name="vpc_Concepts_0004"></a>
|
|
|
|
<h1 class="topictitle1">SNAT</h1>
|
|
<div id="body1488958817764"><p id="vpc_Concepts_0004__p47524794154050">In addition to services provided by the system, some ECSs need to access the Internet to obtain information or download software. You can bind EIPs to virtual network interfaces (ports) of ECSs to enable the ECSs to access the Internet. However, assigning an EIP to each ECS consumes IPv4 addresses, incurs additional costs, and may increase the attack surface for a virtual environment. Therefore, SNAT is introduced to enable multiple ECSs to share one EIP.</p>
|
|
<p id="vpc_Concepts_0004__p2532422815461">On a public cloud, an EIP can be assigned to an ECS that serves as the SNAT router or gateway for other ECSs from the same subnet or VPC.</p>
|
|
<p id="vpc_Concepts_0004__p39449073123229">For details about how to configure SNAT, see <a href="vpc_route_0004.html">Configuring an SNAT Server</a>.</p>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="vpc_Concepts_0001.html">Basic Concepts</a></div>
|
|
</div>
|
|
</div>
|
|
|