forked from docs/doc-exports
ELB_UMN_20240412
Reviewed-by: Hajba, László Antal <laszlo-antal.hajba@t-systems.com> Co-authored-by: zhoumeng <zhoumeng35@huawei.com> Co-committed-by: zhoumeng <zhoumeng35@huawei.com>
This commit is contained in:
parent
3de6842994
commit
d7316db527
File diff suppressed because it is too large
Load Diff
File diff suppressed because it is too large
Load Diff
52
docs/elb/umn/elb_03_0003.html
Normal file
52
docs/elb/umn/elb_03_0003.html
Normal file
@ -0,0 +1,52 @@
|
|||||||
|
<a name="elb_03_0003"></a><a name="elb_03_0003"></a>
|
||||||
|
|
||||||
|
<h1 class="topictitle1">Access Control</h1>
|
||||||
|
<div id="body1516617042123"><p id="elb_03_0003__p7557113410409">Access control allows you to add a whitelist or blacklist to specify IP addresses that are allowed or denied to access a listener. A whitelist allows specified IP addresses to access the listener, while a blacklist denies access from specified IP addresses.</p>
|
||||||
|
<div class="notice" id="elb_03_0003__note1210711144917"><span class="noticetitle"><img src="public_sys-resources/notice_3.0-en-us.png"> </span><div class="noticebody"><ul id="elb_03_0003__ul1810181134920"><li id="elb_03_0003__li61091194912">Adding the whitelist or blacklist may cause risks. Once a whitelist is added, only IP addresses in the whitelist can access the listener. After a blacklist is added, IP addresses in the blacklist cannot access the listener.</li><li id="elb_03_0003__li19106112498">Whitelists and blacklists do not conflict with inbound security group rules. Whitelists define the IP addresses that are allowed to access the listeners, while blacklists specify IP addresses that are denied to access the listeners. Inbound security group rules control access to backend servers by specifying the protocol, ports, and IP addresses.</li><li id="elb_03_0003__li106833558262">Access control does not restrict the <strong id="elb_03_0003__b1635114715319">ping</strong> command. You can still ping backend servers from the restricted IP addresses.<ul id="elb_03_0003__ul1389724410417"><li id="elb_03_0003__li233113436413">To ping the IP address of a shared load balancer, you need to add a listener and associate a backend server to it.</li><li id="elb_03_0003__li12843165869">To ping the IP address of a dedicated load balancer, you only need to add a listener to it.</li></ul>
|
||||||
|
</li><li id="elb_03_0003__li142973122273">Access control policies only take effect for new connections, but not for connections that have been established. If a whitelist is configured for a listener but IP addresses that are not in the whitelist can access the backend server associated with the listener, one possible reason is that a persistent connection is established between the client and the backend server. To deny IP addresses that are not in the whitelist from accessing the listener, the persistent connection between the client and the backend server needs to be disconnected.</li></ul>
|
||||||
|
</div></div>
|
||||||
|
<div class="section" id="elb_03_0003__section109371640175915"><a name="elb_03_0003__section109371640175915"></a><a name="section109371640175915"></a><h4 class="sectiontitle">Configuring Access Control</h4><ol id="elb_03_0003__ol1693724011599"><li id="elb_03_0003__li132711514413">Log in to the management console.</li><li id="elb_03_0003__li11327121564118">In the upper left corner of the page, click <span><img id="elb_03_0003__image15299767936918" src="en-us_image_0000001747739624.png"></span> and select the desired region and project.</li><li id="elb_03_0003__li17301740102218">Click <span><img id="elb_03_0003__image128541183675133" src="en-us_image_0000001794660485.png"></span> in the upper left corner to display <strong id="elb_03_0003__b11199472675133">Service List</strong> and choose <strong id="elb_03_0003__b103720198075133">Network</strong> > <strong id="elb_03_0003__b191380200375133">Elastic Load Balancing</strong>.</li></ol><ol start="4" id="elb_03_0003__ol7937240175912"><li id="elb_03_0003__li12937184095920">Locate the load balancer and click its name.</li><li id="elb_03_0003__li732042314481">You can configure access control for a listener in either of the following ways:<ul id="elb_03_0003__ul4729655597"><li id="elb_03_0003__li167299519597">On the <strong id="elb_03_0003__b22791632141612">Listeners</strong> page, locate the listener and click <strong id="elb_03_0003__b3734144441618">Configure</strong> in the <strong id="elb_03_0003__b524420484163">Access Control</strong> column.</li><li id="elb_03_0003__li355119112116">Click the name of the listener. On the <strong id="elb_03_0003__b41081446102011">Basic Information</strong> page, click <strong id="elb_03_0003__b1761820585206">Configure</strong> on the right of <strong id="elb_03_0003__b61414522120">Access Control</strong>.</li></ul>
|
||||||
|
</li><li id="elb_03_0003__li09947412311">In the displayed <strong id="elb_03_0003__b107874916410">Configure Access Control</strong> dialog box, configure parameters as shown in <a href="#elb_03_0003__table159371240125911">Table 1</a>.
|
||||||
|
<div class="tablenoborder"><a name="elb_03_0003__table159371240125911"></a><a name="table159371240125911"></a><table cellpadding="4" cellspacing="0" summary="" id="elb_03_0003__table159371240125911" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Parameter description</caption><thead align="left"><tr id="elb_03_0003__row20937194017599"><th align="left" class="cellrowborder" valign="top" width="33.33333333333333%" id="mcps1.3.3.3.3.3.2.4.1.1"><p id="elb_03_0003__p159371240155912"><strong id="elb_03_0003__b842352706114331">Parameter</strong></p>
|
||||||
|
</th>
|
||||||
|
<th align="left" class="cellrowborder" valign="top" width="33.33333333333333%" id="mcps1.3.3.3.3.3.2.4.1.2"><p id="elb_03_0003__p179371740105912"><strong id="elb_03_0003__b8423527061772">Description</strong></p>
|
||||||
|
</th>
|
||||||
|
<th align="left" class="cellrowborder" valign="top" width="33.33333333333333%" id="mcps1.3.3.3.3.3.2.4.1.3"><p id="elb_03_0003__p10937104025916"><strong id="elb_03_0003__b842352706194150">Example Value</strong></p>
|
||||||
|
</th>
|
||||||
|
</tr>
|
||||||
|
</thead>
|
||||||
|
<tbody><tr id="elb_03_0003__row17641244188"><td class="cellrowborder" valign="top" width="33.33333333333333%" headers="mcps1.3.3.3.3.3.2.4.1.1 "><p id="elb_03_0003__p1764152416188">Access Control</p>
|
||||||
|
</td>
|
||||||
|
<td class="cellrowborder" valign="top" width="33.33333333333333%" headers="mcps1.3.3.3.3.3.2.4.1.2 "><p id="elb_03_0003__p571112817239">Specifies how access to the listener is controlled. Three options are available:</p>
|
||||||
|
<ul id="elb_03_0003__ul13289134512316"><li id="elb_03_0003__li14611327183216"><strong id="elb_03_0003__b7186124335410">All IP addresses</strong>: All IP addresses can access the listener.</li><li id="elb_03_0003__li19289114517237"><strong id="elb_03_0003__b9916158135417">Whitelist</strong>: Only IP addresses in the IP address group can access the listener.</li><li id="elb_03_0003__li14191417243"><strong id="elb_03_0003__b10609970555">Blacklist</strong>: IP addresses in the IP address group are not allowed to access the listener.</li></ul>
|
||||||
|
</td>
|
||||||
|
<td class="cellrowborder" valign="top" width="33.33333333333333%" headers="mcps1.3.3.3.3.3.2.4.1.3 "><p id="elb_03_0003__p1476532421817">Blacklist</p>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
<tr id="elb_03_0003__row484412181181"><td class="cellrowborder" valign="top" width="33.33333333333333%" headers="mcps1.3.3.3.3.3.2.4.1.1 "><p id="elb_03_0003__p168451218151813">IP Address Group</p>
|
||||||
|
</td>
|
||||||
|
<td class="cellrowborder" valign="top" width="33.33333333333333%" headers="mcps1.3.3.3.3.3.2.4.1.2 "><p id="elb_03_0003__p1484541812184">Specifies the IP address group associated with a whitelist or blacklist. If there is no IP address group, create one first. For more information, see <a href="elb_ug_ip_0000.html#elb_ug_ip_0000__section1143912015382">IP Address Group Overview</a>.</p>
|
||||||
|
</td>
|
||||||
|
<td class="cellrowborder" valign="top" width="33.33333333333333%" headers="mcps1.3.3.3.3.3.2.4.1.3 "><p id="elb_03_0003__p11574181042917">ipGroup-b2</p>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
<tr id="elb_03_0003__row1993734018590"><td class="cellrowborder" valign="top" width="33.33333333333333%" headers="mcps1.3.3.3.3.3.2.4.1.1 "><p id="elb_03_0003__p793754019597">Access Control</p>
|
||||||
|
</td>
|
||||||
|
<td class="cellrowborder" valign="top" width="33.33333333333333%" headers="mcps1.3.3.3.3.3.2.4.1.2 "><p id="elb_03_0003__p967517492305">If you have set <strong id="elb_03_0003__b81010361142">Access Control</strong> to <strong id="elb_03_0003__b13111436347">Whitelist</strong> or <strong id="elb_03_0003__b1511143615419">Blacklist</strong>, you can enable or disable access control.</p>
|
||||||
|
<ul id="elb_03_0003__ul18937740125914"><li id="elb_03_0003__li0776145410312">Only after you enable access control, the whitelist or blacklist takes effect.</li><li id="elb_03_0003__li171440105326">If you disable access control, the whitelist or blacklist does not take effect.</li></ul>
|
||||||
|
</td>
|
||||||
|
<td class="cellrowborder" valign="top" width="33.33333333333333%" headers="mcps1.3.3.3.3.3.2.4.1.3 "><p id="elb_03_0003__p8938040105917">N/A</p>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
</tbody>
|
||||||
|
</table>
|
||||||
|
</div>
|
||||||
|
</li><li id="elb_03_0003__li1193811400599">Click <strong id="elb_03_0003__b842352706102911">OK</strong>.</li></ol>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
<div>
|
||||||
|
<div class="familylinks">
|
||||||
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="elb_ug_fw_0000.html">Access Control</a></div>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
|
@ -1,11 +1,11 @@
|
|||||||
<a name="elb_faq_0040"></a><a name="elb_faq_0040"></a>
|
<a name="elb_faq_0040"></a><a name="elb_faq_0040"></a>
|
||||||
|
|
||||||
<h1 class="topictitle1">How Can I Check the Network Configuration of a Backend Server?</h1>
|
<h1 class="topictitle1">How Can I Check the Network Configuration of a Backend Server?</h1>
|
||||||
<div id="body8662426"><ol id="elb_faq_0040__en-us_topic_0100578555_ol51835414175346"><li id="elb_faq_0040__en-us_topic_0100578555_li26028006175346">Check whether the security group of the server is correctly configured.<ol type="a" id="elb_faq_0040__en-us_topic_0100578555_ol15120255104222"><li id="elb_faq_0040__en-us_topic_0100578555_li8965360104233">On the server details page, view the security group.</li><li id="elb_faq_0040__li1256125092715">Check whether the security group rules allow access from the corresponding IP address range.<ul id="elb_faq_0040__ul18999115652214"><li id="elb_faq_0040__li2330162013231">Dedicated load balancers: Check whether the security group of the backend server has inbound rules to allow traffic from the VPC where the load balancer works. If traffic is not allowed, add an inbound rule to allow traffic from the VPC to the backend server.</li><li id="elb_faq_0040__li613813371268"><span id="elb_faq_0040__ph988272093916">Shared</span> load balancers: Check whether the security group of the backend server has inbound rules to allow traffic from the 100.125.0.0/16. If traffic is not allowed, add an inbound rule to allow traffic from 100.125.0.0/16<span id="elb_faq_0040__ph1944315364202"></span> to the backend server.</li></ul>
|
<div id="body8662426"><ol id="elb_faq_0040__en-us_topic_0100578555_ol51835414175346"><li id="elb_faq_0040__en-us_topic_0100578555_li26028006175346">Check whether the security group of the server is correctly configured.<ol type="a" id="elb_faq_0040__en-us_topic_0100578555_ol15120255104222"><li id="elb_faq_0040__en-us_topic_0100578555_li8965360104233">On the server details page, view the security group.</li><li id="elb_faq_0040__li1256125092715">Check whether the security group rules allow access from the corresponding IP address range.<ul id="elb_faq_0040__ul18999115652214"><li id="elb_faq_0040__li2330162013231">Dedicated load balancers: Check whether the security group of the backend server has inbound rules to allow traffic from the VPC where the load balancer works. If traffic is not allowed, add an inbound rule to allow traffic from the VPC to the backend server.</li><li id="elb_faq_0040__li613813371268"><span id="elb_faq_0040__ph192714001583048">Shared</span> load balancers: Check whether the security group containing the backend server has inbound rules to allow traffic from 100.125.0.0/16. If traffic is not allowed, add an inbound rule to allow traffic from 100.125.0.0/16 to the backend server.</li></ul>
|
||||||
<div class="caution" id="elb_faq_0040__note5214162212421"><span class="cautiontitle"><img src="public_sys-resources/caution_3.0-en-us.png"> </span><div class="cautionbody"><ul id="elb_faq_0040__ul6236111617482"><li id="elb_faq_0040__li9236141624819"><span id="elb_faq_0040__ph14393155975612">Shared</span> load balancers: If <strong id="elb_faq_0040__b9395195955618">Transfer Client IP Address</strong> is enabled for a TCP or UDP listener, there is no need to configure security group rules and <span id="elb_faq_0040__ph240305918568">Firewall</span> rules to allow traffic from 100.125.0.0/16, 100.126.0.0/16, and client IP addresses to backend servers.</li><li id="elb_faq_0040__li523691644811"><span id="elb_faq_0040__ph16422295714">Dedicated load balancers</span>: If <strong id="elb_faq_0040__b56447217577">IP as a Backend</strong> is not enabled for a load balancer that has a TCP or UDP listener, there is no need to configure security group rules and <span id="elb_faq_0040__ph176531526578">Firewall</span> rules to allow traffic from the backend subnet where the load balancer is deployed to the backend servers.</li></ul>
|
<div class="caution" id="elb_faq_0040__note5214162212421"><span class="cautiontitle"><img src="public_sys-resources/caution_3.0-en-us.png"> </span><div class="cautionbody"><ul id="elb_faq_0040__ul6236111617482"><li id="elb_faq_0040__li9236141624819"><span id="elb_faq_0040__ph76583894882354">Shared</span> load balancers: If <strong id="elb_faq_0040__b187079305082354">Transfer Client IP Address</strong> is enabled for a TCP or UDP listener, there is no need to configure security group rules and <span id="elb_faq_0040__ph182186090482354">Firewall</span> rules to allow traffic from 100.125.0.0/16 and client IP addresses to backend servers.</li><li id="elb_faq_0040__li523691644811"><span id="elb_faq_0040__ph56225189182355">Dedicated load balancers</span>: If <strong id="elb_faq_0040__b141641617482355">IP as a Backend</strong> is not enabled for a load balancer that has a TCP or UDP listener, there is no need to configure security group rules and <span id="elb_faq_0040__ph186383193682355">Firewall</span> rules to allow traffic from the backend subnet where the load balancer is deployed to the backend servers.</li></ul>
|
||||||
</div></div>
|
</div></div>
|
||||||
</li></ol>
|
</li></ol>
|
||||||
</li><li id="elb_faq_0040__en-us_topic_0100578555_li2154564893111">Ensure that the firewalls of the subnet where the server resides does not intercept the traffic.<p id="elb_faq_0040__en-us_topic_0100578555_p2017488793128"><a name="elb_faq_0040__en-us_topic_0100578555_li2154564893111"></a><a name="en-us_topic_0100578555_li2154564893111"></a>In the navigation pane of the VPC console, choose <strong id="elb_faq_0040__b855515395272">Access Control</strong> > <strong id="elb_faq_0040__b116901318153311">Firewalls</strong> and check whether the subnet allows traffic.</p>
|
</li><li id="elb_faq_0040__en-us_topic_0100578555_li2154564893111">Ensure that the firewalls of the subnet where the server resides does not intercept the traffic.<p id="elb_faq_0040__en-us_topic_0100578555_p2017488793128"><a name="elb_faq_0040__en-us_topic_0100578555_li2154564893111"></a><a name="en-us_topic_0100578555_li2154564893111"></a>In the navigation pane of the VPC console, choose <strong id="elb_faq_0040__b2666192744111">Access Control</strong> > <strong id="elb_faq_0040__b0667227124111">Firewalls</strong> and check whether the subnet allows traffic.</p>
|
||||||
</li></ol>
|
</li></ol>
|
||||||
</div>
|
</div>
|
||||||
<div>
|
<div>
|
||||||
|
@ -1,8 +1,8 @@
|
|||||||
<a name="elb_faq_0070"></a><a name="elb_faq_0070"></a>
|
<a name="elb_faq_0070"></a><a name="elb_faq_0070"></a>
|
||||||
|
|
||||||
<h1 class="topictitle1">What Do I Do If a Lot of Access Logs Are Generated During Health Checks?</h1>
|
<h1 class="topictitle1">What Do I Do If a Lot of Access Logs Are Generated During Health Checks?</h1>
|
||||||
<div id="body1568692772111"><ol id="elb_faq_0070__ol1537211945718"><li id="elb_faq_0070__li23801840131712">You can increase the health check interval by referring to <a href="en-us_topic_0162227063.html">Configuring a Health Check</a>.<p id="elb_faq_0070__p18514741479">Risk: After the health check interval is prolonged, the time for the load balancer to detect unhealthy servers will increase.</p>
|
<div id="body1568692772111"><ol id="elb_faq_0070__ol1537211945718"><li id="elb_faq_0070__li23801840131712">You can increase the health check interval by referring to <a href="en-us_topic_0000001747380572.html">Modifying Health Check Settings</a>.<p id="elb_faq_0070__p18514741479">Risk: After the health check interval is prolonged, the time for the load balancer to detect unhealthy servers will increase.</p>
|
||||||
</li><li id="elb_faq_0070__li452381210242">You can disable the health check by referring to <a href="elb_ug_hc_0003.html">Disabling a Health Check</a>.<p id="elb_faq_0070__p14371654152413">Risk: After health checks are disabled, the load balancer will not check the backend servers. If a backend server becomes faulty, the load balancer will still route requests to this server.</p>
|
</li><li id="elb_faq_0070__li452381210242">You can disable the health check by referring to <a href="en-us_topic_0000001747380572.html">Modifying Health Check Settings</a>.<p id="elb_faq_0070__p14371654152413">Risk: After health checks are disabled, the load balancer will not check the backend servers. If a backend server becomes faulty, the load balancer will still route requests to this server.</p>
|
||||||
</li></ol>
|
</li></ol>
|
||||||
</div>
|
</div>
|
||||||
<div>
|
<div>
|
||||||
|
@ -1,7 +1,7 @@
|
|||||||
<a name="elb_faq_0074"></a><a name="elb_faq_0074"></a>
|
<a name="elb_faq_0074"></a><a name="elb_faq_0074"></a>
|
||||||
|
|
||||||
<h1 class="topictitle1">Can ELB Route Traffic Across Regions?</h1>
|
<h1 class="topictitle1">Can ELB Route Traffic Across Regions?</h1>
|
||||||
<div id="body1568692772111"><ul id="elb_faq_0074__ul122945544419"><li id="elb_faq_0074__li7475741155511">No. <span id="elb_faq_0074__ph14189143975516">Shared</span> load balancers cannot distribute traffic across regions.</li><li id="elb_faq_0074__li131216557333">No, but dedicated load balancers can distribute traffic across VPCs. For details about how to add backend servers in a different VPC or an on-premises data center, see <a href="elb_ug_hd_0005.html">Configuring Hybrid Load Balancing</a>.</li></ul>
|
<div id="body1568692772111"><ul id="elb_faq_0074__ul122945544419"><li id="elb_faq_0074__li7475741155511"><span id="elb_faq_0074__ph34814412554">Shared</span> load balancers cannot route requests to backend servers across regions.</li><li id="elb_faq_0074__li131216557333">Dedicated load balancers can distribute traffic across VPCs. For details, see <a href="elb_ug_hd3_0004_01.html">Overview</a>.</li></ul>
|
||||||
</div>
|
</div>
|
||||||
<div>
|
<div>
|
||||||
<div class="familylinks">
|
<div class="familylinks">
|
||||||
|
@ -4,7 +4,7 @@
|
|||||||
<div id="body1437669816817"><p id="elb_faq_0090__p126130261229">When you use ELB to route requests to backend servers, IP addresses of the clients will be translated by the ELB. This FAQ guides you to obtain the IP addresses of the clients.</p>
|
<div id="body1437669816817"><p id="elb_faq_0090__p126130261229">When you use ELB to route requests to backend servers, IP addresses of the clients will be translated by the ELB. This FAQ guides you to obtain the IP addresses of the clients.</p>
|
||||||
<ul id="elb_faq_0090__ul083915176263"><li id="elb_faq_0090__li10839121712614">Load balancing at Layer 7 (HTTP or HTTPS listeners): Configure the application server and obtain the IP address of a client from the HTTP header.<p id="elb_faq_0090__p67604963112"><a name="elb_faq_0090__li10839121712614"></a><a name="li10839121712614"></a>For details, see <a href="#elb_faq_0090__section12598161410315">Layer 7 Load Balancing</a>.</p>
|
<ul id="elb_faq_0090__ul083915176263"><li id="elb_faq_0090__li10839121712614">Load balancing at Layer 7 (HTTP or HTTPS listeners): Configure the application server and obtain the IP address of a client from the HTTP header.<p id="elb_faq_0090__p67604963112"><a name="elb_faq_0090__li10839121712614"></a><a name="li10839121712614"></a>For details, see <a href="#elb_faq_0090__section12598161410315">Layer 7 Load Balancing</a>.</p>
|
||||||
</li><li id="elb_faq_0090__li82841612175818">For load balancing at Layer 4 (TCP/UDP), you can enable <strong id="elb_faq_0090__b3216413303">Transfer Client IP Address</strong> to obtain the source IP address.</li></ul>
|
</li><li id="elb_faq_0090__li82841612175818">For load balancing at Layer 4 (TCP/UDP), you can enable <strong id="elb_faq_0090__b3216413303">Transfer Client IP Address</strong> to obtain the source IP address.</li></ul>
|
||||||
<div class="section" id="elb_faq_0090__section13394124610518"><h4 class="sectiontitle">Constraints and Limitations</h4><ul id="elb_faq_0090__ul104521513161519"><li id="elb_faq_0090__li13452113161512">If Network Address Translation (NAT) is used, you cannot obtain the IP addresses of the clients.</li><li id="elb_faq_0090__li9274171501517">If the client is a container, you can obtain only the IP address of the node where the container is located, but cannot obtain the IP address of the container.</li><li id="elb_faq_0090__li9335359112219">If <strong id="elb_faq_0090__b352118212323">Transfer Client IP Address</strong> is enabled for TCP or UDP listeners, a cloud server cannot be used as a backend server and a client at the same time. </li><li id="elb_faq_0090__li983412419371">By default, the <strong id="elb_faq_0090__b149753488323">Transfer Client IP Address</strong> function is enabled for TCP and UDP listeners of dedicated load balancers and cannot be disabled.</li></ul>
|
<div class="section" id="elb_faq_0090__section13394124610518"><h4 class="sectiontitle">Constraints and Limitations</h4><ul id="elb_faq_0090__ul104521513161519"><li id="elb_faq_0090__li13452113161512">If Network Address Translation (NAT) is used, you cannot obtain the IP addresses of the clients.</li><li id="elb_faq_0090__li9274171501517">If the client is a container, you can obtain only the IP address of the node where the container is located, but cannot obtain the IP address of the container.</li><li id="elb_faq_0090__li9335359112219">If <strong id="elb_faq_0090__b1277716497232">Transfer Client IP Address</strong> is enabled for TCP or UDP listeners, a cloud server cannot be used as a backend server and a client at the same time. </li><li id="elb_faq_0090__li983412419371">By default, the <strong id="elb_faq_0090__b149753488323">Transfer Client IP Address</strong> function is enabled for TCP and UDP listeners of dedicated load balancers and cannot be disabled.</li></ul>
|
||||||
</div>
|
</div>
|
||||||
<div class="section" id="elb_faq_0090__section12598161410315"><a name="elb_faq_0090__section12598161410315"></a><a name="section12598161410315"></a><h4 class="sectiontitle">Layer 7 Load Balancing</h4><p id="elb_faq_0090__p1023417204310">Configure the application server and obtain the IP address of a client from the HTTP header.</p>
|
<div class="section" id="elb_faq_0090__section12598161410315"><a name="elb_faq_0090__section12598161410315"></a><a name="section12598161410315"></a><h4 class="sectiontitle">Layer 7 Load Balancing</h4><p id="elb_faq_0090__p1023417204310">Configure the application server and obtain the IP address of a client from the HTTP header.</p>
|
||||||
</div>
|
</div>
|
||||||
@ -19,7 +19,7 @@ RemoteIPHeader X-Forwarded-For
|
|||||||
RemoteIPInternalProxy <strong id="elb_faq_0090__b1977615149432"><em id="elb_faq_0090__i1777601412436">100.125.0.0/16</em></strong></pre>
|
RemoteIPInternalProxy <strong id="elb_faq_0090__b1977615149432"><em id="elb_faq_0090__i1777601412436">100.125.0.0/16</em></strong></pre>
|
||||||
<div class="fignone" id="elb_faq_0090__fig1553761545210"><span class="figcap"><b>Figure 1 </b>Content to be added</span><br><span><img id="elb_faq_0090__image1368125117439" src="en-us_image_0000001794660973.jpg"></span></div>
|
<div class="fignone" id="elb_faq_0090__fig1553761545210"><span class="figcap"><b>Figure 1 </b>Content to be added</span><br><span><img id="elb_faq_0090__image1368125117439" src="en-us_image_0000001794660973.jpg"></span></div>
|
||||||
<div class="note" id="elb_faq_0090__note135510197505"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="elb_faq_0090__p11969135614319">Add the IP address range of the proxy server after <strong id="elb_faq_0090__b110010178155">RemoteIPInternalProxy</strong>.</p>
|
<div class="note" id="elb_faq_0090__note135510197505"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="elb_faq_0090__p11969135614319">Add the IP address range of the proxy server after <strong id="elb_faq_0090__b110010178155">RemoteIPInternalProxy</strong>.</p>
|
||||||
<ul id="elb_faq_0090__ul5985165818319"><li id="elb_faq_0090__li49865581436"><span id="elb_faq_0090__ph1441134105011">Shared</span> load balancers: 100.125.0.0/16<span id="elb_faq_0090__ph126143415508"></span> and the IP address range used by the AAD service. Load balancers use IP addresses in 100.125.0.0/16 to communicate with backend servers, and there are no security risks. Use commas (,) to separate multiple entries.</li><li id="elb_faq_0090__li6194337848">Dedicated load balancers: CIDR block of the subnet where the load balancer resides</li></ul>
|
<ul id="elb_faq_0090__ul5985165818319"><li id="elb_faq_0090__li49865581436"><span id="elb_faq_0090__ph1911810238">Shared</span> load balancers: 100.125.0.0/16 and the IP address range used by the AAD service. Load balancers use IP addresses in 100.125.0.0/16 to communicate with backend servers, and there are no security risks. Use commas (,) to separate multiple entries.</li><li id="elb_faq_0090__li6194337848">Dedicated load balancers: CIDR block of the subnet where the load balancer resides</li></ul>
|
||||||
</div></div>
|
</div></div>
|
||||||
</li><li id="elb_faq_0090__li10895421174213">Change the log output format in the Apache configuration file to the following (<strong id="elb_faq_0090__b1311681216319">%a</strong> indicates the source IP address):<pre class="screen" id="elb_faq_0090__screen13565739124411">LogFormat "<em id="elb_faq_0090__i18199122934118"><strong id="elb_faq_0090__b5762132774111">%</strong><strong id="elb_faq_0090__b194131533162710">a</strong></em> %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\"" combined</pre>
|
</li><li id="elb_faq_0090__li10895421174213">Change the log output format in the Apache configuration file to the following (<strong id="elb_faq_0090__b1311681216319">%a</strong> indicates the source IP address):<pre class="screen" id="elb_faq_0090__screen13565739124411">LogFormat "<em id="elb_faq_0090__i18199122934118"><strong id="elb_faq_0090__b5762132774111">%</strong><strong id="elb_faq_0090__b194131533162710">a</strong></em> %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\"" combined</pre>
|
||||||
</li><li id="elb_faq_0090__li1851619394515">Restart Apache.<pre class="screen" id="elb_faq_0090__screen108061723195117">systemctl restart httpd</pre>
|
</li><li id="elb_faq_0090__li1851619394515">Restart Apache.<pre class="screen" id="elb_faq_0090__screen108061723195117">systemctl restart httpd</pre>
|
||||||
@ -39,7 +39,7 @@ make install</pre>
|
|||||||
real_ip_header X-Forwarded-For;</pre>
|
real_ip_header X-Forwarded-For;</pre>
|
||||||
<div class="fignone" id="elb_faq_0090__fig5645153575820"><span class="figcap"><b>Figure 2 </b>Adding information</span><br><span><img id="elb_faq_0090__image117512241589" src="en-us_image_0000001794820077.jpg"></span></div>
|
<div class="fignone" id="elb_faq_0090__fig5645153575820"><span class="figcap"><b>Figure 2 </b>Adding information</span><br><span><img id="elb_faq_0090__image117512241589" src="en-us_image_0000001794820077.jpg"></span></div>
|
||||||
<div class="note" id="elb_faq_0090__note627612152062"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="elb_faq_0090__p66517423613">Add the IP address range of the proxy server after <strong id="elb_faq_0090__b19751172824110">set_real_ip_from <IP_address></strong>.</p>
|
<div class="note" id="elb_faq_0090__note627612152062"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="elb_faq_0090__p66517423613">Add the IP address range of the proxy server after <strong id="elb_faq_0090__b19751172824110">set_real_ip_from <IP_address></strong>.</p>
|
||||||
<ul id="elb_faq_0090__ul382910413719"><li id="elb_faq_0090__li13829341171"><span id="elb_faq_0090__ph17309135819617">Shared</span> load balancers: 100.125.0.0/16<span id="elb_faq_0090__ph5282205074611"></span> and the IP address range used by the AAD service. Load balancers use IP addresses in 100.125.0.0/16<span id="elb_faq_0090__ph1317615314424"></span> to communicate with backend servers, and there are no security risks. Use commas (,) to separate multiple entries.</li></ul>
|
<ul id="elb_faq_0090__ul382910413719"><li id="elb_faq_0090__li13829341171"><span id="elb_faq_0090__ph1511175242510">Shared</span> load balancers: 100.125.0.0/16 and the IP address range used by the AAD service. Load balancers use IP addresses in 100.125.0.0/16 to communicate with backend servers, and there are no security risks. Use commas (,) to separate multiple entries.</li></ul>
|
||||||
<ul id="elb_faq_0090__ul410015111674"><li id="elb_faq_0090__li14373314679">Dedicated load balancers: CIDR block of the subnet where the load balancer resides</li></ul>
|
<ul id="elb_faq_0090__ul410015111674"><li id="elb_faq_0090__li14373314679">Dedicated load balancers: CIDR block of the subnet where the load balancer resides</li></ul>
|
||||||
</div></div>
|
</div></div>
|
||||||
</li><li id="elb_faq_0090__li641018965916">Start Nginx.<pre class="screen" id="elb_faq_0090__screen578563035916">/path/server/nginx/sbin/nginx</pre>
|
</li><li id="elb_faq_0090__li641018965916">Start Nginx.<pre class="screen" id="elb_faq_0090__screen578563035916">/path/server/nginx/sbin/nginx</pre>
|
||||||
@ -50,7 +50,7 @@ real_ip_header X-Forwarded-For;</pre>
|
|||||||
<ol id="elb_faq_0090__ol78072171526"><li id="elb_faq_0090__li2497621114416">Log in to a server on which Tomcat is installed.</li><li id="elb_faq_0090__li20249121115120">Check whether Tomcat is running properly.<pre class="screen" id="elb_faq_0090__screen44802295146">ps -ef|grep tomcat
|
<ol id="elb_faq_0090__ol78072171526"><li id="elb_faq_0090__li2497621114416">Log in to a server on which Tomcat is installed.</li><li id="elb_faq_0090__li20249121115120">Check whether Tomcat is running properly.<pre class="screen" id="elb_faq_0090__screen44802295146">ps -ef|grep tomcat
|
||||||
netstat -anpt|grep java</pre>
|
netstat -anpt|grep java</pre>
|
||||||
<div class="fignone" id="elb_faq_0090__fig4744183111150"><span class="figcap"><b>Figure 3 </b>Tomcat running properly</span><br><span><img id="elb_faq_0090__image12991039151611" src="en-us_image_0000001747381248.png"></span></div>
|
<div class="fignone" id="elb_faq_0090__fig4744183111150"><span class="figcap"><b>Figure 3 </b>Tomcat running properly</span><br><span><img id="elb_faq_0090__image12991039151611" src="en-us_image_0000001747381248.png"></span></div>
|
||||||
</li><li id="elb_faq_0090__li19727103382213">Modify <strong id="elb_faq_0090__b1571331418">className="org.apache.catalina.valves.AccessLogValve"</strong> in the <strong id="elb_faq_0090__b665121219558">server.xml</strong> file as follows:<pre class="screen" id="elb_faq_0090__screen129226593219">vim /usr/tomcat/tomcat8/conf/server.xml</pre>
|
</li><li id="elb_faq_0090__li19727103382213">Modify <strong id="elb_faq_0090__b1948222513262">className="org.apache.catalina.valves.AccessLogValve"</strong> in the <strong id="elb_faq_0090__b1148642582619">server.xml</strong> file as follows:<pre class="screen" id="elb_faq_0090__screen129226593219">vim /usr/tomcat/tomcat8/conf/server.xml</pre>
|
||||||
<pre class="screen" id="elb_faq_0090__screen19630859193119"><Valve className="org.apache.catalina.valves.AccessLogValve" directory="logs"
|
<pre class="screen" id="elb_faq_0090__screen19630859193119"><Valve className="org.apache.catalina.valves.AccessLogValve" directory="logs"
|
||||||
prefix="localhost_access_log." suffix=".txt"
|
prefix="localhost_access_log." suffix=".txt"
|
||||||
pattern="%{X-FORWARDED-FOR}i %l %u %t %r %s %b %D %q %{User-Agent}i %T" resolveHosts="false" /></pre>
|
pattern="%{X-FORWARDED-FOR}i %l %u %t %r %s %b %D %q %{User-Agent}i %T" resolveHosts="false" /></pre>
|
||||||
@ -78,9 +78,9 @@ cat localhost_access_log..2021-11-29.txt</pre>
|
|||||||
<p id="elb_faq_0090__p157754342011">For load balancing at Layer 4 (TCP/UDP), you can enable <strong id="elb_faq_0090__b16174151214303">Transfer Client IP Address</strong> to obtain the source IP address.</p>
|
<p id="elb_faq_0090__p157754342011">For load balancing at Layer 4 (TCP/UDP), you can enable <strong id="elb_faq_0090__b16174151214303">Transfer Client IP Address</strong> to obtain the source IP address.</p>
|
||||||
<ul id="elb_faq_0090__ul3140135223013"><li id="elb_faq_0090__li13140155233012"><strong id="elb_faq_0090__b6980112313279">Method 1 (for TCP or UDP listeners)</strong>: Enable <strong id="elb_faq_0090__b101155618413">Transfer Client IP Address</strong>.<div class="caution" id="elb_faq_0090__note163721259193419"><span class="cautiontitle"><img src="public_sys-resources/caution_3.0-en-us.png"> </span><div class="cautionbody"><ul id="elb_faq_0090__ul0161183124115"><li id="elb_faq_0090__li11982310114212">After this function is enabled, traffic, such as unidirectional download or push traffic, may be interrupted when backend servers are being migrated during the migration of the associated classic load balancer. After backend servers are migrated, retransmit the packets to restore the traffic.</li><li id="elb_faq_0090__li03069573459">After this function is enabled, the associated backend servers cannot be used as clients to access the listener.</li><li id="elb_faq_0090__li142889194478">If a backend server has been associated with the listener and health checks are enabled, enabling this function will check the health of the backend server, and traffic to this server will be interrupted for two health check intervals.</li></ul>
|
<ul id="elb_faq_0090__ul3140135223013"><li id="elb_faq_0090__li13140155233012"><strong id="elb_faq_0090__b6980112313279">Method 1 (for TCP or UDP listeners)</strong>: Enable <strong id="elb_faq_0090__b101155618413">Transfer Client IP Address</strong>.<div class="caution" id="elb_faq_0090__note163721259193419"><span class="cautiontitle"><img src="public_sys-resources/caution_3.0-en-us.png"> </span><div class="cautionbody"><ul id="elb_faq_0090__ul0161183124115"><li id="elb_faq_0090__li11982310114212">After this function is enabled, traffic, such as unidirectional download or push traffic, may be interrupted when backend servers are being migrated during the migration of the associated classic load balancer. After backend servers are migrated, retransmit the packets to restore the traffic.</li><li id="elb_faq_0090__li03069573459">After this function is enabled, the associated backend servers cannot be used as clients to access the listener.</li><li id="elb_faq_0090__li142889194478">If a backend server has been associated with the listener and health checks are enabled, enabling this function will check the health of the backend server, and traffic to this server will be interrupted for two health check intervals.</li></ul>
|
||||||
</div></div>
|
</div></div>
|
||||||
<ol id="elb_faq_0090__ol730222417346"><li id="elb_faq_0090__li330222433410">Perform the following steps to enable the function:<ol type="a" id="elb_faq_0090__ol16390953185514"><li id="elb_faq_0090__li677391520332">Log in to the management console.</li><li id="elb_faq_0090__li675519100420">In the upper left corner of the page, click <span><img id="elb_faq_0090__en-us_topic_0240829509_image1542118117117" src="en-us_image_0000001747739624.png"></span> and select the desired region and project.</li><li id="elb_faq_0090__li194625132711">Hover on <span><img id="elb_faq_0090__en-us_topic_0167652100_image762510132322" src="en-us_image_0000001794660485.png"></span> in the upper left corner to display <strong id="elb_faq_0090__en-us_topic_0167652100_b9121102522212">Service List</strong> and choose <strong id="elb_faq_0090__en-us_topic_0167652100_b61222025142217">Network</strong> > <strong id="elb_faq_0090__en-us_topic_0167652100_b4124425142210">Elastic Load Balancing</strong>. </li><li id="elb_faq_0090__li1379615339436">In the load balancer list, click the name of the load balancer.</li><li id="elb_faq_0090__li475294174319">Click <strong id="elb_faq_0090__b1858064398">Listeners</strong>.<ul id="elb_faq_0090__ul124372032185517"><li id="elb_faq_0090__li543763255519">To add a listener, click <strong id="elb_faq_0090__b1377149182415">Add Listener</strong>.</li><li id="elb_faq_0090__li12437132115511">To modify a listener, locate the listener, click <span><img id="elb_faq_0090__image18771457113315" src="en-us_image_0000001747740100.png"></span> on the right of its name, and click <strong id="elb_faq_0090__b388015743316">Modify Listener</strong>. In the <strong id="elb_faq_0090__b6881165715337">Modify Listener</strong> dialog box, modify the parameters as needed.</li></ul>
|
<ol id="elb_faq_0090__ol730222417346"><li id="elb_faq_0090__li330222433410">Perform the following steps to enable the function:<ol type="a" id="elb_faq_0090__ol16390953185514"><li id="elb_faq_0090__li677391520332">Log in to the management console.</li><li id="elb_faq_0090__li675519100420">In the upper left corner of the page, click <span><img id="elb_faq_0090__image77755232952126" src="en-us_image_0000001747739624.png"></span> and select the desired region and project.</li><li id="elb_faq_0090__li194625132711">Click <span><img id="elb_faq_0090__image208721291952130" src="en-us_image_0000001794660485.png"></span> in the upper left corner to display <strong id="elb_faq_0090__b49993403052130">Service List</strong> and choose <strong id="elb_faq_0090__b88819871252130">Network</strong> > <strong id="elb_faq_0090__b34359211152130">Elastic Load Balancing</strong>.</li><li id="elb_faq_0090__li1379615339436">In the load balancer list, click the name of the load balancer.</li><li id="elb_faq_0090__li475294174319">Click <strong id="elb_faq_0090__b1231197849">Listeners</strong>.<ul id="elb_faq_0090__ul124372032185517"><li id="elb_faq_0090__li543763255519">To add a listener, click <strong id="elb_faq_0090__b1377149182415">Add Listener</strong>.</li><li id="elb_faq_0090__li12437132115511">To modify a listener, locate the listener, click <span><img id="elb_faq_0090__image18771457113315" src="en-us_image_0000001747740100.png"></span> on the right of its name, and click <strong id="elb_faq_0090__b388015743316">Modify Listener</strong>. In the <strong id="elb_faq_0090__b6881165715337">Modify Listener</strong> dialog box, modify the parameters as needed.</li></ul>
|
||||||
</li><li id="elb_faq_0090__li3100135715344">Enable <strong id="elb_faq_0090__b745821111385">Transfer Client IP Address</strong>.</li></ol>
|
</li><li id="elb_faq_0090__li3100135715344">Enable <strong id="elb_faq_0090__b745821111385">Transfer Client IP Address</strong>.</li></ol>
|
||||||
</li><li id="elb_faq_0090__li99008095116">Configure security groups, network ACLs, and OS and software security policies so that IP addresses of the clients can access these backend servers.<div class="note" id="elb_faq_0090__note9800635192119"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="elb_faq_0090__p17774359172118">If you enable this function, a server cannot be used as both the client and the backend server. If the client and the backend server use the same server and the <strong id="elb_faq_0090__b1799864913">Transfer Client IP Address</strong> option is enabled, the backend server will think the packet from the client is sent by itself and will not return a response packet to the load balancer. As a result, the return traffic will be interrupted.</p>
|
</li><li id="elb_faq_0090__li99008095116">Configure security groups, firewalls, and OS and software security policies so that IP addresses of the clients can access these backend servers.<div class="note" id="elb_faq_0090__note9800635192119"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="elb_faq_0090__p17774359172118">If <strong id="elb_faq_0090__b102626566293">Transfer Client IP Address</strong> is enabled, a server cannot serve as both a backend server and a client. If the client and the backend server use the same server and the <strong id="elb_faq_0090__b1651062122">Transfer Client IP Address</strong> option is enabled, the backend server will think the packet from the client is sent by itself and will not return a response packet to the load balancer. As a result, the return traffic will be interrupted.</p>
|
||||||
</div></div>
|
</div></div>
|
||||||
</li></ol>
|
</li></ol>
|
||||||
</li></ul>
|
</li></ul>
|
||||||
|
@ -1,7 +1,7 @@
|
|||||||
<a name="elb_faq_0114"></a><a name="elb_faq_0114"></a>
|
<a name="elb_faq_0114"></a><a name="elb_faq_0114"></a>
|
||||||
|
|
||||||
<h1 class="topictitle1">Why Does ELB Frequently Send Requests to Backend Servers During Health Checks?</h1>
|
<h1 class="topictitle1">Why Does ELB Frequently Send Requests to Backend Servers During Health Checks?</h1>
|
||||||
<div id="body1566463545231"><p id="elb_faq_0114__p089414334718">ELB is deployed in clusters, and all nodes for request forwarding in the cluster send requests to backend servers at the same time. If the health check interval is too short, health checks are performed once every few seconds, and a large number of packets are sent to backend servers. To control the frequency of access to backend servers, change the health check interval by referring to <a href="en-us_topic_0162227063.html">Configuring a Health Check</a>.</p>
|
<div id="body1566463545231"><p id="elb_faq_0114__p089414334718">ELB is deployed in clusters, and all nodes for request forwarding in the cluster send requests to backend servers at the same time. If the health check interval is too short, health checks are performed once every few seconds, and a large number of packets are sent to backend servers. To control the frequency of access to backend servers, change the health check interval by referring to <a href="en-us_topic_0000001747380572.html">Modifying Health Check Settings</a>.</p>
|
||||||
</div>
|
</div>
|
||||||
<div>
|
<div>
|
||||||
<div class="familylinks">
|
<div class="familylinks">
|
||||||
|
@ -1,7 +1,7 @@
|
|||||||
<a name="elb_faq_0124"></a><a name="elb_faq_0124"></a>
|
<a name="elb_faq_0124"></a><a name="elb_faq_0124"></a>
|
||||||
|
|
||||||
<h1 class="topictitle1">Why Can I Access Backend Servers After a Whitelist Is Configured?</h1>
|
<h1 class="topictitle1">Why Can I Access Backend Servers After a Whitelist Is Configured?</h1>
|
||||||
<div id="body1588062642982"><p id="elb_faq_0124__p14327152719345">The whitelist controls only access to a listener. Only IP addresses in the whitelist can access the listener. To control access to backend servers, you can configure <span id="elb_faq_0124__en-us_topic_0000001390784280_ph3292026172912">Firewall</span> or security group rules.</p>
|
<div id="body1588062642982"><p id="elb_faq_0124__p14327152719345">The whitelist controls only access to a listener. Only IP addresses in the whitelist can access the listener. To control access to backend servers, you can configure firewalls or security group rules.</p>
|
||||||
<p id="elb_faq_0124__p8060118"></p>
|
<p id="elb_faq_0124__p8060118"></p>
|
||||||
</div>
|
</div>
|
||||||
<div>
|
<div>
|
||||||
|
@ -1,7 +1,7 @@
|
|||||||
<a name="elb_faq_0135"></a><a name="elb_faq_0135"></a>
|
<a name="elb_faq_0135"></a><a name="elb_faq_0135"></a>
|
||||||
|
|
||||||
<h1 class="topictitle1">Can ELB Be Used Across Accounts or VPCs?</h1>
|
<h1 class="topictitle1">Can ELB Be Used Across Accounts or VPCs?</h1>
|
||||||
<div id="body1590464381352"><ul id="elb_faq_0135__ul1875610623020"><li id="elb_faq_0135__li89051910123112">Your <span id="elb_faq_0135__ph660616083117">Shared</span> load balancers cannot be used by another account, and you cannot associate backend servers whose VPCs are not the same as the load balancers.</li><li id="elb_faq_0135__li17784848448">For <span id="elb_faq_0135__ph48931152183716">Dedicated load balancer</span>s, you can add servers in a VPC connected using a VPC peering connection, in a VPC in another region and connected through a cloud connection, or in an on-premises data center at the other end of a Direct Connect or VPN connection, by using their IP addresses. For details, see section <a href="elb_ug_hd_0005.html">Configuring Hybrid Load Balancing</a> in <em id="elb_faq_0135__i22091139109">Elastic Load Balance User Guide</em>.</li></ul>
|
<div id="body1590464381352"><ul id="elb_faq_0135__ul1875610623020"><li id="elb_faq_0135__li89051910123112"><span id="elb_faq_0135__ph660616083117">Shared</span> load balancers cannot be used across accounts and cannot route traffic to backend servers in VPCs that are different from the VPCs of the load balancers.</li><li id="elb_faq_0135__li17784848448"><span id="elb_faq_0135__ph48931152183716">For dedicated load balancers, you can add servers in a VPC connected using a VPC peering connection, in a VPC in another region and connected through a cloud connection, or in an on-premises data center at the other end of a Direct Connect or VPN connection, by using their IP addresses.</span> For details, see <a href="elb_ug_hd3_0004_01.html">Overview</a>.</li></ul>
|
||||||
</div>
|
</div>
|
||||||
<div>
|
<div>
|
||||||
<div class="familylinks">
|
<div class="familylinks">
|
||||||
|
File diff suppressed because it is too large
Load Diff
File diff suppressed because it is too large
Load Diff
@ -3,16 +3,16 @@
|
|||||||
<h1 class="topictitle1">Using Dedicated Load Balancers (Advanced Level)</h1>
|
<h1 class="topictitle1">Using Dedicated Load Balancers (Advanced Level)</h1>
|
||||||
<div id="body0000001080005612"><div class="section" id="elb_qs_0003__section18950295143553"><h4 class="sectiontitle">Scenarios</h4><p id="elb_qs_0003__p13318235811">You have two web applications that are deployed on separated ECSs but use the same domain name for access. You can set different URLs to process requests.</p>
|
<div id="body0000001080005612"><div class="section" id="elb_qs_0003__section18950295143553"><h4 class="sectiontitle">Scenarios</h4><p id="elb_qs_0003__p13318235811">You have two web applications that are deployed on separated ECSs but use the same domain name for access. You can set different URLs to process requests.</p>
|
||||||
<p id="elb_qs_0003__p14697175632114">To forward requests based on URLs, you need to create a load balancer, add an HTTP or HTTPS listener, and add forwarding policies to specify the URLs.</p>
|
<p id="elb_qs_0003__p14697175632114">To forward requests based on URLs, you need to create a load balancer, add an HTTP or HTTPS listener, and add forwarding policies to specify the URLs.</p>
|
||||||
<p id="elb_qs_0003__p66625093192530">An HTTP listener is used as an example to describe how to route requests from two URLs (<strong id="elb_qs_0003__b104391544581">/ELB01</strong> and <strong id="elb_qs_0003__b113284714586">/ELB02</strong>) of the same domain name (www.example.com) to different backend servers.</p>
|
<p id="elb_qs_0003__p66625093192530">An HTTP listener is used as an example to describe how to route requests from two URLs (<strong id="elb_qs_0003__b14506131414206">/ELB01</strong> and <strong id="elb_qs_0003__b1050771415200">/ELB02</strong>) of the same domain name (www.example.com) to different backend servers.</p>
|
||||||
</div>
|
</div>
|
||||||
<div class="section" id="elb_qs_0003__section3453061616119"><h4 class="sectiontitle">Prerequisites</h4><ul id="elb_qs_0003__ul15892133835819"><li id="elb_qs_0003__li169934443213">You have added security group rules to allow traffic from the ports used by the two ECSs. (Alternatively, you can enable all ports first and then disable the ports that are no longer used after service deployment.)</li><li id="elb_qs_0003__li16288402223">You have verified that the security group containing the ECSs allows access traffic from the VPC where the load balancer works and that the health check function is normal.<div class="note" id="elb_qs_0003__note2297145295010"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="elb_qs_0003__en-us_topic_0000001126827555_p1297043018186">If <strong id="elb_qs_0003__b166421137155816">IP as a Backend</strong> is not enabled for a dedicated load balancer that has a TCP or UDP listener, there is no need to configure security group rules to allow traffic from the VPC where the load balancer backend subnet works to the backend servers.</p>
|
<div class="section" id="elb_qs_0003__section3453061616119"><h4 class="sectiontitle">Prerequisites</h4><ul id="elb_qs_0003__ul15892133835819"><li id="elb_qs_0003__li169934443213">You have added security group rules to allow traffic from the ports used by the two ECSs. (Alternatively, you can enable all ports first and then disable the ports that are no longer used after service deployment.)</li><li id="elb_qs_0003__li16288402223">You have verified that the security group containing the ECSs allows access traffic from the VPC where the load balancer works and that the health check function is normal.<div class="note" id="elb_qs_0003__note2297145295010"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="elb_qs_0003__en-us_topic_0000001126827555_p1297043018186">If <strong id="elb_qs_0003__b1548161216271">IP as a Backend</strong> is not enabled for a dedicated load balancer that has a TCP or UDP listener, there is no need to configure security group rules to allow traffic from the VPC where the load balancer backend subnet works to the backend servers.</p>
|
||||||
</div></div>
|
</div></div>
|
||||||
</li></ul>
|
</li></ul>
|
||||||
</div>
|
</div>
|
||||||
<div class="section" id="elb_qs_0003__section29839590578"><h4 class="sectiontitle">Creating ECSs</h4><p id="elb_qs_0003__en-us_topic_0166358908_p17398174135812">ECSs are used as backend servers.</p>
|
<div class="section" id="elb_qs_0003__section29839590578"><h4 class="sectiontitle">Creating ECSs</h4><p id="elb_qs_0003__en-us_topic_0166358908_p17398174135812">ECSs are used as backend servers.</p>
|
||||||
<p id="elb_qs_0003__en-us_topic_0166358908_p1323855715215">Each ECS needs an EIP for accessing the Internet and configuring the application on the ECS.</p>
|
<p id="elb_qs_0003__en-us_topic_0166358908_p1323855715215">Each ECS needs an EIP for accessing the Internet and configuring the application on the ECS.</p>
|
||||||
</div>
|
</div>
|
||||||
<ol id="elb_qs_0003__ol09857595579"><li id="elb_qs_0003__en-us_topic_0166358908_li18503134213513">Log in to the management console.</li><li id="elb_qs_0003__en-us_topic_0166358908_li1658495082510">In the upper left corner of the page, click <span><img id="elb_qs_0003__image92319195613" src="en-us_image_0000001747739624.png"></span> and select the desired region and project.</li><li id="elb_qs_0003__en-us_topic_0166358908_li1561583452013">Hover on <span><img id="elb_qs_0003__image191851623534759" src="en-us_image_0000001747380972.png"></span> in the upper left corner to display <strong id="elb_qs_0003__b143191738434759">Service List</strong> and choose <strong id="elb_qs_0003__b41717250434759">Computing</strong> > <strong id="elb_qs_0003__b39863341034759">Elastic Cloud Server</strong>.</li><li id="elb_qs_0003__en-us_topic_0166358908_li12985204673513"><p id="elb_qs_0003__en-us_topic_0166358908_p09941142915"><a name="elb_qs_0003__en-us_topic_0166358908_li12985204673513"></a><a name="en-us_topic_0166358908_li12985204673513"></a>Click <strong id="elb_qs_0003__b118581471934759">Create ECS</strong>, configure the parameters, and click <strong id="elb_qs_0003__b66343763334759">Create Now</strong>.</p>
|
<ol id="elb_qs_0003__ol09857595579"><li id="elb_qs_0003__en-us_topic_0166358908_li18503134213513">Log in to the management console.</li><li id="elb_qs_0003__en-us_topic_0166358908_li1658495082510">In the upper left corner of the page, click <span><img id="elb_qs_0003__image92319195613" src="en-us_image_0000001747739624.png"></span> and select the desired region and project.</li><li id="elb_qs_0003__en-us_topic_0166358908_li1561583452013">Click <span><img id="elb_qs_0003__image191851623534759" src="en-us_image_0000001747380972.png"></span> in the upper left corner to display <strong id="elb_qs_0003__b143191738434759">Service List</strong> and choose <strong id="elb_qs_0003__b41717250434759">Computing</strong> > <strong id="elb_qs_0003__b39863341034759">Elastic Cloud Server</strong>.</li><li id="elb_qs_0003__en-us_topic_0166358908_li12985204673513"><p id="elb_qs_0003__en-us_topic_0166358908_p09941142915"><a name="elb_qs_0003__en-us_topic_0166358908_li12985204673513"></a><a name="en-us_topic_0166358908_li12985204673513"></a>Click <strong id="elb_qs_0003__b118581471934759">Create ECS</strong>, configure the parameters, and click <strong id="elb_qs_0003__b66343763334759">Create Now</strong>.</p>
|
||||||
<p id="elb_qs_0003__en-us_topic_0166358908_p1745011147553"></p>
|
<p id="elb_qs_0003__en-us_topic_0166358908_p1745011147553"></p>
|
||||||
<div class="p" id="elb_qs_0003__en-us_topic_0166358908_p1745013149557">The following table lists the specifications of the two ECSs.
|
<div class="p" id="elb_qs_0003__en-us_topic_0166358908_p1745013149557">The following table lists the specifications of the two ECSs.
|
||||||
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="elb_qs_0003__en-us_topic_0166358908_table169305003620" frame="border" border="1" rules="all"><caption><b>Table 1 </b>ECS specifications</caption><thead align="left"><tr id="elb_qs_0003__en-us_topic_0166358908_row1926804361"><th align="left" class="cellrowborder" valign="top" width="46.949999999999996%" id="mcps1.3.4.4.3.1.2.3.1.1"><p id="elb_qs_0003__en-us_topic_0166358908_p1892518019366"><strong id="elb_qs_0003__b176927738034759">Item</strong></p>
|
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="elb_qs_0003__en-us_topic_0166358908_table169305003620" frame="border" border="1" rules="all"><caption><b>Table 1 </b>ECS specifications</caption><thead align="left"><tr id="elb_qs_0003__en-us_topic_0166358908_row1926804361"><th align="left" class="cellrowborder" valign="top" width="46.949999999999996%" id="mcps1.3.4.4.3.1.2.3.1.1"><p id="elb_qs_0003__en-us_topic_0166358908_p1892518019366"><strong id="elb_qs_0003__b176927738034759">Item</strong></p>
|
||||||
@ -31,9 +31,9 @@
|
|||||||
<td class="cellrowborder" valign="top" width="53.05%" headers="mcps1.3.4.4.3.1.2.3.1.2 "><p id="elb_qs_0003__en-us_topic_0166358908_p4926180103613">CentOS 7.2 64bit</p>
|
<td class="cellrowborder" valign="top" width="53.05%" headers="mcps1.3.4.4.3.1.2.3.1.2 "><p id="elb_qs_0003__en-us_topic_0166358908_p4926180103613">CentOS 7.2 64bit</p>
|
||||||
</td>
|
</td>
|
||||||
</tr>
|
</tr>
|
||||||
<tr id="elb_qs_0003__en-us_topic_0166358908_row192710163612"><td class="cellrowborder" valign="top" width="46.949999999999996%" headers="mcps1.3.4.4.3.1.2.3.1.1 "><p id="elb_qs_0003__en-us_topic_0166358908_p892618033614">CPU</p>
|
<tr id="elb_qs_0003__en-us_topic_0166358908_row192710163612"><td class="cellrowborder" valign="top" width="46.949999999999996%" headers="mcps1.3.4.4.3.1.2.3.1.1 "><p id="elb_qs_0003__en-us_topic_0166358908_p892618033614">vCPUs</p>
|
||||||
</td>
|
</td>
|
||||||
<td class="cellrowborder" valign="top" width="53.05%" headers="mcps1.3.4.4.3.1.2.3.1.2 "><p id="elb_qs_0003__en-us_topic_0166358908_p5927180103614">2vCPUs</p>
|
<td class="cellrowborder" valign="top" width="53.05%" headers="mcps1.3.4.4.3.1.2.3.1.2 "><p id="elb_qs_0003__en-us_topic_0166358908_p5927180103614">2</p>
|
||||||
</td>
|
</td>
|
||||||
</tr>
|
</tr>
|
||||||
<tr id="elb_qs_0003__en-us_topic_0166358908_row1592812043617"><td class="cellrowborder" valign="top" width="46.949999999999996%" headers="mcps1.3.4.4.3.1.2.3.1.1 "><p id="elb_qs_0003__en-us_topic_0166358908_p129271407366">Memory</p>
|
<tr id="elb_qs_0003__en-us_topic_0166358908_row1592812043617"><td class="cellrowborder" valign="top" width="46.949999999999996%" headers="mcps1.3.4.4.3.1.2.3.1.1 "><p id="elb_qs_0003__en-us_topic_0166358908_p129271407366">Memory</p>
|
||||||
@ -122,11 +122,11 @@ systemctl enable nginx</pre>
|
|||||||
</li></ol>
|
</li></ol>
|
||||||
</div>
|
</div>
|
||||||
<div class="section" id="elb_qs_0003__section15436447172917"><h4 class="sectiontitle">Creating a Load Balancer</h4><p id="elb_qs_0003__p229893917615">Each ECS needs an EIP for accessing the Internet and configuring the application on the ECS. The load balancer needs an EIP to access the application deployed on the ECSs over the Internet. You can determine whether to bind an EIP to the load balancer based on your requirements. For details, see <a href="elb_pro_01_0004.html">Load Balancing on a Public or Private Network</a>.</p>
|
<div class="section" id="elb_qs_0003__section15436447172917"><h4 class="sectiontitle">Creating a Load Balancer</h4><p id="elb_qs_0003__p229893917615">Each ECS needs an EIP for accessing the Internet and configuring the application on the ECS. The load balancer needs an EIP to access the application deployed on the ECSs over the Internet. You can determine whether to bind an EIP to the load balancer based on your requirements. For details, see <a href="elb_pro_01_0004.html">Load Balancing on a Public or Private Network</a>.</p>
|
||||||
<ol id="elb_qs_0003__ol353744134512"><li id="elb_qs_0003__li1131682861711">In the upper left corner of the page, click <span><img id="elb_qs_0003__image258891312332" src="en-us_image_0000001747739624.png"></span> and select the desired region and project.</li><li id="elb_qs_0003__li17301740102218">Hover on <span><img id="elb_qs_0003__image42795691334759" src="en-us_image_0000001794660485.png"></span> in the upper left corner to display <strong id="elb_qs_0003__b165511356234759">Service List</strong> and choose <strong id="elb_qs_0003__b97020447334759">Network</strong> > <strong id="elb_qs_0003__b32510415734759">Elastic Load Balancing</strong>. </li><li id="elb_qs_0003__li59220156440">Click <strong id="elb_qs_0003__b16789101818419">Create Elastic Load Balancer</strong> and then configure the parameters.</li><li id="elb_qs_0003__li18940143983112">Click <strong id="elb_qs_0003__b105180856134759">Create Now</strong>.</li><li id="elb_qs_0003__li9984122593614">Confirm the configuration and submit your request.</li><li id="elb_qs_0003__li15984202593610">View the newly created load balancer in the load balancer list.</li></ol>
|
<ol id="elb_qs_0003__ol353744134512"><li id="elb_qs_0003__li1131682861711">In the upper left corner of the page, click <span><img id="elb_qs_0003__image258891312332" src="en-us_image_0000001747739624.png"></span> and select the desired region and project.</li><li id="elb_qs_0003__li17301740102218">Click <span><img id="elb_qs_0003__image42795691334759" src="en-us_image_0000001794660485.png"></span> in the upper left corner to display <strong id="elb_qs_0003__b165511356234759">Service List</strong> and choose <strong id="elb_qs_0003__b97020447334759">Network</strong> > <strong id="elb_qs_0003__b32510415734759">Elastic Load Balancing</strong>. </li><li id="elb_qs_0003__li59220156440">Click <strong id="elb_qs_0003__b16789101818419">Create Elastic Load Balancer</strong> and then configure the parameters.</li><li id="elb_qs_0003__li18940143983112">Click <strong id="elb_qs_0003__b105180856134759">Create Now</strong>.</li><li id="elb_qs_0003__li9984122593614">Confirm the configuration and submit your request.</li><li id="elb_qs_0003__li15984202593610">View the newly created load balancer in the load balancer list.</li></ol>
|
||||||
<div class="note" id="elb_qs_0003__note171711554395"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="elb_qs_0003__en-us_topic_0000001126827555_p817755163912">After you create a dedicated load balancer, configure the security group that contains the ECSs to allow traffic from the VPC where the load balancer works.</p>
|
<div class="note" id="elb_qs_0003__note171711554395"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="elb_qs_0003__en-us_topic_0000001126827555_p817755163912">After you create a dedicated load balancer, configure the security group that contains the ECSs to allow traffic from the VPC where the load balancer works.</p>
|
||||||
</div></div>
|
</div></div>
|
||||||
</div>
|
</div>
|
||||||
<div class="section" id="elb_qs_0003__section26032025134916"><h4 class="sectiontitle">Procedure</h4><ol id="elb_qs_0003__en-us_topic_0000001125381517_ol198141563813"><li id="elb_qs_0003__en-us_topic_0000001125381517_li677391520332">Log in to the management console.</li><li id="elb_qs_0003__en-us_topic_0000001125381517_li675519100420">In the upper left corner of the page, click <span><img id="elb_qs_0003__image741139113310" src="en-us_image_0000001747739624.png"></span> and select the desired region and project.</li><li id="elb_qs_0003__en-us_topic_0000001125381517_en-us_topic_0029320966_li50026016224047">Under <strong id="elb_qs_0003__b7554114310331">Computing</strong>, click <strong id="elb_qs_0003__b1955534313312">Elastic Cloud Server</strong>.</li><li id="elb_qs_0003__en-us_topic_0000001125381517_li34401539214315">On the <strong id="elb_qs_0003__b163171959434759">Elastic Cloud Server</strong> page, click the name of the ECS that has been added to a backend server group.<p id="elb_qs_0003__en-us_topic_0000001125381517_p19982029214319">The page providing details about the ECS is displayed.</p>
|
<div class="section" id="elb_qs_0003__section26032025134916"><h4 class="sectiontitle">Configuring Security Group Rules</h4><ol id="elb_qs_0003__en-us_topic_0000001125381517_ol198141563813"><li id="elb_qs_0003__en-us_topic_0000001125381517_li677391520332">Log in to the management console.</li><li id="elb_qs_0003__en-us_topic_0000001125381517_li675519100420">In the upper left corner of the page, click <span><img id="elb_qs_0003__image741139113310" src="en-us_image_0000001747739624.png"></span> and select the desired region and project.</li><li id="elb_qs_0003__en-us_topic_0000001125381517_en-us_topic_0029320966_li50026016224047">Click <span><img id="elb_qs_0003__image36431824122715" src="en-us_image_0000001747380972.png"></span> in the upper left corner to display <strong id="elb_qs_0003__b10643162410273">Service List</strong> and choose <strong id="elb_qs_0003__b3643192412710">Computing</strong> > <strong id="elb_qs_0003__b364392413274">Elastic Cloud Server</strong>.</li><li id="elb_qs_0003__en-us_topic_0000001125381517_li34401539214315">On the <strong id="elb_qs_0003__b17347154465018">Elastic Cloud Server</strong> page, click the name of the ECS that has been added to a backend server group.<p id="elb_qs_0003__en-us_topic_0000001125381517_p19982029214319">The page providing details about the ECS is displayed.</p>
|
||||||
</li><li id="elb_qs_0003__en-us_topic_0000001125381517_li18750165432511">Click <strong id="elb_qs_0003__b108230856434759">Security Groups</strong>, locate the security group, and view security group rules.</li><li id="elb_qs_0003__en-us_topic_0000001125381517_li45534692214355">Click the security group rule ID or <strong id="elb_qs_0003__b169392652634759">Modify Security Group Rule</strong>. The security group details page is displayed.</li><li id="elb_qs_0003__en-us_topic_0000001125381517_en-us_topic_0000001390784280_en-us_topic_0029320966_li46525942225810">On the<strong id="elb_qs_0003__b112255653734759"> Inbound Rules</strong> tab page, click <strong id="elb_qs_0003__b144562385134759">Add Rule</strong>. Configure an inbound rule based on <a href="#elb_qs_0003__en-us_topic_0000001125381517_en-us_topic_0000001420502298_en-us_topic_0000001390784280_table22703095416">Table 2</a>.
|
</li><li id="elb_qs_0003__en-us_topic_0000001125381517_li18750165432511">Click <strong id="elb_qs_0003__b108230856434759">Security Groups</strong>, locate the security group, and view security group rules.</li><li id="elb_qs_0003__en-us_topic_0000001125381517_li45534692214355">Click the security group rule ID or <strong id="elb_qs_0003__b169392652634759">Modify Security Group Rule</strong>. The security group details page is displayed.</li><li id="elb_qs_0003__en-us_topic_0000001125381517_en-us_topic_0000001390784280_en-us_topic_0029320966_li46525942225810">On the<strong id="elb_qs_0003__b112255653734759"> Inbound Rules</strong> tab page, click <strong id="elb_qs_0003__b144562385134759">Add Rule</strong>. Configure an inbound rule based on <a href="#elb_qs_0003__en-us_topic_0000001125381517_en-us_topic_0000001420502298_en-us_topic_0000001390784280_table22703095416">Table 2</a>.
|
||||||
<div class="tablenoborder"><a name="elb_qs_0003__en-us_topic_0000001125381517_en-us_topic_0000001420502298_en-us_topic_0000001390784280_table22703095416"></a><a name="en-us_topic_0000001125381517_en-us_topic_0000001420502298_en-us_topic_0000001390784280_table22703095416"></a><table cellpadding="4" cellspacing="0" summary="" id="elb_qs_0003__en-us_topic_0000001125381517_en-us_topic_0000001420502298_en-us_topic_0000001390784280_table22703095416" frame="border" border="1" rules="all"><caption><b>Table 2 </b>Security group rules</caption><thead align="left"><tr id="elb_qs_0003__en-us_topic_0000001125381517_en-us_topic_0000001420502298_en-us_topic_0000001390784280_row102813095415"><th align="left" class="cellrowborder" valign="top" width="22.95%" id="mcps1.3.7.2.7.4.2.5.1.1"><p id="elb_qs_0003__en-us_topic_0000001125381517_en-us_topic_0000001420502298_en-us_topic_0000001390784280_p428103020541">Backend Protocol</p>
|
<div class="tablenoborder"><a name="elb_qs_0003__en-us_topic_0000001125381517_en-us_topic_0000001420502298_en-us_topic_0000001390784280_table22703095416"></a><a name="en-us_topic_0000001125381517_en-us_topic_0000001420502298_en-us_topic_0000001390784280_table22703095416"></a><table cellpadding="4" cellspacing="0" summary="" id="elb_qs_0003__en-us_topic_0000001125381517_en-us_topic_0000001420502298_en-us_topic_0000001390784280_table22703095416" frame="border" border="1" rules="all"><caption><b>Table 2 </b>Security group rules</caption><thead align="left"><tr id="elb_qs_0003__en-us_topic_0000001125381517_en-us_topic_0000001420502298_en-us_topic_0000001390784280_row102813095415"><th align="left" class="cellrowborder" valign="top" width="22.95%" id="mcps1.3.7.2.7.4.2.5.1.1"><p id="elb_qs_0003__en-us_topic_0000001125381517_en-us_topic_0000001420502298_en-us_topic_0000001390784280_p428103020541">Backend Protocol</p>
|
||||||
</th>
|
</th>
|
||||||
@ -143,7 +143,7 @@ systemctl enable nginx</pre>
|
|||||||
<td class="cellrowborder" valign="top" width="22.68%" headers="mcps1.3.7.2.7.4.2.5.1.2 "><p id="elb_qs_0003__en-us_topic_0000001125381517_en-us_topic_0000001420502298_en-us_topic_0000001390784280_p1728113025413">Allow</p>
|
<td class="cellrowborder" valign="top" width="22.68%" headers="mcps1.3.7.2.7.4.2.5.1.2 "><p id="elb_qs_0003__en-us_topic_0000001125381517_en-us_topic_0000001420502298_en-us_topic_0000001390784280_p1728113025413">Allow</p>
|
||||||
</td>
|
</td>
|
||||||
<td class="cellrowborder" valign="top" width="29.37%" headers="mcps1.3.7.2.7.4.2.5.1.3 "><p id="elb_qs_0003__en-us_topic_0000001125381517_en-us_topic_0000001420502298_en-us_topic_0000001390784280_p14281430155413"><strong id="elb_qs_0003__b187910197834759">Protocol</strong>: TCP</p>
|
<td class="cellrowborder" valign="top" width="29.37%" headers="mcps1.3.7.2.7.4.2.5.1.3 "><p id="elb_qs_0003__en-us_topic_0000001125381517_en-us_topic_0000001420502298_en-us_topic_0000001390784280_p14281430155413"><strong id="elb_qs_0003__b187910197834759">Protocol</strong>: TCP</p>
|
||||||
<p id="elb_qs_0003__en-us_topic_0000001125381517_en-us_topic_0000001420502298_en-us_topic_0000001390784280_p1499745325519"><strong id="elb_qs_0003__b73702405134759">Port</strong>: the port used by the backend server and health check port</p>
|
<p id="elb_qs_0003__en-us_topic_0000001125381517_en-us_topic_0000001420502298_en-us_topic_0000001390784280_p1499745325519"><strong id="elb_qs_0003__b18339183519719">Port</strong>: the port used by the backend server and health check port</p>
|
||||||
</td>
|
</td>
|
||||||
<td class="cellrowborder" rowspan="3" valign="top" width="25%" headers="mcps1.3.7.2.7.4.2.5.1.4 "><p id="elb_qs_0003__en-us_topic_0000001125381517_en-us_topic_0000001420502298_en-us_topic_0000001390784280_p42853012545">Backend subnet of the load balancer</p>
|
<td class="cellrowborder" rowspan="3" valign="top" width="25%" headers="mcps1.3.7.2.7.4.2.5.1.4 "><p id="elb_qs_0003__en-us_topic_0000001125381517_en-us_topic_0000001420502298_en-us_topic_0000001390784280_p42853012545">Backend subnet of the load balancer</p>
|
||||||
</td>
|
</td>
|
||||||
@ -171,26 +171,26 @@ systemctl enable nginx</pre>
|
|||||||
</div></div>
|
</div></div>
|
||||||
</li><li id="elb_qs_0003__en-us_topic_0000001125381517_li1030715242413">Click <strong id="elb_qs_0003__b73532077534759">OK</strong>.</li></ol>
|
</li><li id="elb_qs_0003__en-us_topic_0000001125381517_li1030715242413">Click <strong id="elb_qs_0003__b73532077534759">OK</strong>.</li></ol>
|
||||||
</div>
|
</div>
|
||||||
<div class="section" id="elb_qs_0003__section1261104918577"><h4 class="sectiontitle">Firewall Rules</h4><p id="elb_qs_0003__en-us_topic_0000001126827555_en-us_topic_0000001125381517_p3997193819710">To control traffic in and out of a subnet, you can associate a firewall with the subnet. Firewalls rules control access to subnets and add an additional layer of defense to your subnets. The default <span id="elb_qs_0003__ph1251994574216">firewall</span> rule denies all inbound and outbound traffic. If the subnet of a load balancer or associated backend servers has a <span id="elb_qs_0003__ph7746936184417">firewall</span> rule associated, the load balancer cannot receive traffic from the Internet or route traffic to backend servers, and backend servers cannot receive traffic from and respond to the load balancer.</p>
|
<div class="section" id="elb_qs_0003__section1261104918577"><h4 class="sectiontitle">Firewall Rules</h4><p id="elb_qs_0003__en-us_topic_0000001126827555_en-us_topic_0000001125381517_p3997193819710">To control traffic in and out of a subnet, you can associate a firewall with the subnet. Firewalls rules control access to subnets and add an additional layer of defense to your subnets. Default <span id="elb_qs_0003__ph545213916372">firewall</span> rules reject all inbound and outbound traffic. If the subnet of a load balancer or associated backend servers has a <span id="elb_qs_0003__ph14546913711">firewall</span> associated, the load balancer cannot receive traffic from the Internet or route traffic to backend servers, and backend servers cannot receive traffic from and respond to the load balancer.</p>
|
||||||
<p id="elb_qs_0003__en-us_topic_0000001126827555_en-us_topic_0000001125381517_p79433211595">Configure an inbound firewall rule to allow traffic from the VPC where the load balancer resides to backend servers.</p>
|
<p id="elb_qs_0003__en-us_topic_0000001126827555_en-us_topic_0000001125381517_p79433211595">Configure an inbound firewall rule to allow traffic from the VPC where the load balancer resides to backend servers.</p>
|
||||||
<ol id="elb_qs_0003__en-us_topic_0000001126827555_en-us_topic_0000001125381517_ol17965143881417"><li id="elb_qs_0003__en-us_topic_0000001126827555_en-us_topic_0000001125381517_li20860192818532">Log in to the management console.</li><li id="elb_qs_0003__en-us_topic_0000001126827555_en-us_topic_0000001125381517_li1486022812537">In the upper left corner of the page, click <span><img id="elb_qs_0003__image94944575534759" src="en-us_image_0000001747739624.png"></span> and select the desired region and project.</li><li id="elb_qs_0003__en-us_topic_0000001126827555_en-us_topic_0000001125381517_li59941052152319">Click <span><img id="elb_qs_0003__image134577316234759" src="en-us_image_0000001747739880.png"></span> in the upper left corner of the page and choose <strong id="elb_qs_0003__b7449690734759">Network</strong> > <strong id="elb_qs_0003__b54911937734759">Virtual Private Cloud</strong>.</li><li id="elb_qs_0003__en-us_topic_0000001126827555_en-us_topic_0000001125381517_li47160469161557">In the navigation pane on the left, choose <strong id="elb_qs_0003__b137514098234759">Access Control</strong> > <span id="elb_qs_0003__ph245105734759"><strong id="elb_qs_0003__b56210275934759">Firewalls</strong></span>.</li><li id="elb_qs_0003__en-us_topic_0000001126827555_en-us_topic_0000001125381517_li30045754154757">In the <span id="elb_qs_0003__ph10725423734759">firewall</span> list, click the name of the <span id="elb_qs_0003__ph152484050934759">firewall</span> to switch to the page showing its details.</li><li id="elb_qs_0003__en-us_topic_0000001126827555_en-us_topic_0000001125381517_li1976338154757">On the <strong id="elb_qs_0003__b193921555434759">Inbound Rules</strong> or <strong id="elb_qs_0003__b59026074534759">Outbound Rules</strong> tab page, click <strong id="elb_qs_0003__b99184665534759">Add Rule</strong> to add a rule.<ul id="elb_qs_0003__en-us_topic_0000001126827555_en-us_topic_0000001125381517_ul185172012178"><li id="elb_qs_0003__en-us_topic_0000001126827555_en-us_topic_0000001125381517_li4511820191719"><strong id="elb_qs_0003__b195627275334759">Action</strong>: Select <strong id="elb_qs_0003__b55846611334759">Allow</strong>.</li><li id="elb_qs_0003__en-us_topic_0000001126827555_en-us_topic_0000001125381517_li8626942141716"><strong id="elb_qs_0003__b21099048934759">Protocol</strong>: The protocol must be the same as the one you selected for the listener.</li><li id="elb_qs_0003__en-us_topic_0000001126827555_en-us_topic_0000001125381517_li9500202313188"><strong id="elb_qs_0003__b112394197134759">Source</strong>: Set it to the VPC CIDR block.</li><li id="elb_qs_0003__en-us_topic_0000001126827555_en-us_topic_0000001125381517_li66251610162417"><strong id="elb_qs_0003__b81206566034759">Source Port Range</strong>: Select a port range.</li><li id="elb_qs_0003__en-us_topic_0000001126827555_en-us_topic_0000001125381517_li7464162916350"><strong id="elb_qs_0003__b15276137534759">Destination</strong>: Enter a destination address allowed in this direction. The default value is <strong id="elb_qs_0003__b157683080134759">0.0.0.0/0</strong>, which indicates that traffic from all IP addresses is permitted.</li><li id="elb_qs_0003__en-us_topic_0000001126827555_en-us_topic_0000001125381517_li5915133319341"><strong id="elb_qs_0003__b135798799734759">Destination Port Range</strong>: Select a port range.</li><li id="elb_qs_0003__en-us_topic_0000001126827555_en-us_topic_0000001125381517_li75457153520">(Optional) <strong id="elb_qs_0003__b109444780334759">Description</strong>: Describe the firewall rule if necessary.</li></ul>
|
<ol id="elb_qs_0003__en-us_topic_0000001126827555_en-us_topic_0000001125381517_ol17965143881417"><li id="elb_qs_0003__en-us_topic_0000001126827555_en-us_topic_0000001125381517_li20860192818532">Log in to the management console.</li><li id="elb_qs_0003__en-us_topic_0000001126827555_en-us_topic_0000001125381517_li1486022812537">In the upper left corner of the page, click <span><img id="elb_qs_0003__image94944575534759" src="en-us_image_0000001747739624.png"></span> and select the desired region and project.</li><li id="elb_qs_0003__en-us_topic_0000001126827555_en-us_topic_0000001125381517_li59941052152319">Click <span><img id="elb_qs_0003__image134577316234759" src="en-us_image_0000001747739880.png"></span> in the upper left corner of the page and choose <strong id="elb_qs_0003__b7449690734759">Network</strong> > <strong id="elb_qs_0003__b54911937734759">Virtual Private Cloud</strong>.</li><li id="elb_qs_0003__en-us_topic_0000001126827555_en-us_topic_0000001125381517_li47160469161557">In the navigation pane on the left, choose <strong id="elb_qs_0003__b780072619371">Access Control</strong> > <span id="elb_qs_0003__ph2080402615379"><strong id="elb_qs_0003__b1180132620371">Firewalls</strong></span>.</li><li id="elb_qs_0003__en-us_topic_0000001126827555_en-us_topic_0000001125381517_li30045754154757">In the <span id="elb_qs_0003__ph1126611297377">firewall</span> list, click the name of the <span id="elb_qs_0003__ph226752911372">firewall</span> to switch to the page showing its details.</li><li id="elb_qs_0003__en-us_topic_0000001126827555_en-us_topic_0000001125381517_li1976338154757">On the <strong id="elb_qs_0003__b193921555434759">Inbound Rules</strong> or <strong id="elb_qs_0003__b59026074534759">Outbound Rules</strong> tab page, click <strong id="elb_qs_0003__b99184665534759">Add Rule</strong> to add a rule.<ul id="elb_qs_0003__en-us_topic_0000001126827555_en-us_topic_0000001125381517_ul185172012178"><li id="elb_qs_0003__en-us_topic_0000001126827555_en-us_topic_0000001125381517_li4511820191719"><strong id="elb_qs_0003__b195627275334759">Action</strong>: Select <strong id="elb_qs_0003__b55846611334759">Allow</strong>.</li><li id="elb_qs_0003__en-us_topic_0000001126827555_en-us_topic_0000001125381517_li8626942141716"><strong id="elb_qs_0003__b21099048934759">Protocol</strong>: The protocol must be the same as the one you selected for the listener.</li><li id="elb_qs_0003__en-us_topic_0000001126827555_en-us_topic_0000001125381517_li9500202313188"><strong id="elb_qs_0003__b112394197134759">Source</strong>: Set it to the VPC CIDR block.</li><li id="elb_qs_0003__en-us_topic_0000001126827555_en-us_topic_0000001125381517_li66251610162417"><strong id="elb_qs_0003__b124932411148">Source Port Range</strong>: Select a port range based on the service requirements.</li><li id="elb_qs_0003__en-us_topic_0000001126827555_en-us_topic_0000001125381517_li7464162916350"><strong id="elb_qs_0003__b15276137534759">Destination</strong>: Enter a destination address allowed in this direction. The default value is <strong id="elb_qs_0003__b157683080134759">0.0.0.0/0</strong>, which indicates that traffic from all IP addresses is permitted.</li><li id="elb_qs_0003__en-us_topic_0000001126827555_en-us_topic_0000001125381517_li5915133319341"><strong id="elb_qs_0003__b20636229101417">Destination Port Range</strong>: Select a port range based on the service requirements.</li><li id="elb_qs_0003__en-us_topic_0000001126827555_en-us_topic_0000001125381517_li75457153520">(Optional) <strong id="elb_qs_0003__b176452032103718">Description</strong>: Describe the firewall rule if necessary.</li></ul>
|
||||||
</li><li id="elb_qs_0003__en-us_topic_0000001126827555_en-us_topic_0000001125381517_li162953310168">Click <strong id="elb_qs_0003__b63113001734759">OK</strong>.</li></ol>
|
</li><li id="elb_qs_0003__en-us_topic_0000001126827555_en-us_topic_0000001125381517_li162953310168">Click <strong id="elb_qs_0003__b63113001734759">OK</strong>.</li></ol>
|
||||||
</div>
|
</div>
|
||||||
<div class="section" id="elb_qs_0003__section184861920245"><h4 class="sectiontitle">Adding a Listener</h4><p id="elb_qs_0003__en-us_topic_0166358908_p845424162316">Add a listener to the created load balancer. When you add the listener, create a backend server group, configure a health check, and add the two ECSs to the created backend server group.</p>
|
<div class="section" id="elb_qs_0003__section184861920245"><h4 class="sectiontitle">Adding a Listener</h4><p id="elb_qs_0003__en-us_topic_0166358908_p845424162316">Add a listener to the created load balancer. When you add the listener, create a backend server group, configure a health check, and add the two ECSs to the created backend server group. If a backend server is detected unhealthy, the load balancer will stop routing traffic to it until the backend server recovers.</p>
|
||||||
<div class="p" id="elb_qs_0003__en-us_topic_0166358908_p174950177514">Configure two forwarding policies to forward HTTP requests to the two ECSs, for example, requests from <strong id="elb_qs_0003__b19477121211531">www.example.com/ELB01/</strong> to ECS01, and those from <strong id="elb_qs_0003__b447818124531">www.example.com/ELB02/</strong> to ECS02.<div class="fignone" id="elb_qs_0003__en-us_topic_0166358908_fig1585611052513"><span class="figcap"><b>Figure 4 </b>Traffic forwarding</span><br><span><img class="vsd" id="elb_qs_0003__en-us_topic_0166358908_image115200401353" src="en-us_image_0000001747739860.png"></span></div>
|
<div class="p" id="elb_qs_0003__en-us_topic_0166358908_p174950177514">Configure two forwarding policies to forward HTTP requests to the two ECSs, for example, requests from <strong id="elb_qs_0003__b19477121211531">www.example.com/ELB01/</strong> to ECS01, and those from <strong id="elb_qs_0003__b447818124531">www.example.com/ELB02/</strong> to ECS02.<div class="fignone" id="elb_qs_0003__en-us_topic_0166358908_fig1585611052513"><span class="figcap"><b>Figure 4 </b>Traffic forwarding</span><br><span><img class="vsd" id="elb_qs_0003__en-us_topic_0166358908_image115200401353" src="en-us_image_0000001747739860.png"></span></div>
|
||||||
</div>
|
</div>
|
||||||
<ol id="elb_qs_0003__en-us_topic_0166358908_ol5476154122712"><li id="elb_qs_0003__en-us_topic_0166358908_li122074130268">Hover on <span><img id="elb_qs_0003__image174615155334759" src="en-us_image_0000001794660485.png"></span> in the upper left corner to display <strong id="elb_qs_0003__b99087358534759">Service List</strong> and choose <strong id="elb_qs_0003__b116053448434759">Network</strong> > <strong id="elb_qs_0003__b26692803834759">Elastic Load Balancing</strong>. </li><li id="elb_qs_0003__en-us_topic_0166358908_li44618046152949">Locate the load balancer and click its name.</li><li id="elb_qs_0003__en-us_topic_0166358908_li13174175374113">Under <strong id="elb_qs_0003__b79943675934759">Listeners</strong>, click <strong id="elb_qs_0003__b55375906534759">Add Listener</strong>.</li><li id="elb_qs_0003__en-us_topic_0166358908_li3525459183317">Configure the listener and click <strong id="elb_qs_0003__b37176564634759">Next</strong>.<ul id="elb_qs_0003__en-us_topic_0166358908_ul19799192211283"><li id="elb_qs_0003__en-us_topic_0166358908_li1680042242817"><strong id="elb_qs_0003__b26706974634759">Name</strong>: Enter a name, for example, <strong id="elb_qs_0003__b127297110634759">listener-HTTP</strong>.</li><li id="elb_qs_0003__en-us_topic_0166358908_li361710862912"><strong id="elb_qs_0003__b113489025834759">Frontend Protocol/Port</strong>: Select a protocol and enter a port for the load balancer to receive requests. For example, set it to <strong id="elb_qs_0003__b138567560534759">HTTP</strong> and <strong id="elb_qs_0003__b4682217934759">80</strong>.</li></ul>
|
<ol id="elb_qs_0003__en-us_topic_0166358908_ol5476154122712"><li id="elb_qs_0003__en-us_topic_0166358908_li122074130268">Click <span><img id="elb_qs_0003__image174615155334759" src="en-us_image_0000001794660485.png"></span> in the upper left corner to display <strong id="elb_qs_0003__b99087358534759">Service List</strong> and choose <strong id="elb_qs_0003__b116053448434759">Network</strong> > <strong id="elb_qs_0003__b26692803834759">Elastic Load Balancing</strong>. </li><li id="elb_qs_0003__en-us_topic_0166358908_li44618046152949">Locate the load balancer and click its name.</li><li id="elb_qs_0003__en-us_topic_0166358908_li13174175374113">Under <strong id="elb_qs_0003__b79943675934759">Listeners</strong>, click <strong id="elb_qs_0003__b55375906534759">Add Listener</strong>.</li><li id="elb_qs_0003__en-us_topic_0166358908_li3525459183317">Configure the listener and click <strong id="elb_qs_0003__b37176564634759">Next</strong>.<ul id="elb_qs_0003__en-us_topic_0166358908_ul19799192211283"><li id="elb_qs_0003__en-us_topic_0166358908_li1680042242817"><strong id="elb_qs_0003__b26706974634759">Name</strong>: Enter a name, for example, <strong id="elb_qs_0003__b127297110634759">listener-HTTP</strong>.</li><li id="elb_qs_0003__en-us_topic_0166358908_li361710862912"><strong id="elb_qs_0003__b113489025834759">Frontend Protocol/Port</strong>: Select a protocol and enter a port for the load balancer to receive requests. For example, set it to <strong id="elb_qs_0003__b138567560534759">HTTP</strong> and <strong id="elb_qs_0003__b4682217934759">80</strong>.</li></ul>
|
||||||
</li><li id="elb_qs_0003__en-us_topic_0166358908_li446913175196">Create a backend server group, configure a health check, and click <strong id="elb_qs_0003__b202181914558">Finish</strong>.<ul id="elb_qs_0003__en-us_topic_0166358908_ul12469417191910"><li id="elb_qs_0003__en-us_topic_0166358908_li74691170194">Backend Server Group<ul id="elb_qs_0003__en-us_topic_0166358908_ul1346941761917"><li id="elb_qs_0003__en-us_topic_0166358908_li7469161717192"><strong id="elb_qs_0003__b713017402555">Name</strong>: Enter a name, for example, <strong id="elb_qs_0003__b513054014555">server_group-ELB</strong>.</li><li id="elb_qs_0003__en-us_topic_0166358908_li94694172199"><strong id="elb_qs_0003__b157953536234759">Load Balancing Algorithm</strong>: Select an algorithm that the load balancer will use to route requests, for example, <strong id="elb_qs_0003__b25910379534759">Weighted round robin</strong>.</li></ul>
|
</li><li id="elb_qs_0003__en-us_topic_0166358908_li446913175196">Create a backend server group, configure a health check, and click <strong id="elb_qs_0003__b1542121421614">Finish</strong>.<ul id="elb_qs_0003__en-us_topic_0166358908_ul12469417191910"><li id="elb_qs_0003__en-us_topic_0166358908_li74691170194">Backend server group<ul id="elb_qs_0003__en-us_topic_0166358908_ul1346941761917"><li id="elb_qs_0003__en-us_topic_0166358908_li7469161717192"><strong id="elb_qs_0003__b164920124178">Name</strong>: Enter a name, for example, <strong id="elb_qs_0003__b2493151211711">server_group-ELB</strong>.</li><li id="elb_qs_0003__en-us_topic_0166358908_li94694172199"><strong id="elb_qs_0003__b157953536234759">Load Balancing Algorithm</strong>: Select an algorithm that the load balancer will use to route requests, for example, <strong id="elb_qs_0003__b25910379534759">Weighted round robin</strong>.</li></ul>
|
||||||
</li></ul>
|
</li></ul>
|
||||||
<ul id="elb_qs_0003__en-us_topic_0166358908_ul1646920173194"><li id="elb_qs_0003__en-us_topic_0166358908_li846910176194">Health check<ul id="elb_qs_0003__en-us_topic_0166358908_ul046931771916"><li id="elb_qs_0003__en-us_topic_0166358908_li1646931771918"><strong id="elb_qs_0003__b184517735934759">Protocol</strong>: Select a protocol for the load balancer to perform health checks on backend servers. If the load balancer uses TCP, HTTP, or HTTPS to receive requests, the health check protocol can be TCP or HTTP. Here we use HTTP as an example. Note that the protocol cannot be changed after the listener is added.</li><li id="elb_qs_0003__en-us_topic_0166358908_li104691517151910"><strong id="elb_qs_0003__b137785870834759">Domain Name</strong>: Enter a domain name that will be used for health checks, for example, www.example.com.</li><li id="elb_qs_0003__en-us_topic_0166358908_li546971711191"><strong id="elb_qs_0003__b28072109234759">Health Check Port</strong>: Enter a port for the load balancer to perform health checks on backend servers, for example, <strong id="elb_qs_0003__b195972119834759">80</strong>.<p id="elb_qs_0003__en-us_topic_0166358908_p446918172196">If you do not specify a health check port, the backend port will be used for health checks by default.</p>
|
<ul id="elb_qs_0003__en-us_topic_0166358908_ul1646920173194"><li id="elb_qs_0003__en-us_topic_0166358908_li846910176194">Health check<ul id="elb_qs_0003__en-us_topic_0166358908_ul046931771916"><li id="elb_qs_0003__en-us_topic_0166358908_li1646931771918"><strong id="elb_qs_0003__b184517735934759">Health Check Protocol</strong>: Select a protocol for the load balancer to perform health checks on backend servers. If the load balancer uses TCP, HTTP, or HTTPS to receive requests, the health check protocol can be TCP or HTTP. Here we use HTTP as an example. Note that the protocol cannot be changed after the listener is added.</li><li id="elb_qs_0003__en-us_topic_0166358908_li104691517151910"><strong id="elb_qs_0003__b137785870834759">Domain Name</strong>: Enter a domain name that will be used for health checks, for example, www.example.com.</li><li id="elb_qs_0003__en-us_topic_0166358908_li546971711191"><strong id="elb_qs_0003__b28072109234759">Health Check Port</strong>: Enter a port for the load balancer to perform health checks on backend servers, for example, <strong id="elb_qs_0003__b195972119834759">80</strong>.<p id="elb_qs_0003__en-us_topic_0166358908_p446918172196">If you do not specify a health check port, the backend port will be used for health checks by default.</p>
|
||||||
</li></ul>
|
</li></ul>
|
||||||
</li></ul>
|
</li></ul>
|
||||||
</li></ol>
|
</li></ol>
|
||||||
</div>
|
</div>
|
||||||
<div class="section" id="elb_qs_0003__section6778123018276"><h4 class="sectiontitle">Adding a Forwarding Policy</h4><ol id="elb_qs_0003__en-us_topic_0166358908_ol16279105810277"><li id="elb_qs_0003__en-us_topic_0166358908_li1279175813279">Click the name of the newly added listener and then click <strong id="elb_qs_0003__b24039750534759">Add</strong> next to <strong id="elb_qs_0003__b101705532734759">Forwarding Policies</strong>.</li><li id="elb_qs_0003__en-us_topic_0166358908_li42791058102718">Configure the forwarding policy and click <strong id="elb_qs_0003__b68801035234759">Next</strong>.<ul id="elb_qs_0003__en-us_topic_0166358908_ul4782734162215"><li id="elb_qs_0003__en-us_topic_0166358908_li197823348223"><strong id="elb_qs_0003__b48735143334759">Name</strong>: Enter a name for the forwarding policy, for example, <strong id="elb_qs_0003__b85232814234759">forwarding_policy-ELB01</strong>.</li><li id="elb_qs_0003__en-us_topic_0166358908_li2078323419221"><strong id="elb_qs_0003__b138938412">Domain Name</strong>: Enter a domain name that will be used to forward the requests, for example, www.example.com. The domain name in the request must exactly match that specified in the forwarding policy.</li><li id="elb_qs_0003__en-us_topic_0166358908_li2739202722519"><strong id="elb_qs_0003__b210210046034759">URL</strong>: You can also specify a URL to forward the requests, for example, <strong id="elb_qs_0003__b78763651634759">/ELB01/</strong>.</li><li id="elb_qs_0003__en-us_topic_0166358908_li66261226102716"><strong id="elb_qs_0003__b101237342334759">URL Matching Rule</strong>: Select a rule for matching the specified URL string with the URL in the request. Three options are available, <strong id="elb_qs_0003__b129130528034759">Exact match</strong>, <strong id="elb_qs_0003__b162287786734759">Prefix match</strong>, and <strong id="elb_qs_0003__b76956779934759">Regular expression match</strong>. <strong id="elb_qs_0003__b76681543634759">Exact match</strong> enjoys the highest priority, and <strong id="elb_qs_0003__b159773644334759">Regular expression match</strong> the lowest priority. Select <strong id="elb_qs_0003__b171209082534759">Exact match</strong> here.</li></ul>
|
<div class="section" id="elb_qs_0003__section6778123018276"><h4 class="sectiontitle">Adding a Forwarding Policy</h4><ol id="elb_qs_0003__en-us_topic_0166358908_ol16279105810277"><li id="elb_qs_0003__en-us_topic_0166358908_li1279175813279">Click the name of the newly added listener and then click <strong id="elb_qs_0003__b24039750534759">Add</strong> next to <strong id="elb_qs_0003__b101705532734759">Forwarding Policies</strong>.</li><li id="elb_qs_0003__en-us_topic_0166358908_li42791058102718">Configure the forwarding policy and click <strong id="elb_qs_0003__b68801035234759">Next</strong>.<ul id="elb_qs_0003__en-us_topic_0166358908_ul4782734162215"><li id="elb_qs_0003__en-us_topic_0166358908_li197823348223"><strong id="elb_qs_0003__b48735143334759">Name</strong>: Enter a name for the forwarding policy, for example, <strong id="elb_qs_0003__b85232814234759">forwarding_policy-ELB01</strong>.</li><li id="elb_qs_0003__en-us_topic_0166358908_li2078323419221"><strong id="elb_qs_0003__b138938412">Domain Name</strong>: Enter a domain name that will be used to forward the requests, for example, www.example.com. The domain name in the request must exactly match that specified in the forwarding policy.</li><li id="elb_qs_0003__en-us_topic_0166358908_li2739202722519"><strong id="elb_qs_0003__b210210046034759">URL</strong>: You can also specify a URL to forward the requests, for example, <strong id="elb_qs_0003__b78763651634759">/ELB01/</strong>.</li><li id="elb_qs_0003__en-us_topic_0166358908_li66261226102716"><strong id="elb_qs_0003__b101237342334759">URL Matching Rule</strong>: Select a rule for matching the specified URL string with the URL in the request. Three options are available, <strong id="elb_qs_0003__b129130528034759">Exact match</strong>, <strong id="elb_qs_0003__b162287786734759">Prefix match</strong>, and <strong id="elb_qs_0003__b76956779934759">Regular expression match</strong>. <strong id="elb_qs_0003__b76681543634759">Exact match</strong> enjoys the highest priority, and <strong id="elb_qs_0003__b159773644334759">Regular expression match</strong> the lowest priority. Select <strong id="elb_qs_0003__b171209082534759">Exact match</strong> here.</li></ul>
|
||||||
</li><li id="elb_qs_0003__en-us_topic_0166358908_li12748141114321">Create a backend server group, configure a health check, and click <strong id="elb_qs_0003__b153789581545">Finish</strong>.<ul id="elb_qs_0003__en-us_topic_0166358908_ul1274861111325"><li id="elb_qs_0003__en-us_topic_0166358908_li11748611203214">Backend Server Group<ul id="elb_qs_0003__en-us_topic_0166358908_ul17748131123211"><li id="elb_qs_0003__en-us_topic_0166358908_li15748191119321"><strong id="elb_qs_0003__b521212169514">Name</strong>: Enter a name, for example, <strong id="elb_qs_0003__b102123161553">server_group-ELB01</strong>.</li><li id="elb_qs_0003__en-us_topic_0166358908_li1374821120322"><strong id="elb_qs_0003__b212057740734759">Load Balancing Algorithm</strong>: Select an algorithm that the load balancer will use to route requests, for example, <strong id="elb_qs_0003__b154488540734759">Weighted round robin</strong>.</li></ul>
|
</li><li id="elb_qs_0003__en-us_topic_0166358908_li12748141114321">Create a backend server group and configure a health check.<ul id="elb_qs_0003__en-us_topic_0166358908_ul1274861111325"><li id="elb_qs_0003__en-us_topic_0166358908_li11748611203214">Backend server group<ul id="elb_qs_0003__en-us_topic_0166358908_ul17748131123211"><li id="elb_qs_0003__en-us_topic_0166358908_li15748191119321"><strong id="elb_qs_0003__b475018281579">Name</strong>: Enter a name, for example, <strong id="elb_qs_0003__b1375010285715">server_group-ELB01</strong>.</li><li id="elb_qs_0003__en-us_topic_0166358908_li1374821120322"><strong id="elb_qs_0003__b212057740734759">Load Balancing Algorithm</strong>: Select an algorithm that the load balancer will use to route requests, for example, <strong id="elb_qs_0003__b154488540734759">Weighted round robin</strong>.</li></ul>
|
||||||
</li></ul>
|
</li></ul>
|
||||||
<ul id="elb_qs_0003__en-us_topic_0166358908_ul1574861111327"><li id="elb_qs_0003__en-us_topic_0166358908_li374812116329">Health check<ul id="elb_qs_0003__en-us_topic_0166358908_ul16748141112321"><li id="elb_qs_0003__en-us_topic_0166358908_li1574819117322"><strong id="elb_qs_0003__b168084178034759">Protocol</strong>: Select a protocol for the load balancer to perform health checks on backend servers. If the load balancer uses TCP, HTTP, or HTTPS to receive requests, the health check protocol can be TCP or HTTP. Here we use HTTP as an example. Note that the protocol cannot be changed after the listener is added.</li><li id="elb_qs_0003__en-us_topic_0166358908_li1174891118325"><strong id="elb_qs_0003__b694212421520">Domain Name</strong>: Enter a domain name that will be used for health checks, for example, <strong id="elb_qs_0003__b394318426511">www.example.com</strong>.</li><li id="elb_qs_0003__en-us_topic_0166358908_li574820119321"><strong id="elb_qs_0003__b41986592434759">Health Check Port</strong>: Enter a port for the load balancer to perform health checks on backend servers, for example, <strong id="elb_qs_0003__b44347085434759">80</strong>.<p id="elb_qs_0003__en-us_topic_0166358908_p3748171183218">If you do not specify a health check port, the backend port will be used for health checks by default.</p>
|
<ul id="elb_qs_0003__en-us_topic_0166358908_ul1574861111327"><li id="elb_qs_0003__en-us_topic_0166358908_li374812116329">Health check<ul id="elb_qs_0003__en-us_topic_0166358908_ul16748141112321"><li id="elb_qs_0003__en-us_topic_0166358908_li1574819117322"><strong id="elb_qs_0003__b168084178034759">Health Check Protocol</strong>: Select a protocol for the load balancer to perform health checks on backend servers. If the load balancer uses TCP, HTTP, or HTTPS to receive requests, the health check protocol can be TCP or HTTP. Here we use HTTP as an example. Note that the protocol cannot be changed after the listener is added.</li><li id="elb_qs_0003__en-us_topic_0166358908_li1174891118325"><strong id="elb_qs_0003__b694212421520">Domain Name</strong>: Enter a domain name that will be used for health checks, for example, <strong id="elb_qs_0003__b394318426511">www.example.com</strong>.</li><li id="elb_qs_0003__en-us_topic_0166358908_li574820119321"><strong id="elb_qs_0003__b41986592434759">Health Check Port</strong>: Enter a port for the load balancer to perform health checks on backend servers, for example, <strong id="elb_qs_0003__b44347085434759">80</strong>.<p id="elb_qs_0003__en-us_topic_0166358908_p3748171183218">If you do not specify a health check port, the backend port will be used for health checks by default.</p>
|
||||||
</li></ul>
|
</li></ul>
|
||||||
</li></ul>
|
</li></ul>
|
||||||
</li><li id="elb_qs_0003__en-us_topic_0166358908_li614204520397">Select the newly added forwarding policy. On the <strong id="elb_qs_0003__b40823188634759">Backend Server Groups</strong> tab page on the right, click <strong id="elb_qs_0003__b123760118934759">Add</strong>.</li><li id="elb_qs_0003__en-us_topic_0166358908_li19903154544217">Select the server you want to add, set the backend port, and click <strong id="elb_qs_0003__b126538263234759">Finish</strong>.<ul id="elb_qs_0003__en-us_topic_0166358908_ul19482182214415"><li id="elb_qs_0003__en-us_topic_0166358908_li2048352284418">Backend server: ECS01</li><li id="elb_qs_0003__en-us_topic_0166358908_li6483922104411">Backend port: Set it to <strong id="elb_qs_0003__b178090125634759">80</strong>. Backend servers will use this port to communicate with the load balancer.</li></ul>
|
</li><li id="elb_qs_0003__en-us_topic_0166358908_li614204520397">Select the newly added forwarding policy. On the <strong id="elb_qs_0003__b40823188634759">Backend Server Groups</strong> tab page on the right, click <strong id="elb_qs_0003__b123760118934759">Add</strong>.</li><li id="elb_qs_0003__en-us_topic_0166358908_li19903154544217">Select the server you want to add, set the backend port, and click <strong id="elb_qs_0003__b126538263234759">Finish</strong>.<ul id="elb_qs_0003__en-us_topic_0166358908_ul19482182214415"><li id="elb_qs_0003__en-us_topic_0166358908_li2048352284418">Backend server: ECS01</li><li id="elb_qs_0003__en-us_topic_0166358908_li6483922104411">Backend port: Set it to <strong id="elb_qs_0003__b178090125634759">80</strong>. Backend servers will use this port to communicate with the load balancer.</li></ul>
|
||||||
@ -201,10 +201,10 @@ systemctl enable nginx</pre>
|
|||||||
</div>
|
</div>
|
||||||
</li><li id="elb_qs_0003__en-us_topic_0166358908_li1677863072715">On the CLI of your PC, run the following command to check whether the domain name is mapped to the load balancer EIP:<p id="elb_qs_0003__en-us_topic_0166358908_p141804481111"><a name="elb_qs_0003__en-us_topic_0166358908_li1677863072715"></a><a name="en-us_topic_0166358908_li1677863072715"></a><strong id="elb_qs_0003__en-us_topic_0166358908_b099542951110">ping www.example.com</strong></p>
|
</li><li id="elb_qs_0003__en-us_topic_0166358908_li1677863072715">On the CLI of your PC, run the following command to check whether the domain name is mapped to the load balancer EIP:<p id="elb_qs_0003__en-us_topic_0166358908_p141804481111"><a name="elb_qs_0003__en-us_topic_0166358908_li1677863072715"></a><a name="en-us_topic_0166358908_li1677863072715"></a><strong id="elb_qs_0003__en-us_topic_0166358908_b099542951110">ping www.example.com</strong></p>
|
||||||
<p id="elb_qs_0003__en-us_topic_0166358908_p081752681216">If data packets are returned, the domain name has been mapped to the load balancer EIP.</p>
|
<p id="elb_qs_0003__en-us_topic_0166358908_p081752681216">If data packets are returned, the domain name has been mapped to the load balancer EIP.</p>
|
||||||
</li><li id="elb_qs_0003__en-us_topic_0166358908_li4888169202412">Use your browser to access <strong id="elb_qs_0003__b3277132714714">http://www.example.com/ELB01/</strong>. If the following page is displayed, the load balancer has routed the request to ECS01.<div class="fignone" id="elb_qs_0003__en-us_topic_0166358908_fig174313116258"><span class="figcap"><b>Figure 6 </b>Accessing ECS01</span><br><span><img id="elb_qs_0003__en-us_topic_0166358908_image1262314345916" src="en-us_image_0000001794819797.png"></span></div>
|
</li><li id="elb_qs_0003__en-us_topic_0166358908_li4888169202412">Use your browser to access <strong id="elb_qs_0003__b1713307811">http://www.example.com/ELB01/</strong>. If the following page is displayed, the load balancer has routed the request to ECS01.<div class="fignone" id="elb_qs_0003__en-us_topic_0166358908_fig174313116258"><span class="figcap"><b>Figure 6 </b>Accessing ECS01</span><br><span><img id="elb_qs_0003__en-us_topic_0166358908_image1262314345916" src="en-us_image_0000001794819797.png"></span></div>
|
||||||
<div class="note" id="elb_qs_0003__en-us_topic_0166358908_note7365102853611"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="elb_qs_0003__en-us_topic_0166358908_p1687510552309"><strong id="elb_qs_0003__b18472006734759">ELB01/</strong> indicates that the default directory named <strong id="elb_qs_0003__b46476352434759">ECS01</strong> is accessed, while <strong id="elb_qs_0003__b160378015834759">ELB01</strong> indicates the file name. Therefore, the slash (/) following <strong id="elb_qs_0003__b49106551034759">ELB01</strong> must be retained.</p>
|
<div class="note" id="elb_qs_0003__en-us_topic_0166358908_note7365102853611"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="elb_qs_0003__en-us_topic_0166358908_p1687510552309"><strong id="elb_qs_0003__b18472006734759">ELB01/</strong> indicates that the default directory named <strong id="elb_qs_0003__b46476352434759">ECS01</strong> is accessed, while <strong id="elb_qs_0003__b160378015834759">ELB01</strong> indicates the file name. Therefore, the slash (/) following <strong id="elb_qs_0003__b49106551034759">ELB01</strong> must be retained.</p>
|
||||||
</div></div>
|
</div></div>
|
||||||
</li><li id="elb_qs_0003__en-us_topic_0166358908_li1497010584220">Use your browser to access <strong id="elb_qs_0003__b750716571719">http://www.example.com/ELB02/</strong>. If the following page is displayed, the load balancer has routed the request to ECS02.<div class="fignone" id="elb_qs_0003__en-us_topic_0166358908_fig897020534220"><span class="figcap"><b>Figure 7 </b>Accessing ECS02</span><br><span><img id="elb_qs_0003__en-us_topic_0166358908_image139479102108" src="en-us_image_0000001794660721.png"></span></div>
|
</li><li id="elb_qs_0003__en-us_topic_0166358908_li1497010584220">Use your browser to access <strong id="elb_qs_0003__b1447320481081">http://www.example.com/ELB02/</strong>. If the following page is displayed, the load balancer has routed the request to ECS02.<div class="fignone" id="elb_qs_0003__en-us_topic_0166358908_fig897020534220"><span class="figcap"><b>Figure 7 </b>Accessing ECS02</span><br><span><img id="elb_qs_0003__en-us_topic_0166358908_image139479102108" src="en-us_image_0000001794660721.png"></span></div>
|
||||||
</li></ol>
|
</li></ol>
|
||||||
</div>
|
</div>
|
||||||
</div>
|
</div>
|
||||||
|
@ -5,24 +5,24 @@
|
|||||||
</div>
|
</div>
|
||||||
<div class="section" id="elb_ug_bq_0000__section1163718452455"><h4 class="sectiontitle">Adding a Tag to a Load Balancer</h4><p id="elb_ug_bq_0000__p16505195164615">You can add a tag to a load balancer in the following method:</p>
|
<div class="section" id="elb_ug_bq_0000__section1163718452455"><h4 class="sectiontitle">Adding a Tag to a Load Balancer</h4><p id="elb_ug_bq_0000__p16505195164615">You can add a tag to a load balancer in the following method:</p>
|
||||||
<ul id="elb_ug_bq_0000__ul28401728175019"><li id="elb_ug_bq_0000__li9839628155019">Add a tag when you create a load balancer.<p id="elb_ug_bq_0000__p0711112119289"><a name="elb_ug_bq_0000__li9839628155019"></a><a name="li9839628155019"></a>For detailed operations, see <a href="elb_lb_000006.html">Creating a Dedicated Load Balancer</a> and <a href="en-us_topic_0015479967.html">Creating a Shared Load Balancer</a>.</p>
|
<ul id="elb_ug_bq_0000__ul28401728175019"><li id="elb_ug_bq_0000__li9839628155019">Add a tag when you create a load balancer.<p id="elb_ug_bq_0000__p0711112119289"><a name="elb_ug_bq_0000__li9839628155019"></a><a name="li9839628155019"></a>For detailed operations, see <a href="elb_lb_000006.html">Creating a Dedicated Load Balancer</a> and <a href="en-us_topic_0015479967.html">Creating a Shared Load Balancer</a>.</p>
|
||||||
</li><li id="elb_ug_bq_0000__li583918282505">Add a tag to an existing load balancer.<ol id="elb_ug_bq_0000__ol11229133665417"><li id="elb_ug_bq_0000__li677391520332">Log in to the management console.</li><li id="elb_ug_bq_0000__li675519100420">In the upper left corner of the page, click <span><img id="elb_ug_bq_0000__image35565756623028" src="en-us_image_0000001747739624.png"></span> and select the desired region and project.</li><li id="elb_ug_bq_0000__li83736197297">Hover on <span><img id="elb_ug_bq_0000__image178568419323028" src="en-us_image_0000001794660485.png"></span> in the upper left corner to display <strong id="elb_ug_bq_0000__b62740478023028">Service List</strong> and choose <strong id="elb_ug_bq_0000__b173622365723028">Network</strong> > <strong id="elb_ug_bq_0000__b145758779423028">Elastic Load Balancing</strong>.</li><li id="elb_ug_bq_0000__li1222911365545">Locate the load balancer and click its name.</li><li id="elb_ug_bq_0000__li7981103114568">Under <strong id="elb_ug_bq_0000__b84235270612121">Tags</strong>, click <strong id="elb_ug_bq_0000__b8423527061224">Add Tag</strong>.</li><li id="elb_ug_bq_0000__li206491583010">In the <strong id="elb_ug_bq_0000__b2115587242165643">Add Tag</strong> dialog box, enter a tag key and value and click <strong id="elb_ug_bq_0000__b611835798165643">OK</strong>.<div class="note" id="elb_ug_bq_0000__note1649510311200"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="elb_ug_bq_0000__ul1459215541328"><li id="elb_ug_bq_0000__li3592854126">A maximum of 20 tags can be added to a load balancer.</li><li id="elb_ug_bq_0000__li1659275414213">Each tag is a key-value pair, and the tag key is unique.</li></ul>
|
</li><li id="elb_ug_bq_0000__li583918282505">Add a tag to an existing load balancer.<ol id="elb_ug_bq_0000__ol11229133665417"><li id="elb_ug_bq_0000__li677391520332">Log in to the management console.</li><li id="elb_ug_bq_0000__li675519100420">In the upper left corner of the page, click <span><img id="elb_ug_bq_0000__image35565756623028" src="en-us_image_0000001747739624.png"></span> and select the desired region and project.</li><li id="elb_ug_bq_0000__li83736197297">Click <span><img id="elb_ug_bq_0000__image178568419323028" src="en-us_image_0000001794660485.png"></span> in the upper left corner to display <strong id="elb_ug_bq_0000__b62740478023028">Service List</strong> and choose <strong id="elb_ug_bq_0000__b173622365723028">Network</strong> > <strong id="elb_ug_bq_0000__b145758779423028">Elastic Load Balancing</strong>.</li><li id="elb_ug_bq_0000__li1222911365545">Locate the load balancer and click its name.</li><li id="elb_ug_bq_0000__li7981103114568">Under <strong id="elb_ug_bq_0000__b84235270612121">Tags</strong>, click <strong id="elb_ug_bq_0000__b8423527061224">Add Tag</strong>.</li><li id="elb_ug_bq_0000__li206491583010">In the <strong id="elb_ug_bq_0000__b2115587242165643">Add Tag</strong> dialog box, enter a tag key and value and click <strong id="elb_ug_bq_0000__b611835798165643">OK</strong>.<div class="note" id="elb_ug_bq_0000__note1649510311200"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="elb_ug_bq_0000__ul1459215541328"><li id="elb_ug_bq_0000__li3592854126">A maximum of 20 tags can be added to a load balancer.</li><li id="elb_ug_bq_0000__li1659275414213">Each tag is a key-value pair, and the tag key is unique.</li></ul>
|
||||||
</div></div>
|
</div></div>
|
||||||
</li></ol>
|
</li></ol>
|
||||||
</li></ul>
|
</li></ul>
|
||||||
</div>
|
</div>
|
||||||
<div class="section" id="elb_ug_bq_0000__section175469211735"><h4 class="sectiontitle">Adding a Tag to a Listener</h4><p id="elb_ug_bq_0000__p078516156810">You can add tags when you add listeners.</p>
|
<div class="section" id="elb_ug_bq_0000__section175469211735"><h4 class="sectiontitle">Adding a Tag to a Listener</h4><p id="elb_ug_bq_0000__p078516156810">You can add tags when you add listeners.</p>
|
||||||
<p id="elb_ug_bq_0000__p1868913231548">To add a tag to an existing listener, perform the following steps:</p>
|
<p id="elb_ug_bq_0000__p1868913231548">To add a tag to an existing listener, perform the following steps:</p>
|
||||||
<ol id="elb_ug_bq_0000__ol18792714101"><li id="elb_ug_bq_0000__li115212495820">Log in to the management console.</li><li id="elb_ug_bq_0000__li15529419589">In the upper left corner of the page, click <span><img id="elb_ug_bq_0000__image129670569320" src="en-us_image_0000001747739624.png"></span> and select the desired region and project.</li><li id="elb_ug_bq_0000__li17301740102218">Hover on <span><img id="elb_ug_bq_0000__image185212624323028" src="en-us_image_0000001794660485.png"></span> in the upper left corner to display <strong id="elb_ug_bq_0000__b80065074223028">Service List</strong> and choose <strong id="elb_ug_bq_0000__b64618483823028">Network</strong> > <strong id="elb_ug_bq_0000__b139029583023028">Elastic Load Balancing</strong>.</li><li id="elb_ug_bq_0000__li15101427161014">Locate the load balancer and click its name.</li><li id="elb_ug_bq_0000__li8487359151011">Click <strong id="elb_ug_bq_0000__b842352706163816">Listeners</strong>, locate the listener, and click its name.</li><li id="elb_ug_bq_0000__li8155171491312">Under <strong id="elb_ug_bq_0000__b842352706165356">Tags</strong>, click <strong id="elb_ug_bq_0000__b842352706165539">Add Tag</strong>.</li><li id="elb_ug_bq_0000__li16111627151011">In the <strong id="elb_ug_bq_0000__b60865473">Add Tag</strong> dialog box, enter a tag key and value and click <strong id="elb_ug_bq_0000__b1610769486">OK</strong>.<div class="note" id="elb_ug_bq_0000__note12326124181515"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="elb_ug_bq_0000__ul332819417158"><li id="elb_ug_bq_0000__li932820411151">A maximum of 20 tags can be added to a listener.</li><li id="elb_ug_bq_0000__li132915415152">Each tag is a key-value pair, and the tag key is unique.</li></ul>
|
<ol id="elb_ug_bq_0000__ol18792714101"><li id="elb_ug_bq_0000__li115212495820">Log in to the management console.</li><li id="elb_ug_bq_0000__li15529419589">In the upper left corner of the page, click <span><img id="elb_ug_bq_0000__image129670569320" src="en-us_image_0000001747739624.png"></span> and select the desired region and project.</li><li id="elb_ug_bq_0000__li17301740102218">Click <span><img id="elb_ug_bq_0000__image185212624323028" src="en-us_image_0000001794660485.png"></span> in the upper left corner to display <strong id="elb_ug_bq_0000__b80065074223028">Service List</strong> and choose <strong id="elb_ug_bq_0000__b64618483823028">Network</strong> > <strong id="elb_ug_bq_0000__b139029583023028">Elastic Load Balancing</strong>.</li><li id="elb_ug_bq_0000__li15101427161014">Locate the load balancer and click its name.</li><li id="elb_ug_bq_0000__li8487359151011">Click <strong id="elb_ug_bq_0000__b842352706163816">Listeners</strong>, locate the listener, and click its name.</li><li id="elb_ug_bq_0000__li8155171491312">Under <strong id="elb_ug_bq_0000__b842352706165356">Tags</strong>, click <strong id="elb_ug_bq_0000__b842352706165539">Add Tag</strong>.</li><li id="elb_ug_bq_0000__li16111627151011">In the <strong id="elb_ug_bq_0000__b1379376943">Add Tag</strong> dialog box, enter a tag key and value and click <strong id="elb_ug_bq_0000__b562238371">OK</strong>.<div class="note" id="elb_ug_bq_0000__note12326124181515"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="elb_ug_bq_0000__ul332819417158"><li id="elb_ug_bq_0000__li932820411151">A maximum of 20 tags can be added to a listener.</li><li id="elb_ug_bq_0000__li132915415152">Each tag is a key-value pair, and the tag key is unique.</li></ul>
|
||||||
</div></div>
|
</div></div>
|
||||||
</li></ol>
|
</li></ol>
|
||||||
<p id="elb_ug_bq_0000__p38741451272"></p>
|
<p id="elb_ug_bq_0000__p38741451272"></p>
|
||||||
</div>
|
</div>
|
||||||
<div class="section" id="elb_ug_bq_0000__section1432939104616"><h4 class="sectiontitle">Modifying a Tag</h4><ol id="elb_ug_bq_0000__ol1698016422035"><li id="elb_ug_bq_0000__li1780018151587">Log in to the management console.</li><li id="elb_ug_bq_0000__li480015155581">In the upper left corner of the page, click <span><img id="elb_ug_bq_0000__image200716150023028" src="en-us_image_0000001747739624.png"></span> and select the desired region and project.</li><li id="elb_ug_bq_0000__li3915642514">Hover on <span><img id="elb_ug_bq_0000__image161362657223028" src="en-us_image_0000001794660485.png"></span> in the upper left corner to display <strong id="elb_ug_bq_0000__b59554934223028">Service List</strong> and choose <strong id="elb_ug_bq_0000__b186906152123028">Network</strong> > <strong id="elb_ug_bq_0000__b167678064123028">Elastic Load Balancing</strong>.</li><li id="elb_ug_bq_0000__li69321144732">Locate the load balancer and click its name.</li><li id="elb_ug_bq_0000__li39326442032">Click <strong id="elb_ug_bq_0000__b14429401261262">Tags</strong>, select the tag to be edited, and click <strong id="elb_ug_bq_0000__b8423527061276">Edit</strong> in the <strong id="elb_ug_bq_0000__b8423527061273">Operation</strong> column. In the <strong id="elb_ug_bq_0000__b8730353761262">Edit Tag</strong> dialog box, change the tag value.<div class="note" id="elb_ug_bq_0000__note1042524418619"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="elb_ug_bq_0000__p34251844869">The tag key cannot be changed.</p>
|
<div class="section" id="elb_ug_bq_0000__section1432939104616"><h4 class="sectiontitle">Modifying a Tag</h4><ol id="elb_ug_bq_0000__ol1698016422035"><li id="elb_ug_bq_0000__li1780018151587">Log in to the management console.</li><li id="elb_ug_bq_0000__li480015155581">In the upper left corner of the page, click <span><img id="elb_ug_bq_0000__image200716150023028" src="en-us_image_0000001747739624.png"></span> and select the desired region and project.</li><li id="elb_ug_bq_0000__li3915642514">Click <span><img id="elb_ug_bq_0000__image161362657223028" src="en-us_image_0000001794660485.png"></span> in the upper left corner to display <strong id="elb_ug_bq_0000__b59554934223028">Service List</strong> and choose <strong id="elb_ug_bq_0000__b186906152123028">Network</strong> > <strong id="elb_ug_bq_0000__b167678064123028">Elastic Load Balancing</strong>.</li><li id="elb_ug_bq_0000__li69321144732">Locate the load balancer and click its name.</li><li id="elb_ug_bq_0000__li39326442032">Click <strong id="elb_ug_bq_0000__b14429401261262">Tags</strong>, select the tag to be edited, and click <strong id="elb_ug_bq_0000__b8423527061276">Edit</strong> in the <strong id="elb_ug_bq_0000__b8423527061273">Operation</strong> column. In the <strong id="elb_ug_bq_0000__b8730353761262">Edit Tag</strong> dialog box, change the tag value.<div class="note" id="elb_ug_bq_0000__note1042524418619"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="elb_ug_bq_0000__p34251844869">The tag key cannot be changed.</p>
|
||||||
</div></div>
|
</div></div>
|
||||||
</li><li id="elb_ug_bq_0000__li81253361963">Click <strong id="elb_ug_bq_0000__b842352706105230">OK</strong>.</li></ol>
|
</li><li id="elb_ug_bq_0000__li81253361963">Click <strong id="elb_ug_bq_0000__b842352706105230">OK</strong>.</li></ol>
|
||||||
<p id="elb_ug_bq_0000__p167794245223">The operations for modifying a listener tag are not detailed here. Refer to the operations of modifying a load balancer tag.</p>
|
<p id="elb_ug_bq_0000__p167794245223">The operations for modifying a listener tag are not detailed here. Refer to the operations of modifying a load balancer tag.</p>
|
||||||
</div>
|
</div>
|
||||||
<div class="section" id="elb_ug_bq_0000__section1864818172465"><h4 class="sectiontitle">Deleting a Tag</h4><ol id="elb_ug_bq_0000__ol14211132811713"><li id="elb_ug_bq_0000__li5274142820589">Log in to the management console.</li><li id="elb_ug_bq_0000__li72741528155818">In the upper left corner of the page, click <span><img id="elb_ug_bq_0000__image80996007723028" src="en-us_image_0000001747739624.png"></span> and select the desired region and project.</li><li id="elb_ug_bq_0000__li1168141913315">Hover on <span><img id="elb_ug_bq_0000__image78427240023028" src="en-us_image_0000001794660485.png"></span> in the upper left corner to display <strong id="elb_ug_bq_0000__b4948487623028">Service List</strong> and choose <strong id="elb_ug_bq_0000__b5594039123028">Network</strong> > <strong id="elb_ug_bq_0000__b47076291323028">Elastic Load Balancing</strong>.</li><li id="elb_ug_bq_0000__li1521392816713">Locate the load balancer and click its name.</li><li id="elb_ug_bq_0000__li182134280714">Click <strong id="elb_ug_bq_0000__b164336334112833">Tags</strong>, select the tag to be deleted, and click <strong id="elb_ug_bq_0000__b99785180512833">Delete</strong> in the <strong id="elb_ug_bq_0000__b30597287512833">Operation</strong> column.</li><li id="elb_ug_bq_0000__li1495110710912">In the displayed dialog box, click <strong id="elb_ug_bq_0000__b84235270612924">Yes</strong>.</li></ol>
|
<div class="section" id="elb_ug_bq_0000__section1864818172465"><h4 class="sectiontitle">Deleting a Tag</h4><ol id="elb_ug_bq_0000__ol14211132811713"><li id="elb_ug_bq_0000__li5274142820589">Log in to the management console.</li><li id="elb_ug_bq_0000__li72741528155818">In the upper left corner of the page, click <span><img id="elb_ug_bq_0000__image80996007723028" src="en-us_image_0000001747739624.png"></span> and select the desired region and project.</li><li id="elb_ug_bq_0000__li1168141913315">Click <span><img id="elb_ug_bq_0000__image78427240023028" src="en-us_image_0000001794660485.png"></span> in the upper left corner to display <strong id="elb_ug_bq_0000__b4948487623028">Service List</strong> and choose <strong id="elb_ug_bq_0000__b5594039123028">Network</strong> > <strong id="elb_ug_bq_0000__b47076291323028">Elastic Load Balancing</strong>.</li><li id="elb_ug_bq_0000__li1521392816713">Locate the load balancer and click its name.</li><li id="elb_ug_bq_0000__li182134280714">Click <strong id="elb_ug_bq_0000__b164336334112833">Tags</strong>, select the tag to be deleted, and click <strong id="elb_ug_bq_0000__b99785180512833">Delete</strong> in the <strong id="elb_ug_bq_0000__b30597287512833">Operation</strong> column.</li><li id="elb_ug_bq_0000__li1495110710912">In the displayed dialog box, click <strong id="elb_ug_bq_0000__b84235270612924">Yes</strong>.</li></ol>
|
||||||
<p id="elb_ug_bq_0000__p836323472418">The operations for deleting a listener tag are not detailed here. Refer to the operations of deleting a load balancer tag.</p>
|
<p id="elb_ug_bq_0000__p836323472418">The operations for deleting a listener tag are not detailed here. Refer to the operations of deleting a load balancer tag.</p>
|
||||||
</div>
|
</div>
|
||||||
</div>
|
</div>
|
||||||
|
17
docs/elb/umn/elb_ug_fw_0000.html
Normal file
17
docs/elb/umn/elb_ug_fw_0000.html
Normal file
@ -0,0 +1,17 @@
|
|||||||
|
<a name="elb_ug_fw_0000"></a><a name="elb_ug_fw_0000"></a>
|
||||||
|
|
||||||
|
|
||||||
|
<h1 class="topictitle1">Access Control</h1>
|
||||||
|
|
||||||
|
<div id="body0000001891467489"><p id="elb_ug_fw_0000__p8060118"></p>
|
||||||
|
</div>
|
||||||
|
|
||||||
|
<div>
|
||||||
|
<ul class="ullinks">
|
||||||
|
<li class="ulchildlink"><strong><a href="elb_03_0003.html">Access Control</a></strong><br>
|
||||||
|
</li>
|
||||||
|
<li class="ulchildlink"><strong><a href="elb_ug_ip_0001.html">Managing IP Address Groups</a></strong><br>
|
||||||
|
</li>
|
||||||
|
</ul>
|
||||||
|
</div>
|
||||||
|
|
@ -2,7 +2,7 @@
|
|||||||
|
|
||||||
<h1 class="topictitle1">Preparations for Creating a Load Balancer</h1>
|
<h1 class="topictitle1">Preparations for Creating a Load Balancer</h1>
|
||||||
<div id="body1555913901701"><p id="elb_ug_fz_0004__p724713239412">Before creating a load balancer, you must plan its region, network, protocol, and backend servers.</p>
|
<div id="body1555913901701"><p id="elb_ug_fz_0004__p724713239412">Before creating a load balancer, you must plan its region, network, protocol, and backend servers.</p>
|
||||||
<div class="section" id="elb_ug_fz_0004__section12884538197"><h4 class="sectiontitle">Region</h4><div class="p" id="elb_ug_fz_0004__p1730711354418">When you select a region, note the following:<ul id="elb_ug_fz_0004__ul122945544419"><li id="elb_ug_fz_0004__li19327429145512">The region must be close to your users to reduce network latency and improve the download speed.</li><li id="elb_ug_fz_0004__li7475741155511"><span id="elb_ug_fz_0004__ph1428172813214">Shared</span> load balancers cannot distribute traffic across regions. When creating a shared load balancer, select the same region as the backend servers.</li><li id="elb_ug_fz_0004__li15748513175618">Dedicated load balancers support adding backend servers across VPCs using the IP as a backend function. For details, see <a href="elb_ug_hd_0005.html">Configuring Hybrid Load Balancing</a>.</li></ul>
|
<div class="section" id="elb_ug_fz_0004__section12884538197"><h4 class="sectiontitle">Region</h4><div class="p" id="elb_ug_fz_0004__p1730711354418">When you select a region, note the following:<ul id="elb_ug_fz_0004__ul122945544419"><li id="elb_ug_fz_0004__li19327429145512">The region must be close to your users to reduce network latency and improve the download speed.</li><li id="elb_ug_fz_0004__li7475741155511"><span id="elb_ug_fz_0004__ph1428172813214">Shared</span> load balancers cannot distribute traffic across regions. When creating a shared load balancer, select the same region as the backend servers.</li><li id="elb_ug_fz_0004__li15748513175618">Dedicated load balancers support adding backend servers across VPCs using the IP as a backend function. For details, see <a href="elb_ug_hd3_0004_01.html">Overview</a>.</li></ul>
|
||||||
</div>
|
</div>
|
||||||
</div>
|
</div>
|
||||||
<div class="section" id="elb_ug_fz_0004__section818284043213"><h4 class="sectiontitle">AZ</h4><p id="elb_ug_fz_0004__p8289152233211"><span id="elb_ug_fz_0004__ph15219124320582">Dedicated load balancers</span> can be deployed across AZs. If you select multiple AZs, a load balancer is created in each selected AZ.</p>
|
<div class="section" id="elb_ug_fz_0004__section818284043213"><h4 class="sectiontitle">AZ</h4><p id="elb_ug_fz_0004__p8289152233211"><span id="elb_ug_fz_0004__ph15219124320582">Dedicated load balancers</span> can be deployed across AZs. If you select multiple AZs, a load balancer is created in each selected AZ.</p>
|
||||||
|
@ -9,7 +9,7 @@
|
|||||||
<div class="section" id="elb_ug_fz_0008__section131941342381"><h4 class="sectiontitle">Prerequisites</h4><p id="elb_ug_fz_0008__p4144101553416">Delete the resources configured for the load balancer in the following sequence:</p>
|
<div class="section" id="elb_ug_fz_0008__section131941342381"><h4 class="sectiontitle">Prerequisites</h4><p id="elb_ug_fz_0008__p4144101553416">Delete the resources configured for the load balancer in the following sequence:</p>
|
||||||
<ol id="elb_ug_fz_0008__ol157731724204317"><li id="elb_ug_fz_0008__li077312247434">Delete all the forwarding policies added to HTTP and HTTPS listeners of the load balancer.</li><li id="elb_ug_fz_0008__li13773112484314">Delete the redirect created for each HTTP listener of the load balancer.</li><li id="elb_ug_fz_0008__li777432411438">Remove all the backend servers from the backend server groups associated with each listener of the load balancer.</li><li id="elb_ug_fz_0008__li777432414312">Delete all the listeners added to the load balancer.</li><li id="elb_ug_fz_0008__li117741524104319">Delete all backend server groups associated with each listener of the load balancer.</li></ol>
|
<ol id="elb_ug_fz_0008__ol157731724204317"><li id="elb_ug_fz_0008__li077312247434">Delete all the forwarding policies added to HTTP and HTTPS listeners of the load balancer.</li><li id="elb_ug_fz_0008__li13773112484314">Delete the redirect created for each HTTP listener of the load balancer.</li><li id="elb_ug_fz_0008__li777432411438">Remove all the backend servers from the backend server groups associated with each listener of the load balancer.</li><li id="elb_ug_fz_0008__li777432414312">Delete all the listeners added to the load balancer.</li><li id="elb_ug_fz_0008__li117741524104319">Delete all backend server groups associated with each listener of the load balancer.</li></ol>
|
||||||
</div>
|
</div>
|
||||||
<div class="section" id="elb_ug_fz_0008__section13384917815"><h4 class="sectiontitle">Deleting a Load Balancer</h4><ol id="elb_ug_fz_0008__ol1889111542441"><li id="elb_ug_fz_0008__li677391520332">Log in to the management console.</li><li id="elb_ug_fz_0008__li675519100420">In the upper left corner of the page, click <span><img id="elb_ug_fz_0008__en-us_topic_0240829509_image1542118117117" src="en-us_image_0000001747739624.png"></span> and select the desired region and project.</li><li id="elb_ug_fz_0008__li78811227131312">Hover on <span><img id="elb_ug_fz_0008__en-us_topic_0167652100_image762510132322" src="en-us_image_0000001794660485.png"></span> in the upper left corner to display <strong id="elb_ug_fz_0008__en-us_topic_0167652100_b9121102522212">Service List</strong> and choose <strong id="elb_ug_fz_0008__en-us_topic_0167652100_b61222025142217">Network</strong> > <strong id="elb_ug_fz_0008__en-us_topic_0167652100_b4124425142210">Elastic Load Balancing</strong>. </li><li id="elb_ug_fz_0008__li786163214298">Locate the load balancer and click <strong id="elb_ug_fz_0008__b176641686335">Delete</strong> in the <strong id="elb_ug_fz_0008__b8608101218338">Operation</strong> column.</li><li id="elb_ug_fz_0008__li649416466551">Click <strong id="elb_ug_fz_0008__b16243731133212">Yes</strong>.</li></ol>
|
<div class="section" id="elb_ug_fz_0008__section13384917815"><h4 class="sectiontitle">Deleting a Load Balancer</h4><ol id="elb_ug_fz_0008__ol1889111542441"><li id="elb_ug_fz_0008__li677391520332">Log in to the management console.</li><li id="elb_ug_fz_0008__li675519100420">In the upper left corner of the page, click <span><img id="elb_ug_fz_0008__image139184085824" src="en-us_image_0000001747739624.png"></span> and select the desired region and project.</li><li id="elb_ug_fz_0008__li78811227131312">Click <span><img id="elb_ug_fz_0008__image16538406718228" src="en-us_image_0000001794660485.png"></span> in the upper left corner to display <strong id="elb_ug_fz_0008__b6507474498228">Service List</strong> and choose <strong id="elb_ug_fz_0008__b6458751758228">Network</strong> > <strong id="elb_ug_fz_0008__b4443361328228">Elastic Load Balancing</strong>.</li><li id="elb_ug_fz_0008__li1661713210191">Locate the load balancer and choose <strong id="elb_ug_fz_0008__b125383573520">More</strong> > <strong id="elb_ug_fz_0008__b962054612410">Delete</strong> in the <strong id="elb_ug_fz_0008__b1362184610414">Operation</strong> column.</li><li id="elb_ug_fz_0008__li1477614269478">In the displayed dialog box, enter <strong id="elb_ug_fz_0008__b12396135414335">DELETE</strong>.</li><li id="elb_ug_fz_0008__li649416466551">Click <strong id="elb_ug_fz_0008__b16243731133212">Yes</strong>.</li></ol>
|
||||||
</div>
|
</div>
|
||||||
</div>
|
</div>
|
||||||
<div>
|
<div>
|
||||||
|
@ -3,7 +3,7 @@
|
|||||||
<h1 class="topictitle1">Exporting the Load Balancer List</h1>
|
<h1 class="topictitle1">Exporting the Load Balancer List</h1>
|
||||||
<div id="body0000001149193504"><div class="section" id="elb_ug_fz_0011__section20538244111217"><h4 class="sectiontitle">Scenarios</h4><p id="elb_ug_fz_0011__p1668911345208">You can export the load balancer list for backup.</p>
|
<div id="body0000001149193504"><div class="section" id="elb_ug_fz_0011__section20538244111217"><h4 class="sectiontitle">Scenarios</h4><p id="elb_ug_fz_0011__p1668911345208">You can export the load balancer list for backup.</p>
|
||||||
</div>
|
</div>
|
||||||
<div class="section" id="elb_ug_fz_0011__section19169366120"><h4 class="sectiontitle">Procedure</h4><ol id="elb_ug_fz_0011__en-us_topic_0093321970_ol18971723131315"><li id="elb_ug_fz_0011__li104062575369">Log in to the management console.</li><li id="elb_ug_fz_0011__li640635753619">In the upper left corner of the page, click <span><img id="elb_ug_fz_0011__en-us_topic_0240829509_image1542118117117" src="en-us_image_0000001747739624.png"></span> and select the desired region and project.</li><li id="elb_ug_fz_0011__li17301740102218">Hover on <span><img id="elb_ug_fz_0011__en-us_topic_0167652100_image762510132322" src="en-us_image_0000001794660485.png"></span> in the upper left corner to display <strong id="elb_ug_fz_0011__en-us_topic_0167652100_b9121102522212">Service List</strong> and choose <strong id="elb_ug_fz_0011__en-us_topic_0167652100_b61222025142217">Network</strong> > <strong id="elb_ug_fz_0011__en-us_topic_0167652100_b4124425142210">Elastic Load Balancing</strong>. </li><li id="elb_ug_fz_0011__en-us_topic_0093321970_li162431917151414">In the upper right corner of the load balancer list, click <span><img id="elb_ug_fz_0011__en-us_topic_0093321970_image56755919206" src="en-us_image_0000001794660541.png"></span>.</li></ol>
|
<div class="section" id="elb_ug_fz_0011__section19169366120"><h4 class="sectiontitle">Procedure</h4><ol id="elb_ug_fz_0011__en-us_topic_0093321970_ol18971723131315"><li id="elb_ug_fz_0011__li104062575369">Log in to the management console.</li><li id="elb_ug_fz_0011__li640635753619">In the upper left corner of the page, click <span><img id="elb_ug_fz_0011__image533015024823" src="en-us_image_0000001747739624.png"></span> and select the desired region and project.</li><li id="elb_ug_fz_0011__li17301740102218">Click <span><img id="elb_ug_fz_0011__image479669228228" src="en-us_image_0000001794660485.png"></span> in the upper left corner to display <strong id="elb_ug_fz_0011__b2463906818228">Service List</strong> and choose <strong id="elb_ug_fz_0011__b14637288268228">Network</strong> > <strong id="elb_ug_fz_0011__b6616341868228">Elastic Load Balancing</strong>.</li><li id="elb_ug_fz_0011__li4508337155620">In the upper left corner of the load balancer list, click <strong id="elb_ug_fz_0011__b2078074941916">Export</strong>.</li></ol>
|
||||||
</div>
|
</div>
|
||||||
</div>
|
</div>
|
||||||
<div>
|
<div>
|
||||||
|
@ -6,8 +6,7 @@
|
|||||||
</div></div>
|
</div></div>
|
||||||
</div>
|
</div>
|
||||||
<div class="section" id="elb_ug_fz_0015__section12411142510365"><h4 class="sectiontitle">Modifying the Bandwidth</h4><p id="elb_ug_fz_0015__p241118251361">When you modify the bandwidth, traffic routing will not be interrupted.</p>
|
<div class="section" id="elb_ug_fz_0015__section12411142510365"><h4 class="sectiontitle">Modifying the Bandwidth</h4><p id="elb_ug_fz_0015__p241118251361">When you modify the bandwidth, traffic routing will not be interrupted.</p>
|
||||||
<ol id="elb_ug_fz_0015__ol16411125143617"><li id="elb_ug_fz_0015__li741120255362">Log in to the management console.</li><li id="elb_ug_fz_0015__li4412162513614">In the upper left corner of the page, click <span><img id="elb_ug_fz_0015__en-us_topic_0240829509_image1542118117117" src="en-us_image_0000001747739624.png"></span> and select the desired region and project.</li><li id="elb_ug_fz_0015__li4412192563615">Hover on <span><img id="elb_ug_fz_0015__en-us_topic_0167652100_image762510132322" src="en-us_image_0000001794660485.png"></span> in the upper left corner to display <strong id="elb_ug_fz_0015__en-us_topic_0167652100_b9121102522212">Service List</strong> and choose <strong id="elb_ug_fz_0015__en-us_topic_0167652100_b61222025142217">Network</strong> > <strong id="elb_ug_fz_0015__en-us_topic_0167652100_b4124425142210">Elastic Load Balancing</strong>. </li><li id="elb_ug_fz_0015__li7413142519362">On the <strong id="elb_ug_fz_0015__b118309556645840">Load Balancers</strong> page:<p id="elb_ug_fz_0015__p941317251361">Dedicated load balancers: Locate the load balancer and click <strong id="elb_ug_fz_0015__b67783518845840">Modify IPv4 Bandwidth</strong> or choose <strong id="elb_ug_fz_0015__b68593305245840">More</strong> > <strong id="elb_ug_fz_0015__b110385578745840">Modify IPv6 Bandwidth</strong> in the <strong id="elb_ug_fz_0015__b101129305745840">Operation</strong> column (if the load balancer has an IPv6 address that has been added to a shared bandwidth).</p>
|
<ol id="elb_ug_fz_0015__ol16411125143617"><li id="elb_ug_fz_0015__li741120255362">Log in to the management console.</li><li id="elb_ug_fz_0015__li4412162513614">In the upper left corner of the page, click <span><img id="elb_ug_fz_0015__image84151311329" src="en-us_image_0000001747739624.png"></span> and select the desired region and project.</li><li id="elb_ug_fz_0015__li4412192563615">Click <span><img id="elb_ug_fz_0015__image17525182512216" src="en-us_image_0000001794660485.png"></span> in the upper left corner to display <strong id="elb_ug_fz_0015__b15257251921">Service List</strong> and choose <strong id="elb_ug_fz_0015__b8525925220">Network</strong> > <strong id="elb_ug_fz_0015__b1752611251210">Elastic Load Balancing</strong>.</li><li id="elb_ug_fz_0015__li914418401691">On the <strong id="elb_ug_fz_0015__b19610124502812">Load Balancers</strong> page, locate the load balancer and click <strong id="elb_ug_fz_0015__b13226261843">More</strong> in the <strong id="elb_ug_fz_0015__b1122126345">Operation</strong> column.</li><li id="elb_ug_fz_0015__li1110217493117">Dedicated load balancers: Click <strong id="elb_ug_fz_0015__b148617135297">Modify IPv4 Bandwidth</strong> or <strong id="elb_ug_fz_0015__b18041717296">Modify IPv6 Bandwidth</strong>.<p id="elb_ug_fz_0015__p1264715397139">Shared load balancers: Click <strong id="elb_ug_fz_0015__b24961721122912">Modify IPv4 Bandwidth</strong>.</p>
|
||||||
<p id="elb_ug_fz_0015__p44139252365">Shared load balancers: Locate the load balancer and click <strong id="elb_ug_fz_0015__b29647971545840">Modify IPv4 Bandwidth</strong> in the <strong id="elb_ug_fz_0015__b175441670145840">Operation</strong> column.</p>
|
|
||||||
</li><li id="elb_ug_fz_0015__li154131425193614">In the <strong id="elb_ug_fz_0015__b107169693445840">New Configuration</strong> area, modify the bandwidth and click <strong id="elb_ug_fz_0015__b100774143045840">Next</strong>.<p id="elb_ug_fz_0015__p13413825143618">You can select the bandwidth defined by the system or customize the bandwidth. The bandwidth ranges from 1 Mbit/s to 1,000 Mbit/s.</p>
|
</li><li id="elb_ug_fz_0015__li154131425193614">In the <strong id="elb_ug_fz_0015__b107169693445840">New Configuration</strong> area, modify the bandwidth and click <strong id="elb_ug_fz_0015__b100774143045840">Next</strong>.<p id="elb_ug_fz_0015__p13413825143618">You can select the bandwidth defined by the system or customize the bandwidth. The bandwidth ranges from 1 Mbit/s to 1,000 Mbit/s.</p>
|
||||||
</li><li id="elb_ug_fz_0015__li8413192523612">Confirm the modified bandwidth and click <strong id="elb_ug_fz_0015__b1034754613366">Submit</strong>.</li></ol>
|
</li><li id="elb_ug_fz_0015__li8413192523612">Confirm the modified bandwidth and click <strong id="elb_ug_fz_0015__b1034754613366">Submit</strong>.</li></ol>
|
||||||
</div>
|
</div>
|
||||||
|
@ -42,7 +42,7 @@
|
|||||||
<div class="note" id="elb_ug_fz_0016__note176121233"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><div class="p" id="elb_ug_fz_0016__p277419221935">Downgrading specifications will temporarily affect services.<ul id="elb_ug_fz_0016__ul203162131837"><li id="elb_ug_fz_0016__li93164131634">Network load balancing (TCP/UDP): New connections may fail to establish.</li><li id="elb_ug_fz_0016__li53162013433">Application load balancing (HTTP/HTTPS): New connections may not be able to be established and some persistent connections may be interrupted.</li></ul>
|
<div class="note" id="elb_ug_fz_0016__note176121233"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><div class="p" id="elb_ug_fz_0016__p277419221935">Downgrading specifications will temporarily affect services.<ul id="elb_ug_fz_0016__ul203162131837"><li id="elb_ug_fz_0016__li93164131634">Network load balancing (TCP/UDP): New connections may fail to establish.</li><li id="elb_ug_fz_0016__li53162013433">Application load balancing (HTTP/HTTPS): New connections may not be able to be established and some persistent connections may be interrupted.</li></ul>
|
||||||
</div>
|
</div>
|
||||||
</div></div>
|
</div></div>
|
||||||
<ol id="elb_ug_fz_0016__ol1583571253"><li id="elb_ug_fz_0016__li1499011972516">Log in to the management console.</li><li id="elb_ug_fz_0016__li1991159172516">In the upper left corner of the page, click <span><img id="elb_ug_fz_0016__image02015242137" src="en-us_image_0000001747739624.png"></span> and select the desired region and project.</li><li id="elb_ug_fz_0016__li17301740102218">Hover on <span><img id="elb_ug_fz_0016__image174731025151311" src="en-us_image_0000001794660485.png"></span> in the upper left corner to display <strong id="elb_ug_fz_0016__b1747315252138">Service List</strong> and choose <strong id="elb_ug_fz_0016__b1847592561320">Network</strong> > <strong id="elb_ug_fz_0016__b15478172571313">Elastic Load Balancing</strong>.</li><li id="elb_ug_fz_0016__li467515291339">On the <strong id="elb_ug_fz_0016__b179016643745830">Load Balancers</strong> page, locate the load balancer whose specifications you want to modify, click <strong id="elb_ug_fz_0016__b85235419645830">More</strong> in the <strong id="elb_ug_fz_0016__b111184359245830">Operation</strong> column, and select <strong id="elb_ug_fz_0016__b134845194045830">Change Specifications</strong>.</li><li id="elb_ug_fz_0016__li119912913258">Select the new specifications and click <strong id="elb_ug_fz_0016__b69404554745830">Next</strong>.</li><li id="elb_ug_fz_0016__li11654104818397">Confirm the information and click <strong id="elb_ug_fz_0016__b31651356345830">Submit</strong>.</li></ol>
|
<ol id="elb_ug_fz_0016__ol1583571253"><li id="elb_ug_fz_0016__li1499011972516">Log in to the management console.</li><li id="elb_ug_fz_0016__li1991159172516">In the upper left corner of the page, click <span><img id="elb_ug_fz_0016__image02015242137" src="en-us_image_0000001747739624.png"></span> and select the desired region and project.</li><li id="elb_ug_fz_0016__li17301740102218">Click <span><img id="elb_ug_fz_0016__image174731025151311" src="en-us_image_0000001794660485.png"></span> in the upper left corner to display <strong id="elb_ug_fz_0016__b1747315252138">Service List</strong> and choose <strong id="elb_ug_fz_0016__b1847592561320">Network</strong> > <strong id="elb_ug_fz_0016__b15478172571313">Elastic Load Balancing</strong>.</li><li id="elb_ug_fz_0016__li467515291339">On the <strong id="elb_ug_fz_0016__b179016643745830">Load Balancers</strong> page, locate the load balancer whose specifications you want to modify, click <strong id="elb_ug_fz_0016__b85235419645830">More</strong> in the <strong id="elb_ug_fz_0016__b111184359245830">Operation</strong> column, and select <strong id="elb_ug_fz_0016__b134845194045830">Change Specifications</strong>.</li><li id="elb_ug_fz_0016__li119912913258">Select the new specifications and click <strong id="elb_ug_fz_0016__b69404554745830">Next</strong>.</li><li id="elb_ug_fz_0016__li11654104818397">Confirm the information and click <strong id="elb_ug_fz_0016__b31651356345830">Submit</strong>.</li></ol>
|
||||||
</div>
|
</div>
|
||||||
</div>
|
</div>
|
||||||
<div>
|
<div>
|
||||||
|
@ -1,17 +0,0 @@
|
|||||||
<a name="elb_ug_hc_0000"></a><a name="elb_ug_hc_0000"></a>
|
|
||||||
|
|
||||||
<h1 class="topictitle1">Health Check</h1>
|
|
||||||
<div id="body1554880416660"></div>
|
|
||||||
<div>
|
|
||||||
<ul class="ullinks">
|
|
||||||
<li class="ulchildlink"><strong><a href="elb_ug_hc_0001.html">Overview</a></strong><br>
|
|
||||||
</li>
|
|
||||||
<li class="ulchildlink"><strong><a href="en-us_topic_0162227063.html">Configuring a Health Check</a></strong><br>
|
|
||||||
</li>
|
|
||||||
<li class="ulchildlink"><strong><a href="elb_ug_hc_0005.html">Changing the Health Check Protocol</a></strong><br>
|
|
||||||
</li>
|
|
||||||
<li class="ulchildlink"><strong><a href="elb_ug_hc_0003.html">Disabling a Health Check</a></strong><br>
|
|
||||||
</li>
|
|
||||||
</ul>
|
|
||||||
</div>
|
|
||||||
|
|
File diff suppressed because it is too large
Load Diff
@ -1,15 +0,0 @@
|
|||||||
<a name="elb_ug_hc_0003"></a><a name="elb_ug_hc_0003"></a>
|
|
||||||
|
|
||||||
<h1 class="topictitle1">Disabling a Health Check</h1>
|
|
||||||
<div id="body1554880418073"><div class="section" id="elb_ug_hc_0003__section1481212713114"><h4 class="sectiontitle">Scenarios</h4><p id="elb_ug_hc_0003__p12671131175110">If you do not require health check, you can disable it when you add listeners. If you have already added listeners with health check enabled, you can also disable it when you modify the listeners.</p>
|
|
||||||
<p id="elb_ug_hc_0003__p4302165719110">After health check is disabled, the load balancer will consider all backend servers healthy and will still route requests to backend servers even if they are not working normally. As a result, applications on these servers are inaccessible. If this happens, ensure that the ports used by the backend servers are normal. Do not disable health check unless necessary.</p>
|
|
||||||
</div>
|
|
||||||
<div class="section" id="elb_ug_hc_0003__section3986711219"><h4 class="sectiontitle">Procedure</h4><ol id="elb_ug_hc_0003__ol89376506300"><li id="elb_ug_hc_0003__li677391520332">Log in to the management console.</li><li id="elb_ug_hc_0003__li675519100420">In the upper left corner of the page, click <span><img id="elb_ug_hc_0003__en-us_topic_0240829509_image1542118117117" src="en-us_image_0000001747739624.png"></span> and select the desired region and project.</li><li id="elb_ug_hc_0003__li83736197297">Hover on <span><img id="elb_ug_hc_0003__en-us_topic_0167652100_image762510132322" src="en-us_image_0000001794660485.png"></span> in the upper left corner to display <strong id="elb_ug_hc_0003__en-us_topic_0167652100_b9121102522212">Service List</strong> and choose <strong id="elb_ug_hc_0003__en-us_topic_0167652100_b61222025142217">Network</strong> > <strong id="elb_ug_hc_0003__en-us_topic_0167652100_b4124425142210">Elastic Load Balancing</strong>. </li><li id="elb_ug_hc_0003__li826120259204">Locate the load balancer and click its name.</li></ol><ol start="5" id="elb_ug_hc_0003__ol19800720131219"><li id="elb_ug_hc_0003__li207994203124">Click <strong id="elb_ug_hc_0003__b919914515157">Backend Server Groups</strong>, locate the backend <span id="elb_ug_hc_0003__text10799152018124">server</span> group, and click its name.</li><li id="elb_ug_hc_0003__li10799142011214">In the <strong id="elb_ug_hc_0003__b1776814399236">Basic Information</strong> area, click <strong id="elb_ug_hc_0003__b10769439202312">Configure</strong> next to <strong id="elb_ug_hc_0003__b15769113962312">Health Check</strong>.</li></ol><ol start="7" id="elb_ug_hc_0003__ol1658400181413"><li id="elb_ug_hc_0003__li1858317091415">In the <strong id="elb_ug_hc_0003__b085196191617">Configure Health Check</strong> dialog box, disable the health check.</li></ol><ol start="8" id="elb_ug_hc_0003__ol1986661951414"><li id="elb_ug_hc_0003__li1086614191148">Click <strong id="elb_ug_hc_0003__b207371201552">OK</strong>.</li></ol>
|
|
||||||
</div>
|
|
||||||
</div>
|
|
||||||
<div>
|
|
||||||
<div class="familylinks">
|
|
||||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="elb_ug_hc_0000.html">Health Check</a></div>
|
|
||||||
</div>
|
|
||||||
</div>
|
|
||||||
|
|
@ -1,15 +0,0 @@
|
|||||||
<a name="elb_ug_hc_0005"></a><a name="elb_ug_hc_0005"></a>
|
|
||||||
|
|
||||||
<h1 class="topictitle1">Changing the Health Check Protocol</h1>
|
|
||||||
<div id="body1599790719987"><div class="section" id="elb_ug_hc_0005__section1121010331536"><h4 class="sectiontitle">Scenarios</h4><p id="elb_ug_hc_0005__p10969115116258">You can change the health check protocol as required. After the protocol is changed, the load balancer uses the new protocol to detect the health of backend servers, and it continues to route traffic to the backend servers after they are detected healthy.</p>
|
|
||||||
<p id="elb_ug_hc_0005__p56365397479">During this period, the load balancer may return the HTTP 503 error code to the clients.</p>
|
|
||||||
</div>
|
|
||||||
<div class="section" id="elb_ug_hc_0005__section126005588310"><h4 class="sectiontitle">Procedure</h4><ol id="elb_ug_hc_0005__ol5312821122018"><li id="elb_ug_hc_0005__li677391520332">Log in to the management console.</li><li id="elb_ug_hc_0005__li675519100420">In the upper left corner of the page, click <span><img id="elb_ug_hc_0005__en-us_topic_0240829509_image1542118117117" src="en-us_image_0000001747739624.png"></span> and select the desired region and project.</li><li id="elb_ug_hc_0005__li83736197297">Hover on <span><img id="elb_ug_hc_0005__en-us_topic_0167652100_image762510132322" src="en-us_image_0000001794660485.png"></span> in the upper left corner to display <strong id="elb_ug_hc_0005__en-us_topic_0167652100_b9121102522212">Service List</strong> and choose <strong id="elb_ug_hc_0005__en-us_topic_0167652100_b61222025142217">Network</strong> > <strong id="elb_ug_hc_0005__en-us_topic_0167652100_b4124425142210">Elastic Load Balancing</strong>. </li><li id="elb_ug_hc_0005__li826120259204">Locate the load balancer and click its name.</li><li id="elb_ug_hc_0005__li119961554152810">Click <strong id="elb_ug_hc_0005__b197034217173">Backend Server Groups</strong>, locate the backend server group, and click its name.</li><li id="elb_ug_hc_0005__li416017569309">Click <strong id="elb_ug_hc_0005__b1051863016179">More</strong> in the <strong id="elb_ug_hc_0005__b951953010173">Operation</strong> column.</li><li id="elb_ug_hc_0005__li1438812372133">Select <strong id="elb_ug_hc_0005__b85441132121712">Configure Health Check</strong> from the drop-down list.</li><li id="elb_ug_hc_0005__li1623598131117">In the <strong id="elb_ug_hc_0005__b17337634122312">Basic Information</strong> area, click <strong id="elb_ug_hc_0005__b4337173442319">Configure</strong> next to <strong id="elb_ug_hc_0005__b2338153414233">Health Check</strong>.</li><li id="elb_ug_hc_0005__li353264814359">Change the health check protocol.</li><li id="elb_ug_hc_0005__li1884133194615">Click <strong id="elb_ug_hc_0005__b207371201552">OK</strong>.</li></ol>
|
|
||||||
</div>
|
|
||||||
</div>
|
|
||||||
<div>
|
|
||||||
<div class="familylinks">
|
|
||||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="elb_ug_hc_0000.html">Health Check</a></div>
|
|
||||||
</div>
|
|
||||||
</div>
|
|
||||||
|
|
15
docs/elb/umn/elb_ug_hd2_0000.html
Normal file
15
docs/elb/umn/elb_ug_hd2_0000.html
Normal file
@ -0,0 +1,15 @@
|
|||||||
|
<a name="elb_ug_hd2_0000"></a><a name="elb_ug_hd2_0000"></a>
|
||||||
|
|
||||||
|
<h1 class="topictitle1">Backend Server (Shared Load Balancers)</h1>
|
||||||
|
<div id="body8662426"></div>
|
||||||
|
<div>
|
||||||
|
<ul class="ullinks">
|
||||||
|
<li class="ulchildlink"><strong><a href="elb_ug_hd2_0001.html">Overview</a></strong><br>
|
||||||
|
</li>
|
||||||
|
<li class="ulchildlink"><strong><a href="elb_ug_hd_0002.html">Configuring Security Group and Firewall Rules</a></strong><br>
|
||||||
|
</li>
|
||||||
|
<li class="ulchildlink"><strong><a href="elb_ug_hd2_0003.html">Managing Backend Servers</a></strong><br>
|
||||||
|
</li>
|
||||||
|
</ul>
|
||||||
|
</div>
|
||||||
|
|
48
docs/elb/umn/elb_ug_hd2_0001.html
Normal file
48
docs/elb/umn/elb_ug_hd2_0001.html
Normal file
@ -0,0 +1,48 @@
|
|||||||
|
<a name="elb_ug_hd2_0001"></a><a name="elb_ug_hd2_0001"></a>
|
||||||
|
|
||||||
|
<h1 class="topictitle1">Overview</h1>
|
||||||
|
<div id="body8662426"><p id="elb_ug_hd2_0001__p17989102822315">Backend servers receive and process requests from the associated load balancer.</p>
|
||||||
|
<p id="elb_ug_hd2_0001__en-us_topic_0000001384422734_p24672418012">If the incoming traffic increases, you can add more backend servers to ensure the stability and reliability of applications and eliminate SPOFs. If the incoming traffic decreases, you can remove some backend servers to reduce costs.</p>
|
||||||
|
<p id="elb_ug_hd2_0001__en-us_topic_0000001384422734_en-us_topic_0237163437_p147921630749">If the load balancer is associated with an AS group, backend servers are automatically associated with or disassociated from the load balancer.</p>
|
||||||
|
<p id="elb_ug_hd2_0001__p1880613613282">You can only add servers in the same VPC as the load balancer. For details, see <a href="elb_ug_hd2_0003_01.html">Adding Backend Servers</a>.</p>
|
||||||
|
<div class="section" id="elb_ug_hd2_0001__en-us_topic_0000001456485765_section10505173011816"><h4 class="sectiontitle">Precautions</h4><ul id="elb_ug_hd2_0001__en-us_topic_0000001470778697_ul872011396174"><li id="elb_ug_hd2_0001__en-us_topic_0000001470778697_li117801845111719">It is recommended that you select backend servers running the same OS for easier management and maintenance.</li></ul>
|
||||||
|
<ul id="elb_ug_hd2_0001__en-us_topic_0000001470778697_en-us_topic_0000001384422734_ul73727864619"><li id="elb_ug_hd2_0001__en-us_topic_0000001470778697_en-us_topic_0000001384422734_li19602011171016">The load balancer checks the health of each server added to the associated backend server group if you have configured health check for the backend server group. If a backend server responds normally, the load balancer will consider it healthy. If a backend server responds abnormally, the load balancer will periodically check its health until the backend server is considered healthy.</li><li id="elb_ug_hd2_0001__en-us_topic_0000001470778697_en-us_topic_0000001384422734_li7670111820107">If a backend server is stopped or restarted, connections established with this server will be disconnected, and data being transmitted over these connections will be lost. To avoid this from happening, configure the retry function on the clients to prevent data loss.</li><li id="elb_ug_hd2_0001__en-us_topic_0000001470778697_en-us_topic_0000001384422734_li1437298174611">If you enable sticky sessions, traffic to backend servers may be unbalanced. If this happens, disable sticky sessions and check the requests received by each backend server.</li></ul>
|
||||||
|
</div>
|
||||||
|
<div class="section" id="elb_ug_hd2_0001__en-us_topic_0000001456485765_section14679112320124"><h4 class="sectiontitle">Constraints and Limitations</h4><ul id="elb_ug_hd2_0001__en-us_topic_0000001456485765_ul12290181581811"><li id="elb_ug_hd2_0001__en-us_topic_0000001456485765_li16911992016">A maximum of 500 backend servers can be added to a backend server group.</li><li id="elb_ug_hd2_0001__en-us_topic_0000001456485765_li19386154971510">Inbound security group rules must be configured to allow traffic over the port of each backend server and the health check port. For details, see <a href="elb_ug_hd_0002.html">Configuring Security Group and Firewall Rules</a>.</li></ul>
|
||||||
|
</div>
|
||||||
|
<div class="section" id="elb_ug_hd2_0001__en-us_topic_0000001456485765_section747447113118"><a name="elb_ug_hd2_0001__en-us_topic_0000001456485765_section747447113118"></a><a name="en-us_topic_0000001456485765_section747447113118"></a><h4 class="sectiontitle">Backend Server Weights</h4><p id="elb_ug_hd2_0001__en-us_topic_0000001470778697_en-us_topic_0000001384422734_p14750103113544">You need to set a weight for each backend server in a backend server group. The higher the weight, the more requests the backend server receives.</p>
|
||||||
|
<p id="elb_ug_hd2_0001__en-us_topic_0000001470778697_en-us_topic_0000001384422734_p65481273554">The weight ranges from <strong id="elb_ug_hd2_0001__b149271931203214">0</strong> to <strong id="elb_ug_hd2_0001__b992733119321">100</strong>. If you set the weight of a backend server to <strong id="elb_ug_hd2_0001__b2092819315326">0</strong>, new requests will not be routed to this server.</p>
|
||||||
|
<p id="elb_ug_hd2_0001__en-us_topic_0000001470778697_p6456174511313">Three load balancing algorithms allow you to set weights to backend servers, as described in <a href="#elb_ug_hd2_0001__en-us_topic_0000001470778697_table0105125317327">Table 1</a>. For more information about load balancing algorithms, see <a href="elb_ug_jt_0003.html">Load Balancing Algorithms</a>.</p>
|
||||||
|
|
||||||
|
<div class="tablenoborder"><a name="elb_ug_hd2_0001__en-us_topic_0000001470778697_table0105125317327"></a><a name="en-us_topic_0000001470778697_table0105125317327"></a><table cellpadding="4" cellspacing="0" summary="" id="elb_ug_hd2_0001__en-us_topic_0000001470778697_table0105125317327" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Server weights in different load balancing algorithms</caption><thead align="left"><tr id="elb_ug_hd2_0001__en-us_topic_0000001470778697_row191053532323"><th align="left" class="cellrowborder" valign="top" width="24.41%" id="mcps1.3.7.5.2.3.1.1"><p id="elb_ug_hd2_0001__en-us_topic_0000001470778697_p310565319325">Load Balancing Algorithm</p>
|
||||||
|
</th>
|
||||||
|
<th align="left" class="cellrowborder" valign="top" width="75.59%" id="mcps1.3.7.5.2.3.1.2"><p id="elb_ug_hd2_0001__en-us_topic_0000001470778697_p9673144523310">Weight Setting</p>
|
||||||
|
</th>
|
||||||
|
</tr>
|
||||||
|
</thead>
|
||||||
|
<tbody><tr id="elb_ug_hd2_0001__en-us_topic_0000001470778697_row1810545343215"><td class="cellrowborder" valign="top" width="24.41%" headers="mcps1.3.7.5.2.3.1.1 "><p id="elb_ug_hd2_0001__en-us_topic_0000001470778697_p11105153123210">Weighted round robin</p>
|
||||||
|
</td>
|
||||||
|
<td class="cellrowborder" valign="top" width="75.59%" headers="mcps1.3.7.5.2.3.1.2 "><ul id="elb_ug_hd2_0001__en-us_topic_0000001470778697_ul2070275713222"><li id="elb_ug_hd2_0001__en-us_topic_0000001470778697_li0702125702218">If none of the servers have a weight of 0, the load balancer routes requests to backend servers based on their weights. Backend servers with higher weights receive proportionately more requests.</li><li id="elb_ug_hd2_0001__en-us_topic_0000001470778697_li69542007234">If two backend servers have the same weights, they receive the same number of requests.</li></ul>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
<tr id="elb_ug_hd2_0001__en-us_topic_0000001470778697_row910515533326"><td class="cellrowborder" valign="top" width="24.41%" headers="mcps1.3.7.5.2.3.1.1 "><p id="elb_ug_hd2_0001__en-us_topic_0000001470778697_p14105115383217">Weighted least connections</p>
|
||||||
|
</td>
|
||||||
|
<td class="cellrowborder" valign="top" width="75.59%" headers="mcps1.3.7.5.2.3.1.2 "><ul id="elb_ug_hd2_0001__en-us_topic_0000001470778697_ul9807731238"><li id="elb_ug_hd2_0001__en-us_topic_0000001470778697_li1580718362317">If none of the backend servers have a weight of 0, the load balancer calculates the load of each backend server using the formula (Overhead = Number of current connections/Backend server weight).</li><li id="elb_ug_hd2_0001__en-us_topic_0000001470778697_li29271672237">The load balancer routes requests to the backend server with the lowest overhead.</li></ul>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
<tr id="elb_ug_hd2_0001__en-us_topic_0000001470778697_row810512539322"><td class="cellrowborder" valign="top" width="24.41%" headers="mcps1.3.7.5.2.3.1.1 "><p id="elb_ug_hd2_0001__en-us_topic_0000001470778697_p810575310322">Source IP hash</p>
|
||||||
|
</td>
|
||||||
|
<td class="cellrowborder" valign="top" width="75.59%" headers="mcps1.3.7.5.2.3.1.2 "><ul id="elb_ug_hd2_0001__en-us_topic_0000001470778697_ul17597426152318"><li id="elb_ug_hd2_0001__en-us_topic_0000001470778697_li5597112618231">If none of the backend servers have a weight of 0, the requests from the same client are routed to the same backend server within a period of time.</li><li id="elb_ug_hd2_0001__en-us_topic_0000001470778697_li45381828172320">If the weight of a backend server is 0, no requests are routed to this backend server.</li></ul>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
</tbody>
|
||||||
|
</table>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
<div>
|
||||||
|
<div class="familylinks">
|
||||||
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="elb_ug_hd2_0000.html">Backend Server (Shared Load Balancers)</a></div>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
|
21
docs/elb/umn/elb_ug_hd2_0003.html
Normal file
21
docs/elb/umn/elb_ug_hd2_0003.html
Normal file
@ -0,0 +1,21 @@
|
|||||||
|
<a name="elb_ug_hd2_0003"></a><a name="elb_ug_hd2_0003"></a>
|
||||||
|
|
||||||
|
<h1 class="topictitle1">Managing Backend Servers</h1>
|
||||||
|
<div id="body8662426"></div>
|
||||||
|
<div>
|
||||||
|
<ul class="ullinks">
|
||||||
|
<li class="ulchildlink"><strong><a href="elb_ug_hd2_0003_01.html">Adding Backend Servers</a></strong><br>
|
||||||
|
</li>
|
||||||
|
<li class="ulchildlink"><strong><a href="elb_ug_hd2_0003_02.html">Viewing Backend Servers</a></strong><br>
|
||||||
|
</li>
|
||||||
|
<li class="ulchildlink"><strong><a href="elb_ug_hd2_0003_03.html">Removing Backend Servers</a></strong><br>
|
||||||
|
</li>
|
||||||
|
<li class="ulchildlink"><strong><a href="elb_ug_hd2_0003_04.html">Changing Backend Server Weights</a></strong><br>
|
||||||
|
</li>
|
||||||
|
</ul>
|
||||||
|
|
||||||
|
<div class="familylinks">
|
||||||
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="elb_ug_hd2_0000.html">Backend Server (Shared Load Balancers)</a></div>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
|
19
docs/elb/umn/elb_ug_hd2_0003_01.html
Normal file
19
docs/elb/umn/elb_ug_hd2_0003_01.html
Normal file
@ -0,0 +1,19 @@
|
|||||||
|
<a name="elb_ug_hd2_0003_01"></a><a name="elb_ug_hd2_0003_01"></a>
|
||||||
|
|
||||||
|
<h1 class="topictitle1">Adding Backend Servers</h1>
|
||||||
|
<div id="body8662426"><div class="section" id="elb_ug_hd2_0003_01__en-us_topic_0000001406125918_section55691341173019"><h4 class="sectiontitle">Scenario</h4><p id="elb_ug_hd2_0003_01__en-us_topic_0000001406125918_p1258710299613">You can add backend servers to a backend server group to process requests from clients.</p>
|
||||||
|
<p id="elb_ug_hd2_0003_01__en-us_topic_0000001406285894_en-us_topic_0237163437_p885734911310">When you use ELB to route requests, ensure that at least one backend server is running normally and can receive requests routed by the load balancer.</p>
|
||||||
|
<p id="elb_ug_hd2_0003_01__en-us_topic_0000001406285894_en-us_topic_0237163437_p14672198046">If a backend server is removed, it is disassociated from the load balancer and can still run normally. However, it cannot receive requests from the load balancer. You can add the backend server to the backend server group again when traffic increases or the reliability needs to be enhanced.</p>
|
||||||
|
</div>
|
||||||
|
<div class="section" id="elb_ug_hd2_0003_01__en-us_topic_0000001406125918_section09141458143016"><h4 class="sectiontitle">Constraints and Limitations</h4><p id="elb_ug_hd2_0003_01__en-us_topic_0000001406125918_p3688924172819">Only servers in the same VPC as the load balancer can be added.</p>
|
||||||
|
</div>
|
||||||
|
<div class="section" id="elb_ug_hd2_0003_01__en-us_topic_0000001406125918_section2617111193110"><h4 class="sectiontitle">Procedure</h4><ol id="elb_ug_hd2_0003_01__ol72121839141017"><li id="elb_ug_hd2_0003_01__en-us_topic_0000001439637645_li195153301329">Log in to the management console.</li><li id="elb_ug_hd2_0003_01__en-us_topic_0000001439637645_li149716294347">In the upper left corner of the page, click <span><img id="elb_ug_hd2_0003_01__image9104414786917" src="en-us_image_0000001747739624.png"></span> and select the desired region and project.</li><li id="elb_ug_hd2_0003_01__en-us_topic_0000001439637645_li1141022273516">Click <span><img id="elb_ug_hd2_0003_01__image124701827155110" src="en-us_image_0000001794660485.png"></span> in the upper left corner to display <strong id="elb_ug_hd2_0003_01__b1847042715519">Service List</strong> and choose <strong id="elb_ug_hd2_0003_01__b94722277519">Network</strong> > <strong id="elb_ug_hd2_0003_01__b847342720519">Elastic Load Balancing</strong>.</li><li id="elb_ug_hd2_0003_01__li858934311566">In the navigation pane on the left, choose <strong id="elb_ug_hd2_0003_01__b6773155114">Elastic Load Balancing</strong> > <strong id="elb_ug_hd2_0003_01__b178431115112">Backend Server Groups</strong>.</li><li id="elb_ug_hd2_0003_01__li2951145515614">On the <strong id="elb_ug_hd2_0003_01__b41834133537">Backend Server Groups</strong> page, click the name of the backend server group.</li><li id="elb_ug_hd2_0003_01__li138518113571">Switch to the <strong id="elb_ug_hd2_0003_01__b1780632165316">Backend Servers</strong> tab and click <strong id="elb_ug_hd2_0003_01__b188061021185312">Add</strong> on the right.</li><li id="elb_ug_hd2_0003_01__li1109156205717">Search for backend servers using keywords. </li><li id="elb_ug_hd2_0003_01__en-us_topic_0000001439637645_li20553057761">Specify the weights and ports for the backend servers, and click <strong id="elb_ug_hd2_0003_01__b66076241616">Finish</strong>.<p id="elb_ug_hd2_0003_01__p2276463561">Backend server ports can be set in batches.</p>
|
||||||
|
</li></ol>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
<div>
|
||||||
|
<div class="familylinks">
|
||||||
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="elb_ug_hd2_0003.html">Managing Backend Servers</a></div>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
|
14
docs/elb/umn/elb_ug_hd2_0003_02.html
Normal file
14
docs/elb/umn/elb_ug_hd2_0003_02.html
Normal file
@ -0,0 +1,14 @@
|
|||||||
|
<a name="elb_ug_hd2_0003_02"></a><a name="elb_ug_hd2_0003_02"></a>
|
||||||
|
|
||||||
|
<h1 class="topictitle1">Viewing Backend Servers</h1>
|
||||||
|
<div id="body8662426"><div class="section" id="elb_ug_hd2_0003_02__en-us_topic_0000001456405693_section1272110277488"><h4 class="sectiontitle">Scenario</h4><p id="elb_ug_hd2_0003_02__en-us_topic_0000001470898713_en-us_topic_0000001441695393_p1063653152314">You can view the added backend servers in a backend server group. For example, you can view their status, private IP addresses, health check results, weights, and ports.</p>
|
||||||
|
</div>
|
||||||
|
<div class="section" id="elb_ug_hd2_0003_02__en-us_topic_0000001456405693_section1099714362482"><h4 class="sectiontitle">Procedure</h4><ol id="elb_ug_hd2_0003_02__en-us_topic_0000001470898713_en-us_topic_0000001441695393_ol14514133043212"><li id="elb_ug_hd2_0003_02__en-us_topic_0000001470898713_en-us_topic_0000001441695393_li195153301329">Log in to the management console.</li><li id="elb_ug_hd2_0003_02__en-us_topic_0000001470898713_en-us_topic_0000001441695393_li149716294347">In the upper left corner of the page, click <span><img id="elb_ug_hd2_0003_02__image15654049366917" src="en-us_image_0000001747739624.png"></span> and select the desired region and project.</li><li id="elb_ug_hd2_0003_02__en-us_topic_0000001470898713_en-us_topic_0000001441695393_li1141022273516">Click <span><img id="elb_ug_hd2_0003_02__image71184297475131" src="en-us_image_0000001794660485.png"></span> in the upper left corner to display <strong id="elb_ug_hd2_0003_02__b87127504875131">Service List</strong> and choose <strong id="elb_ug_hd2_0003_02__b156885464175131">Network</strong> > <strong id="elb_ug_hd2_0003_02__b39734304875131">Elastic Load Balancing</strong>.</li><li id="elb_ug_hd2_0003_02__en-us_topic_0000001470898713_en-us_topic_0000001441695393_li20553057761">In the navigation pane on the left, choose <strong id="elb_ug_hd2_0003_02__b55696195375155">Elastic Load Balancing</strong> > <strong id="elb_ug_hd2_0003_02__b185835692075155">Backend Server Groups</strong>.</li><li id="elb_ug_hd2_0003_02__en-us_topic_0000001470898713_en-us_topic_0000001441695393_li0670204023612">On the <strong id="elb_ug_hd2_0003_02__b1945174711558">Backend Server Groups</strong> page, click the name of the backend server group.</li><li id="elb_ug_hd2_0003_02__en-us_topic_0000001470898713_en-us_topic_0000001441695393_li35731251105414">Switch to the <strong id="elb_ug_hd2_0003_02__b274273011567">Backend Servers</strong> tab and click <strong id="elb_ug_hd2_0003_02__b14742143016565">Backend Servers</strong>.</li><li id="elb_ug_hd2_0003_02__en-us_topic_0000001470898713_en-us_topic_0000001441695393_li889585223011">In the backend server list, view the backend servers.</li></ol>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
<div>
|
||||||
|
<div class="familylinks">
|
||||||
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="elb_ug_hd2_0003.html">Managing Backend Servers</a></div>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
|
15
docs/elb/umn/elb_ug_hd2_0003_03.html
Normal file
15
docs/elb/umn/elb_ug_hd2_0003_03.html
Normal file
@ -0,0 +1,15 @@
|
|||||||
|
<a name="elb_ug_hd2_0003_03"></a><a name="elb_ug_hd2_0003_03"></a>
|
||||||
|
|
||||||
|
<h1 class="topictitle1">Removing Backend Servers</h1>
|
||||||
|
<div id="body8662426"><div class="section" id="elb_ug_hd2_0003_03__en-us_topic_0000001456486069_section192853054618"><h4 class="sectiontitle">Scenario</h4><p id="elb_ug_hd2_0003_03__en-us_topic_0000001420819874_en-us_topic_0000001389158858_p1366417203238">You can remove a backend server that is no longer needed from a backend server group.</p>
|
||||||
|
<p id="elb_ug_hd2_0003_03__en-us_topic_0000001420819874_p3496941102715">If a backend server is removed, it is disassociated from the load balancer and can still run normally. However, it cannot receive requests from the load balancer. You can add the backend server to the backend server group again when traffic increases or the reliability needs to be enhanced.</p>
|
||||||
|
</div>
|
||||||
|
<div class="section" id="elb_ug_hd2_0003_03__en-us_topic_0000001456486069_section3736614104618"><h4 class="sectiontitle">Procedure</h4><ol id="elb_ug_hd2_0003_03__en-us_topic_0000001420819874_en-us_topic_0000001389158858_ol14514133043212"><li id="elb_ug_hd2_0003_03__en-us_topic_0000001420819874_en-us_topic_0000001389158858_li195153301329">Log in to the management console.</li><li id="elb_ug_hd2_0003_03__en-us_topic_0000001420819874_en-us_topic_0000001389158858_li149716294347">In the upper left corner of the page, click <span><img id="elb_ug_hd2_0003_03__image4959786556918" src="en-us_image_0000001747739624.png"></span> and select the desired region and project.</li><li id="elb_ug_hd2_0003_03__en-us_topic_0000001420819874_en-us_topic_0000001389158858_li1141022273516">Click <span><img id="elb_ug_hd2_0003_03__image208343143775131" src="en-us_image_0000001794660485.png"></span> in the upper left corner to display <strong id="elb_ug_hd2_0003_03__b209397033775131">Service List</strong> and choose <strong id="elb_ug_hd2_0003_03__b42986572275131">Network</strong> > <strong id="elb_ug_hd2_0003_03__b80580016575131">Elastic Load Balancing</strong>.</li><li id="elb_ug_hd2_0003_03__en-us_topic_0000001420819874_en-us_topic_0000001389158858_li20553057761">In the navigation pane on the left, choose <strong id="elb_ug_hd2_0003_03__b37049379575156">Elastic Load Balancing</strong> > <strong id="elb_ug_hd2_0003_03__b168555198375156">Backend Server Groups</strong>.</li><li id="elb_ug_hd2_0003_03__en-us_topic_0000001420819874_en-us_topic_0000001389158858_li0670204023612">On the <strong id="elb_ug_hd2_0003_03__b59902057589">Backend Server Groups</strong> page, click the name of the backend server group. </li><li id="elb_ug_hd2_0003_03__en-us_topic_0000001420819874_en-us_topic_0000001389158858_li1638414174311">Switch to the <strong id="elb_ug_hd2_0003_03__b14611118975639">Backend Servers</strong> tab and click <strong id="elb_ug_hd2_0003_03__b168249440575639">Backend Servers</strong>.</li><li id="elb_ug_hd2_0003_03__en-us_topic_0000001420819874_en-us_topic_0000001389158858_li583573145517">Select the backend servers you want to remove and click <strong id="elb_ug_hd2_0003_03__b12723134135916">Remove</strong> above the backend server list.</li><li id="elb_ug_hd2_0003_03__en-us_topic_0000001420819874_en-us_topic_0000001389158858_li128181118115416">In the displayed dialog box, click <strong id="elb_ug_hd2_0003_03__b178612919591">Yes</strong>.</li></ol>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
<div>
|
||||||
|
<div class="familylinks">
|
||||||
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="elb_ug_hd2_0003.html">Managing Backend Servers</a></div>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
|
19
docs/elb/umn/elb_ug_hd2_0003_04.html
Normal file
19
docs/elb/umn/elb_ug_hd2_0003_04.html
Normal file
@ -0,0 +1,19 @@
|
|||||||
|
<a name="elb_ug_hd2_0003_04"></a><a name="elb_ug_hd2_0003_04"></a>
|
||||||
|
|
||||||
|
<h1 class="topictitle1">Changing Backend Server Weights</h1>
|
||||||
|
<div id="body8662426"><div class="section" id="elb_ug_hd2_0003_04__en-us_topic_0000001456165713_section1684643485113"><h4 class="sectiontitle">Scenario</h4><p id="elb_ug_hd2_0003_04__en-us_topic_0000001420979186_en-us_topic_0000001391917484_p1668113092420">You can change the weights specified for backend servers based on their capability to process requests.</p>
|
||||||
|
</div>
|
||||||
|
<div class="section" id="elb_ug_hd2_0003_04__en-us_topic_0000001456165713_section138147532442"><h4 class="sectiontitle">Constraints and Limitations</h4><ul id="elb_ug_hd2_0003_04__en-us_topic_0000001456165713_ul56361441103419"><li id="elb_ug_hd2_0003_04__en-us_topic_0000001456165713_li26362413343">The weight ranges from <strong id="elb_ug_hd2_0003_04__b126313006853315">0</strong> to <strong id="elb_ug_hd2_0003_04__b89721384153315">100</strong>. If you set the weight of a backend server to <strong id="elb_ug_hd2_0003_04__b86215266653315">0</strong>, new requests will not be routed to this server.</li><li id="elb_ug_hd2_0003_04__en-us_topic_0000001456165713_li998444416345">The weights can only be specified when you select weighted round robin, weighted least connections, or source IP hash as the load balancing algorithm. For more information about load balancing algorithms, see <a href="elb_ug_hd2_0001.html#elb_ug_hd2_0001__en-us_topic_0000001456485765_section747447113118">Backend Server Weights</a>.</li></ul>
|
||||||
|
</div>
|
||||||
|
<div class="section" id="elb_ug_hd2_0003_04__en-us_topic_0000001456165713_section1534011448515"><h4 class="sectiontitle">Procedure</h4><ol id="elb_ug_hd2_0003_04__en-us_topic_0000001420979186_en-us_topic_0000001391917484_en-us_topic_0117477001_ol153371524105415"><li id="elb_ug_hd2_0003_04__en-us_topic_0000001420979186_en-us_topic_0000001391917484_li677391520332">Log in to the management console.</li><li id="elb_ug_hd2_0003_04__en-us_topic_0000001420979186_en-us_topic_0000001391917484_li675519100420">In the upper left corner of the page, click <span><img id="elb_ug_hd2_0003_04__en-us_topic_0000001420979186_en-us_topic_0240829509_image1542118117117" src="en-us_image_0000001794820037.png"></span> and select the desired region and project.</li><li id="elb_ug_hd2_0003_04__en-us_topic_0000001439637645_li1141022273516">Click <span><img id="elb_ug_hd2_0003_04__image40156623575132" src="en-us_image_0000001794660485.png"></span> in the upper left corner to display <strong id="elb_ug_hd2_0003_04__b66966617775132">Service List</strong> and choose <strong id="elb_ug_hd2_0003_04__b50925163675132">Network</strong> > <strong id="elb_ug_hd2_0003_04__b149393178375132">Elastic Load Balancing</strong>.</li><li id="elb_ug_hd2_0003_04__en-us_topic_0000001439637645_li20553057761">In the navigation pane on the left, choose <strong id="elb_ug_hd2_0003_04__b113968477275157">Elastic Load Balancing</strong> > <strong id="elb_ug_hd2_0003_04__b113737306475157">Backend Server Groups</strong>.</li><li id="elb_ug_hd2_0003_04__en-us_topic_0000001420979186_en-us_topic_0000001391917484_en-us_topic_0117477001_li1133822465414">On the <strong id="elb_ug_hd2_0003_04__b89351647165914">Backend Server Groups</strong> page, click the name of the backend server group.</li><li id="elb_ug_hd2_0003_04__en-us_topic_0000001420979186_en-us_topic_0000001391917484_li9497198183116">Switch to the <strong id="elb_ug_hd2_0003_04__b765410472120">Backend Servers</strong> tab and click <strong id="elb_ug_hd2_0003_04__b76551547512">Backend Servers</strong>.</li><li id="elb_ug_hd2_0003_04__en-us_topic_0000001420979186_li17987104142817">Select the backend servers and click <strong id="elb_ug_hd2_0003_04__b1424145410111">Modify Weight</strong> above the backend server list.</li><li id="elb_ug_hd2_0003_04__en-us_topic_0000001420979186_en-us_topic_0000001391917484_li151816716194">In the displayed dialog box, change the weights as you need.<ul id="elb_ug_hd2_0003_04__en-us_topic_0000001420979186_ul14989991913"><li id="elb_ug_hd2_0003_04__en-us_topic_0000001420979186_li1622714565336">Changing the weight of a single backend server: Set the weight in the <strong id="elb_ug_hd2_0003_04__b1514471022">Weight</strong> column.</li><li id="elb_ug_hd2_0003_04__en-us_topic_0000001420979186_li20177172893412">Changing the weights of multiple backend servers: Set the weight next to <strong id="elb_ug_hd2_0003_04__b863517164215">Batch Modify Weights</strong> and click <strong id="elb_ug_hd2_0003_04__b7636141614211">OK</strong>.</li></ul>
|
||||||
|
<div class="note" id="elb_ug_hd2_0003_04__en-us_topic_0000001420979186_note917792819344"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="elb_ug_hd2_0003_04__en-us_topic_0000001420979186_p19177162843413">You can change the weights of multiple backend servers to <strong id="elb_ug_hd2_0003_04__b1386615266215">0</strong> so they will not receive requests from the load balancer.</p>
|
||||||
|
</div></div>
|
||||||
|
</li><li id="elb_ug_hd2_0003_04__en-us_topic_0000001420979186_li1675617327339">Click <strong id="elb_ug_hd2_0003_04__b620316155451">OK</strong>.</li></ol>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
<div>
|
||||||
|
<div class="familylinks">
|
||||||
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="elb_ug_hd2_0003.html">Managing Backend Servers</a></div>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
|
17
docs/elb/umn/elb_ug_hd3_0000.html
Normal file
17
docs/elb/umn/elb_ug_hd3_0000.html
Normal file
@ -0,0 +1,17 @@
|
|||||||
|
<a name="elb_ug_hd3_0000"></a><a name="elb_ug_hd3_0000"></a>
|
||||||
|
|
||||||
|
<h1 class="topictitle1">Backend Server (Dedicated Load Balancers)</h1>
|
||||||
|
<div id="body8662426"></div>
|
||||||
|
<div>
|
||||||
|
<ul class="ullinks">
|
||||||
|
<li class="ulchildlink"><strong><a href="elb_ug_hd3_0001.html">Overview</a></strong><br>
|
||||||
|
</li>
|
||||||
|
<li class="ulchildlink"><strong><a href="elb_ug_hd_0007.html">Configuring Security Group and Firewall Rules</a></strong><br>
|
||||||
|
</li>
|
||||||
|
<li class="ulchildlink"><strong><a href="elb_ug_hd3_0003.html">Managing Backend Servers</a></strong><br>
|
||||||
|
</li>
|
||||||
|
<li class="ulchildlink"><strong><a href="elb_ug_hd3_0004.html">IP Addresses as Backend Servers</a></strong><br>
|
||||||
|
</li>
|
||||||
|
</ul>
|
||||||
|
</div>
|
||||||
|
|
78
docs/elb/umn/elb_ug_hd3_0001.html
Normal file
78
docs/elb/umn/elb_ug_hd3_0001.html
Normal file
@ -0,0 +1,78 @@
|
|||||||
|
<a name="elb_ug_hd3_0001"></a><a name="elb_ug_hd3_0001"></a>
|
||||||
|
|
||||||
|
<h1 class="topictitle1">Overview</h1>
|
||||||
|
<div id="body8662426"><p id="elb_ug_hd3_0001__p17989102822315">Backend servers receive and process requests from the associated load balancer.</p>
|
||||||
|
<p id="elb_ug_hd3_0001__en-us_topic_0000001384422734_p24672418012">If the incoming traffic increases, you can add more backend servers to ensure the stability and reliability of applications and eliminate SPOFs. If the incoming traffic decreases, you can remove some backend servers to reduce costs.</p>
|
||||||
|
<p id="elb_ug_hd3_0001__en-us_topic_0000001384422734_en-us_topic_0237163437_p147921630749">If the load balancer is associated with an AS group, backend servers are automatically associated with or disassociated from the load balancer.</p>
|
||||||
|
|
||||||
|
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="elb_ug_hd3_0001__table16605112117218" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Adding backend servers</caption><thead align="left"><tr id="elb_ug_hd3_0001__en-us_topic_0000001464593065_row16793145184413"><th align="left" class="cellrowborder" valign="top" width="20.32203220322032%" id="mcps1.3.4.2.4.1.1"><p id="elb_ug_hd3_0001__en-us_topic_0000001464593065_p14718558541">Backend Server Type</p>
|
||||||
|
</th>
|
||||||
|
<th align="left" class="cellrowborder" valign="top" width="48.244824482448244%" id="mcps1.3.4.2.4.1.2"><p id="elb_ug_hd3_0001__en-us_topic_0000001464593065_p779416519443">Description</p>
|
||||||
|
</th>
|
||||||
|
<th align="left" class="cellrowborder" valign="top" width="31.433143314331435%" id="mcps1.3.4.2.4.1.3"><p id="elb_ug_hd3_0001__en-us_topic_0000001464593065_p13794135124410">Reference</p>
|
||||||
|
</th>
|
||||||
|
</tr>
|
||||||
|
</thead>
|
||||||
|
<tbody><tr id="elb_ug_hd3_0001__en-us_topic_0000001464593065_row14794195120449"><td class="cellrowborder" valign="top" width="20.32203220322032%" headers="mcps1.3.4.2.4.1.1 "><p id="elb_ug_hd3_0001__en-us_topic_0000001464593065_p279405144414">Cloud servers</p>
|
||||||
|
</td>
|
||||||
|
<td class="cellrowborder" valign="top" width="48.244824482448244%" headers="mcps1.3.4.2.4.1.2 "><p id="elb_ug_hd3_0001__en-us_topic_0000001464593065_p1079425114410">You can add ECSs or BMSs that are in the same VPC as the load balancer.</p>
|
||||||
|
</td>
|
||||||
|
<td class="cellrowborder" valign="top" width="31.433143314331435%" headers="mcps1.3.4.2.4.1.3 "><p id="elb_ug_hd3_0001__en-us_topic_0000001464593065_p167944516441"><a href="elb_ug_hd3_0003_01.html">Adding Backend Servers</a></p>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
<tr id="elb_ug_hd3_0001__en-us_topic_0000001464593065_row10663111011542"><td class="cellrowborder" valign="top" width="20.32203220322032%" headers="mcps1.3.4.2.4.1.1 "><p id="elb_ug_hd3_0001__en-us_topic_0000001464593065_p18663171010548">IP as backend servers</p>
|
||||||
|
</td>
|
||||||
|
<td class="cellrowborder" valign="top" width="48.244824482448244%" headers="mcps1.3.4.2.4.1.2 "><p id="elb_ug_hd3_0001__en-us_topic_0000001464593065_p106693131304">You can add cloud servers in other VPCs or on-premises servers if IP as a backend is enabled for the load balancer.</p>
|
||||||
|
</td>
|
||||||
|
<td class="cellrowborder" valign="top" width="31.433143314331435%" headers="mcps1.3.4.2.4.1.3 "><p id="elb_ug_hd3_0001__en-us_topic_0000001464593065_p53593320117"><a href="elb_ug_hd3_0004_03.html">Adding IP Addresses as Backend Servers</a></p>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
</tbody>
|
||||||
|
</table>
|
||||||
|
</div>
|
||||||
|
<div class="section" id="elb_ug_hd3_0001__en-us_topic_0000001384422734_section1756715023715"><h4 class="sectiontitle">Precautions</h4><ul id="elb_ug_hd3_0001__ul872011396174"><li id="elb_ug_hd3_0001__li117801845111719">It is recommended that you select backend servers running the same OS for easier management and maintenance.</li></ul>
|
||||||
|
<ul id="elb_ug_hd3_0001__en-us_topic_0000001384422734_ul73727864619"><li id="elb_ug_hd3_0001__en-us_topic_0000001384422734_li19602011171016">The load balancer checks the health of each server added to the associated backend server group if you have configured health check for the backend server group. If a backend server responds normally, the load balancer will consider it healthy. If a backend server responds abnormally, the load balancer will periodically check its health until the backend server is considered healthy.</li><li id="elb_ug_hd3_0001__en-us_topic_0000001384422734_li7670111820107">If a backend server is stopped or restarted, connections established with this server will be disconnected, and data being transmitted over these connections will be lost. To avoid this from happening, configure the retry function on the clients to prevent data loss.</li><li id="elb_ug_hd3_0001__en-us_topic_0000001384422734_li1437298174611">If you enable sticky sessions, traffic to backend servers may be unbalanced. If this happens, disable sticky sessions and check the requests received by each backend server.</li></ul>
|
||||||
|
</div>
|
||||||
|
<div class="section" id="elb_ug_hd3_0001__en-us_topic_0000001384422734_section1661134617020"><h4 class="sectiontitle">Constraints and Limitations</h4><ul id="elb_ug_hd3_0001__en-us_topic_0000001384422734_ul0680457805"><li id="elb_ug_hd3_0001__en-us_topic_0000001384422734_li16680185712018">A maximum of 500 backend servers can be added to a backend server group.</li><li id="elb_ug_hd3_0001__en-us_topic_0000001384422734_li19386154971510">Inbound security group rules must be configured to allow traffic over the port of each backend server and the health check port. For details, see <a href="elb_ug_hd_0007.html">Configuring Security Group and Firewall Rules</a>.</li><li id="elb_ug_hd3_0001__li59542379239">If you select only network load balancing, a server cannot serve as both a backend server and a client.</li></ul>
|
||||||
|
</div>
|
||||||
|
<div class="section" id="elb_ug_hd3_0001__en-us_topic_0000001384422734_section84064491587"><a name="elb_ug_hd3_0001__en-us_topic_0000001384422734_section84064491587"></a><a name="en-us_topic_0000001384422734_section84064491587"></a><h4 class="sectiontitle">Backend Server Weights</h4><p id="elb_ug_hd3_0001__en-us_topic_0000001384422734_p14750103113544">You need to set a weight for each backend server in a backend server group to receive requests. The higher the weight, the more requests the backend server receives.</p>
|
||||||
|
<p id="elb_ug_hd3_0001__en-us_topic_0000001384422734_p65481273554">The weight ranges from <strong id="elb_ug_hd3_0001__b34661516184812">0</strong> to <strong id="elb_ug_hd3_0001__b154675163488">100</strong>. If you set the weight of a backend server to <strong id="elb_ug_hd3_0001__b1646710166489">0</strong>, new requests will not be routed to this server.</p>
|
||||||
|
<p id="elb_ug_hd3_0001__p6456174511313">Three load balancing algorithms allow you to set weights to backend servers, as shown in the following table. For more information about load balancing algorithms, see <a href="elb_ug_jt_0003.html">Load Balancing Algorithms</a>.</p>
|
||||||
|
|
||||||
|
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="elb_ug_hd3_0001__table0105125317327" frame="border" border="1" rules="all"><caption><b>Table 2 </b>Server weights in different load balancing algorithms</caption><thead align="left"><tr id="elb_ug_hd3_0001__row191053532323"><th align="left" class="cellrowborder" valign="top" width="18.35%" id="mcps1.3.7.5.2.3.1.1"><p id="elb_ug_hd3_0001__p310565319325">Load Balancing Algorithm</p>
|
||||||
|
</th>
|
||||||
|
<th align="left" class="cellrowborder" valign="top" width="81.65%" id="mcps1.3.7.5.2.3.1.2"><p id="elb_ug_hd3_0001__p9673144523310">Weight Setting Description</p>
|
||||||
|
</th>
|
||||||
|
</tr>
|
||||||
|
</thead>
|
||||||
|
<tbody><tr id="elb_ug_hd3_0001__row1810545343215"><td class="cellrowborder" valign="top" width="18.35%" headers="mcps1.3.7.5.2.3.1.1 "><p id="elb_ug_hd3_0001__p11105153123210">Weighted round robin</p>
|
||||||
|
</td>
|
||||||
|
<td class="cellrowborder" valign="top" width="81.65%" headers="mcps1.3.7.5.2.3.1.2 "><ul id="elb_ug_hd3_0001__ul2070275713222"><li id="elb_ug_hd3_0001__li0702125702218">If none of the backend servers have a weight of 0, the load balancer routes requests to backend servers based on their weights. Backend servers with higher weights receive proportionately more requests.</li><li id="elb_ug_hd3_0001__li69542007234">If two backend servers have the same weights, they receive the same number of requests.</li></ul>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
<tr id="elb_ug_hd3_0001__row910515533326"><td class="cellrowborder" valign="top" width="18.35%" headers="mcps1.3.7.5.2.3.1.1 "><p id="elb_ug_hd3_0001__p14105115383217">Weighted least connections</p>
|
||||||
|
</td>
|
||||||
|
<td class="cellrowborder" valign="top" width="81.65%" headers="mcps1.3.7.5.2.3.1.2 "><ul id="elb_ug_hd3_0001__ul9807731238"><li id="elb_ug_hd3_0001__li1580718362317">If none of the backend servers have a weight of 0, the load balancer calculates the load of each backend server using the formula (Overhead = Number of current connections/Backend server weight).</li><li id="elb_ug_hd3_0001__li29271672237">The load balancer routes requests to the backend server with the lowest overhead.</li></ul>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
<tr id="elb_ug_hd3_0001__row810512539322"><td class="cellrowborder" valign="top" width="18.35%" headers="mcps1.3.7.5.2.3.1.1 "><p id="elb_ug_hd3_0001__p810575310322">Source IP hash</p>
|
||||||
|
</td>
|
||||||
|
<td class="cellrowborder" valign="top" width="81.65%" headers="mcps1.3.7.5.2.3.1.2 "><ul id="elb_ug_hd3_0001__ul17597426152318"><li id="elb_ug_hd3_0001__li5597112618231">If none of the backend servers have a weight of 0, requests from the same client are routed to the same backend server within a period of time.</li><li id="elb_ug_hd3_0001__li45381828172320">If the weight of a backend server is 0, no requests are routed to this backend server.</li></ul>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
<tr id="elb_ug_hd3_0001__row6475192316155"><td class="cellrowborder" valign="top" width="18.35%" headers="mcps1.3.7.5.2.3.1.1 "><p id="elb_ug_hd3_0001__p194761423181518">Connection ID</p>
|
||||||
|
</td>
|
||||||
|
<td class="cellrowborder" valign="top" width="81.65%" headers="mcps1.3.7.5.2.3.1.2 "><ul id="elb_ug_hd3_0001__ul28581016191811"><li id="elb_ug_hd3_0001__li085881671819">If none of the backend servers have a weight of 0, the requests from the same client are routed to the same backend server within a period of time.</li><li id="elb_ug_hd3_0001__li36818872019">If the weight of a backend server is 0, no requests are routed to this backend server.</li></ul>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
</tbody>
|
||||||
|
</table>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
<div>
|
||||||
|
<div class="familylinks">
|
||||||
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="elb_ug_hd3_0000.html">Backend Server (Dedicated Load Balancers)</a></div>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
|
21
docs/elb/umn/elb_ug_hd3_0003.html
Normal file
21
docs/elb/umn/elb_ug_hd3_0003.html
Normal file
@ -0,0 +1,21 @@
|
|||||||
|
<a name="elb_ug_hd3_0003"></a><a name="elb_ug_hd3_0003"></a>
|
||||||
|
|
||||||
|
<h1 class="topictitle1">Managing Backend Servers</h1>
|
||||||
|
<div id="body8662426"></div>
|
||||||
|
<div>
|
||||||
|
<ul class="ullinks">
|
||||||
|
<li class="ulchildlink"><strong><a href="elb_ug_hd3_0003_01.html">Adding Backend Servers</a></strong><br>
|
||||||
|
</li>
|
||||||
|
<li class="ulchildlink"><strong><a href="elb_ug_hd3_0003_02.html">Viewing Backend Servers</a></strong><br>
|
||||||
|
</li>
|
||||||
|
<li class="ulchildlink"><strong><a href="elb_ug_hd3_0003_03.html">Removing Backend Servers</a></strong><br>
|
||||||
|
</li>
|
||||||
|
<li class="ulchildlink"><strong><a href="elb_ug_hd3_0003_04.html">Changing Backend Server Weights</a></strong><br>
|
||||||
|
</li>
|
||||||
|
</ul>
|
||||||
|
|
||||||
|
<div class="familylinks">
|
||||||
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="elb_ug_hd3_0000.html">Backend Server (Dedicated Load Balancers)</a></div>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
|
18
docs/elb/umn/elb_ug_hd3_0003_01.html
Normal file
18
docs/elb/umn/elb_ug_hd3_0003_01.html
Normal file
@ -0,0 +1,18 @@
|
|||||||
|
<a name="elb_ug_hd3_0003_01"></a><a name="elb_ug_hd3_0003_01"></a>
|
||||||
|
|
||||||
|
<h1 class="topictitle1">Adding Backend Servers</h1>
|
||||||
|
<div id="body8662426"><div class="section" id="elb_ug_hd3_0003_01__en-us_topic_0000001439637645_section178506259224"><h4 class="sectiontitle">Scenario</h4><p id="elb_ug_hd3_0003_01__en-us_topic_0000001439637645_p1258710299613">When you use ELB to route traffic to backend servers, you need to ensure that at least one backend server is running normally and can receive requests from the associated load balancer.</p>
|
||||||
|
<p id="elb_ug_hd3_0003_01__p79311437142912">If the incoming traffic increases, you can add more backend servers to ensure the stability and reliability of applications and eliminate SPOFs. If the incoming traffic decreases, you can remove some backend servers to reduce costs.</p>
|
||||||
|
</div>
|
||||||
|
<div class="section" id="elb_ug_hd3_0003_01__en-us_topic_0000001439637645_section345985062712"><h4 class="sectiontitle">Constraints and Limitations</h4><ul id="elb_ug_hd3_0003_01__en-us_topic_0000001439637645_ul12850168285"><li id="elb_ug_hd3_0003_01__en-us_topic_0000001439637645_li1085015682815">The cloud servers must be in the same VPC as the backend server group.</li></ul>
|
||||||
|
</div>
|
||||||
|
<div class="section" id="elb_ug_hd3_0003_01__en-us_topic_0000001439637645_section55561057202215"><h4 class="sectiontitle">Procedure</h4><ol id="elb_ug_hd3_0003_01__en-us_topic_0000001439637645_ol14514133043212"><li id="elb_ug_hd3_0003_01__en-us_topic_0000001439637645_li195153301329">Log in to the management console.</li><li id="elb_ug_hd3_0003_01__en-us_topic_0000001439637645_li149716294347">In the upper left corner of the page, click <span><img id="elb_ug_hd3_0003_01__image42371500481314" src="en-us_image_0000001747739624.png"></span> and select the desired region and project.</li><li id="elb_ug_hd3_0003_01__en-us_topic_0000001439637645_li1141022273516">Click <span><img id="elb_ug_hd3_0003_01__image833032811164" src="en-us_image_0000001794660485.png"></span> in the upper left corner to display <strong id="elb_ug_hd3_0003_01__b113308285161">Service List</strong> and choose <strong id="elb_ug_hd3_0003_01__b6332112819163">Network</strong> > <strong id="elb_ug_hd3_0003_01__b733311288163">Elastic Load Balancing</strong>.</li><li id="elb_ug_hd3_0003_01__en-us_topic_0000001439637645_li20553057761">In the navigation pane on the left, choose <strong id="elb_ug_hd3_0003_01__b16801833101613">Elastic Load Balancing</strong> > <strong id="elb_ug_hd3_0003_01__b68083341610">Backend Server Groups</strong>.</li><li id="elb_ug_hd3_0003_01__en-us_topic_0000001439637645_li0670204023612">On the <strong id="elb_ug_hd3_0003_01__b4197154216169">Backend Server Groups</strong> page, click the name of the backend server group.</li><li id="elb_ug_hd3_0003_01__en-us_topic_0000001439637645_li35731251105414">Switch to the <strong id="elb_ug_hd3_0003_01__b17405204720168">Backend Servers</strong> tab and click <strong id="elb_ug_hd3_0003_01__b124051947131615">Add</strong> on the right.</li><li id="elb_ug_hd3_0003_01__li1238313285389">Search for backend servers using keywords. </li><li id="elb_ug_hd3_0003_01__en-us_topic_0000001439637645_li574554155515">Specify the weights and ports for the backend servers, and click <strong id="elb_ug_hd3_0003_01__b580012370615">Finish</strong>.<p id="elb_ug_hd3_0003_01__p637015281505">Backend server ports can be set in batches.</p>
|
||||||
|
</li></ol>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
<div>
|
||||||
|
<div class="familylinks">
|
||||||
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="elb_ug_hd3_0003.html">Managing Backend Servers</a></div>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
|
14
docs/elb/umn/elb_ug_hd3_0003_02.html
Normal file
14
docs/elb/umn/elb_ug_hd3_0003_02.html
Normal file
@ -0,0 +1,14 @@
|
|||||||
|
<a name="elb_ug_hd3_0003_02"></a><a name="elb_ug_hd3_0003_02"></a>
|
||||||
|
|
||||||
|
<h1 class="topictitle1">Viewing Backend Servers</h1>
|
||||||
|
<div id="body8662426"><div class="section" id="elb_ug_hd3_0003_02__en-us_topic_0000001441695393_section154641443132312"><h4 class="sectiontitle">Scenario</h4><p id="elb_ug_hd3_0003_02__en-us_topic_0000001441695393_p1063653152314">You can view backend servers that have been added to a backend server group. For example, you can view their status, private IP addresses, health check results, weights, and ports.</p>
|
||||||
|
</div>
|
||||||
|
<div class="section" id="elb_ug_hd3_0003_02__en-us_topic_0000001441695393_section598717562230"><h4 class="sectiontitle">Procedure</h4><ol id="elb_ug_hd3_0003_02__en-us_topic_0000001441695393_ol14514133043212"><li id="elb_ug_hd3_0003_02__en-us_topic_0000001441695393_li195153301329">Log in to the management console.</li><li id="elb_ug_hd3_0003_02__en-us_topic_0000001441695393_li149716294347">In the upper left corner of the page, click <span><img id="elb_ug_hd3_0003_02__image157291203681315" src="en-us_image_0000001747739624.png"></span> and select the desired region and project.</li><li id="elb_ug_hd3_0003_02__en-us_topic_0000001441695393_li1141022273516">Click <span><img id="elb_ug_hd3_0003_02__image168362156791633" src="en-us_image_0000001794660485.png"></span> in the upper left corner to display <strong id="elb_ug_hd3_0003_02__b196014181291633">Service List</strong> and choose <strong id="elb_ug_hd3_0003_02__b190201872791633">Network</strong> > <strong id="elb_ug_hd3_0003_02__b91741804591633">Elastic Load Balancing</strong>.</li><li id="elb_ug_hd3_0003_02__en-us_topic_0000001441695393_li20553057761">In the navigation pane on the left, choose <strong id="elb_ug_hd3_0003_02__b159579062591642">Elastic Load Balancing</strong> > <strong id="elb_ug_hd3_0003_02__b186907764791642">Backend Server Groups</strong>.</li><li id="elb_ug_hd3_0003_02__en-us_topic_0000001441695393_li0670204023612">On the <strong id="elb_ug_hd3_0003_02__b79031043212">Backend Server Groups</strong> page, click the name of the backend server group.</li><li id="elb_ug_hd3_0003_02__en-us_topic_0000001441695393_li35731251105414">Switch to the <strong id="elb_ug_hd3_0003_02__b1041278142110">Backend Servers</strong> tab and click <strong id="elb_ug_hd3_0003_02__b74130817216">Backend Servers</strong>.</li><li id="elb_ug_hd3_0003_02__en-us_topic_0000001441695393_li889585223011">In the backend server list, view the backend servers.</li></ol>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
<div>
|
||||||
|
<div class="familylinks">
|
||||||
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="elb_ug_hd3_0003.html">Managing Backend Servers</a></div>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
|
15
docs/elb/umn/elb_ug_hd3_0003_03.html
Normal file
15
docs/elb/umn/elb_ug_hd3_0003_03.html
Normal file
@ -0,0 +1,15 @@
|
|||||||
|
<a name="elb_ug_hd3_0003_03"></a><a name="elb_ug_hd3_0003_03"></a>
|
||||||
|
|
||||||
|
<h1 class="topictitle1">Removing Backend Servers</h1>
|
||||||
|
<div id="body8662426"><div class="section" id="elb_ug_hd3_0003_03__en-us_topic_0000001389158858_section148451716237"><h4 class="sectiontitle">Scenario</h4><p id="elb_ug_hd3_0003_03__en-us_topic_0000001389158858_p1366417203238">You can remove a backend server that is no longer needed from a backend server group.</p>
|
||||||
|
<p id="elb_ug_hd3_0003_03__p3496941102715">If a backend server is removed, it is disassociated from the load balancer and can still run normally. However, it cannot receive requests from the load balancer. You can add the backend server to the backend server group again when traffic increases or the reliability needs to be enhanced.</p>
|
||||||
|
</div>
|
||||||
|
<div class="section" id="elb_ug_hd3_0003_03__en-us_topic_0000001389158858_section111611727172310"><h4 class="sectiontitle">Procedure</h4><ol id="elb_ug_hd3_0003_03__en-us_topic_0000001389158858_ol14514133043212"><li id="elb_ug_hd3_0003_03__en-us_topic_0000001389158858_li195153301329">Log in to the management console.</li><li id="elb_ug_hd3_0003_03__en-us_topic_0000001389158858_li149716294347">In the upper left corner of the page, click <span><img id="elb_ug_hd3_0003_03__image181591719281315" src="en-us_image_0000001747739624.png"></span> and select the desired region and project.</li><li id="elb_ug_hd3_0003_03__en-us_topic_0000001389158858_li1141022273516">Click <span><img id="elb_ug_hd3_0003_03__image108121790691633" src="en-us_image_0000001794660485.png"></span> in the upper left corner to display <strong id="elb_ug_hd3_0003_03__b29703021891633">Service List</strong> and choose <strong id="elb_ug_hd3_0003_03__b12284138391633">Network</strong> > <strong id="elb_ug_hd3_0003_03__b80562213191633">Elastic Load Balancing</strong>.</li><li id="elb_ug_hd3_0003_03__en-us_topic_0000001389158858_li20553057761">In the navigation pane on the left, choose <strong id="elb_ug_hd3_0003_03__b176120029991643">Elastic Load Balancing</strong> > <strong id="elb_ug_hd3_0003_03__b75453793991643">Backend Server Groups</strong>.</li><li id="elb_ug_hd3_0003_03__en-us_topic_0000001389158858_li0670204023612">On the <strong id="elb_ug_hd3_0003_03__b2264175182315">Backend Server Groups</strong> page, click the name of the backend server group. </li><li id="elb_ug_hd3_0003_03__en-us_topic_0000001389158858_li1638414174311">Switch to the <strong id="elb_ug_hd3_0003_03__b81949255492110">Backend Servers</strong> tab and click <strong id="elb_ug_hd3_0003_03__b24246717092110">Backend Servers</strong>.</li><li id="elb_ug_hd3_0003_03__en-us_topic_0000001389158858_li583573145517">Select the backend servers you want to remove and click <strong id="elb_ug_hd3_0003_03__b72851332419">Remove</strong> above the backend server list.</li><li id="elb_ug_hd3_0003_03__en-us_topic_0000001389158858_li128181118115416">In the displayed dialog box, click <strong id="elb_ug_hd3_0003_03__b1712055720249">Yes</strong>.</li></ol>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
<div>
|
||||||
|
<div class="familylinks">
|
||||||
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="elb_ug_hd3_0003.html">Managing Backend Servers</a></div>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
|
20
docs/elb/umn/elb_ug_hd3_0003_04.html
Normal file
20
docs/elb/umn/elb_ug_hd3_0003_04.html
Normal file
@ -0,0 +1,20 @@
|
|||||||
|
<a name="elb_ug_hd3_0003_04"></a><a name="elb_ug_hd3_0003_04"></a>
|
||||||
|
|
||||||
|
<h1 class="topictitle1">Changing Backend Server Weights</h1>
|
||||||
|
<div id="body8662426"><div class="section" id="elb_ug_hd3_0003_04__en-us_topic_0000001391917484_section131561225112415"><h4 class="sectiontitle">Scenario</h4><p id="elb_ug_hd3_0003_04__en-us_topic_0000001391917484_p1668113092420">You can change the weights specified for backend servers based on their capability to process requests.</p>
|
||||||
|
</div>
|
||||||
|
<div class="section" id="elb_ug_hd3_0003_04__en-us_topic_0000001391917484_section14978524123417"><h4 class="sectiontitle">Constraints and Limitations</h4><ul id="elb_ug_hd3_0003_04__en-us_topic_0000001391917484_ul56361441103419"><li id="elb_ug_hd3_0003_04__en-us_topic_0000001391917484_li26362413343">The weight ranges from <strong id="elb_ug_hd3_0003_04__b180889070274832">0</strong> to <strong id="elb_ug_hd3_0003_04__b198120892574832">100</strong>. If you set the weight of a backend server to <strong id="elb_ug_hd3_0003_04__b127758998874832">0</strong>, new requests will not be routed to this server.</li><li id="elb_ug_hd3_0003_04__en-us_topic_0000001391917484_li998444416345">The weights can only be specified when you select weighted round robin, weighted least connections, or source IP hash as the load balancing algorithm. For more information about load balancing algorithms, see <a href="elb_ug_hd3_0001.html#elb_ug_hd3_0001__en-us_topic_0000001384422734_section84064491587">Backend Server Weights</a>.</li></ul>
|
||||||
|
</div>
|
||||||
|
<div class="section" id="elb_ug_hd3_0003_04__en-us_topic_0000001391917484_section1949153552417"><h4 class="sectiontitle">Procedure</h4><ol id="elb_ug_hd3_0003_04__en-us_topic_0000001391917484_en-us_topic_0117477001_ol153371524105415"><li id="elb_ug_hd3_0003_04__en-us_topic_0000001391917484_li677391520332">Log in to the management console.</li><li id="elb_ug_hd3_0003_04__en-us_topic_0000001391917484_li675519100420">In the upper left corner of the page, click <span><img id="elb_ug_hd3_0003_04__image136662934281316" src="en-us_image_0000001747739624.png"></span> and select the desired region and project.</li><li id="elb_ug_hd3_0003_04__en-us_topic_0000001391917484_li83736197297">Click <span><img id="elb_ug_hd3_0003_04__image3445496991634" src="en-us_image_0000001794660485.png"></span> in the upper left corner to display <strong id="elb_ug_hd3_0003_04__b137019340091634">Service List</strong> and choose <strong id="elb_ug_hd3_0003_04__b143498480591634">Network</strong> > <strong id="elb_ug_hd3_0003_04__b95405022791634">Elastic Load Balancing</strong>.</li><li id="elb_ug_hd3_0003_04__en-us_topic_0000001392237328_li20553057761">In the navigation pane on the left, choose <strong id="elb_ug_hd3_0003_04__b185182842591643">Elastic Load Balancing</strong> > <strong id="elb_ug_hd3_0003_04__b200492414391643">Backend Server Groups</strong>.</li><li id="elb_ug_hd3_0003_04__en-us_topic_0000001391917484_en-us_topic_0117477001_li1133822465414">On the <strong id="elb_ug_hd3_0003_04__b11420133182512">Backend Server Groups</strong> page, click the name of the backend server group.</li><li id="elb_ug_hd3_0003_04__en-us_topic_0000001391917484_li9497198183116">Switch to the <strong id="elb_ug_hd3_0003_04__b068910355253">Backend Servers</strong> tab and click <strong id="elb_ug_hd3_0003_04__b1368983518251">Backend Servers</strong>.</li><li id="elb_ug_hd3_0003_04__li17987104142817">Select the backend servers and click <strong id="elb_ug_hd3_0003_04__b11604143842515">Modify Port/Weight</strong> above the backend server list.</li><li id="elb_ug_hd3_0003_04__en-us_topic_0000001391917484_li151816716194">In the displayed dialog box, change the weights as you need.<ul id="elb_ug_hd3_0003_04__ul1369416452316"><li id="elb_ug_hd3_0003_04__li203941035183314">Changing weights:<ul id="elb_ug_hd3_0003_04__ul14989991913"><li id="elb_ug_hd3_0003_04__li1622714565336">Changing the weight of a single backend server: Set the weight in the <strong id="elb_ug_hd3_0003_04__b64621136172613">Weight</strong> column.</li><li id="elb_ug_hd3_0003_04__li20177172893412">Changing the weights of multiple backend servers: Set the weight next to <strong id="elb_ug_hd3_0003_04__b19815421260">Batch Modify Weights</strong> and click <strong id="elb_ug_hd3_0003_04__b149164220269">OK</strong>.</li></ul>
|
||||||
|
<div class="note" id="elb_ug_hd3_0003_04__note917792819344"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="elb_ug_hd3_0003_04__p19177162843413">You can change the weights of multiple backend servers to <strong id="elb_ug_hd3_0003_04__b1164212449267">0</strong> so they will not receive requests from the load balancer.</p>
|
||||||
|
</div></div>
|
||||||
|
</li></ul>
|
||||||
|
</li><li id="elb_ug_hd3_0003_04__li1675617327339">Click <strong id="elb_ug_hd3_0003_04__b1111915175011">OK</strong>.</li></ol>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
<div>
|
||||||
|
<div class="familylinks">
|
||||||
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="elb_ug_hd3_0003.html">Managing Backend Servers</a></div>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
|
25
docs/elb/umn/elb_ug_hd3_0004.html
Normal file
25
docs/elb/umn/elb_ug_hd3_0004.html
Normal file
@ -0,0 +1,25 @@
|
|||||||
|
<a name="elb_ug_hd3_0004"></a><a name="elb_ug_hd3_0004"></a>
|
||||||
|
|
||||||
|
<h1 class="topictitle1">IP Addresses as Backend Servers</h1>
|
||||||
|
<div id="body8662426"></div>
|
||||||
|
<div>
|
||||||
|
<ul class="ullinks">
|
||||||
|
<li class="ulchildlink"><strong><a href="elb_ug_hd3_0004_01.html">Overview</a></strong><br>
|
||||||
|
</li>
|
||||||
|
<li class="ulchildlink"><strong><a href="elb_ug_hd3_0004_02.html">Enabling IP as a Backend</a></strong><br>
|
||||||
|
</li>
|
||||||
|
<li class="ulchildlink"><strong><a href="elb_ug_hd3_0004_03.html">Adding IP Addresses as Backend Servers</a></strong><br>
|
||||||
|
</li>
|
||||||
|
<li class="ulchildlink"><strong><a href="elb_ug_hd3_0004_04.html">Viewing Backend Servers</a></strong><br>
|
||||||
|
</li>
|
||||||
|
<li class="ulchildlink"><strong><a href="elb_ug_hd3_0004_05.html">Removing Backend Servers</a></strong><br>
|
||||||
|
</li>
|
||||||
|
<li class="ulchildlink"><strong><a href="elb_ug_hd3_0004_06.html">Changing Backend Server Weights</a></strong><br>
|
||||||
|
</li>
|
||||||
|
</ul>
|
||||||
|
|
||||||
|
<div class="familylinks">
|
||||||
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="elb_ug_hd3_0000.html">Backend Server (Dedicated Load Balancers)</a></div>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
|
38
docs/elb/umn/elb_ug_hd3_0004_01.html
Normal file
38
docs/elb/umn/elb_ug_hd3_0004_01.html
Normal file
@ -0,0 +1,38 @@
|
|||||||
|
<a name="elb_ug_hd3_0004_01"></a><a name="elb_ug_hd3_0004_01"></a>
|
||||||
|
|
||||||
|
<h1 class="topictitle1">Overview</h1>
|
||||||
|
<div id="body8662426"><p id="elb_ug_hd3_0004_01__en-us_topic_0000001439818489_p1422589172817"><span id="elb_ug_hd3_0004_01__en-us_topic_0000001439818489_ph02255911282">Dedicated load balancers support hybrid load balancing. You can add servers and supplementary network interfaces in the VPC where the load balancer is created, in a different VPC, or in an on-premises data center, by using private IP addresses of the servers to the backend server group of the load balancer.</span></p>
|
||||||
|
<p id="elb_ug_hd3_0004_01__en-us_topic_0000001439818489_p14100101713279">In this way, incoming traffic can be flexibly distributed to cloud servers and on-premises servers.</p>
|
||||||
|
<div class="fignone" id="elb_ug_hd3_0004_01__en-us_topic_0000001439818489_fig184861133164013"><span class="figcap"><b>Figure 1 </b>Routing requests to cloud and on-premises servers</span><br><span><img id="elb_ug_hd3_0004_01__en-us_topic_0000001439818489_image94861033174018" src="en-us_image_0000001794819821.png"></span></div>
|
||||||
|
<div class="section" id="elb_ug_hd3_0004_01__section238985111148"><h4 class="sectiontitle">Constraints and Limitations</h4><ul id="elb_ug_hd3_0004_01__ul126564312157"><li id="elb_ug_hd3_0004_01__li86567310153">IP as a backend cannot be disabled after it is enabled.</li><li id="elb_ug_hd3_0004_01__li15656183101519">Only private IPv4 addresses can be added as backend servers.</li><li id="elb_ug_hd3_0004_01__li13656133161518">A maximum of 50,000 concurrent connections can be established with a backend server that is added by using its IP address.</li><li id="elb_ug_hd3_0004_01__li77681758134716">If you add IP addresses as backend servers, the source IP addresses of the clients cannot be passed to these servers. </li></ul>
|
||||||
|
</div>
|
||||||
|
<div class="section" id="elb_ug_hd3_0004_01__en-us_topic_0000001439818489_en-us_topic_0237163437_section245813014316"><h4 class="sectiontitle">Scenario</h4><p id="elb_ug_hd3_0004_01__en-us_topic_0000001439818489_p342451912446">If IP as a backend is enabled, you can add backend servers by using their IP addresses. You need to get prepared for different scenarios as shown in <a href="#elb_ug_hd3_0004_01__table39821317182412">Table 1</a>.</p>
|
||||||
|
|
||||||
|
<div class="tablenoborder"><a name="elb_ug_hd3_0004_01__table39821317182412"></a><a name="table39821317182412"></a><table cellpadding="4" cellspacing="0" summary="" id="elb_ug_hd3_0004_01__table39821317182412" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Adding IP addresses as backend servers</caption><thead align="left"><tr id="elb_ug_hd3_0004_01__row11982131792420"><th align="left" class="cellrowborder" valign="top" id="mcps1.3.5.3.2.4.1.1"><p id="elb_ug_hd3_0004_01__p098211711241">Where Servers Are Running</p>
|
||||||
|
</th>
|
||||||
|
<th align="left" class="cellrowborder" colspan="2" valign="top" id="mcps1.3.5.3.2.4.1.2"><p id="elb_ug_hd3_0004_01__p69821517162410">Preparations</p>
|
||||||
|
</th>
|
||||||
|
</tr>
|
||||||
|
</thead>
|
||||||
|
<tbody><tr id="elb_ug_hd3_0004_01__row498221719240"><td class="cellrowborder" valign="top" headers="mcps1.3.5.3.2.4.1.1 "><p id="elb_ug_hd3_0004_01__p11982161711243">In a VPC that is different from the VPC where the load balancer is running</p>
|
||||||
|
</td>
|
||||||
|
<td class="cellrowborder" colspan="2" valign="top" headers="mcps1.3.5.3.2.4.1.2 "><p id="elb_ug_hd3_0004_01__p1198291782410">Set up a VPC peering connection between the VPC where the load balancer is running and the VPC where the servers are running.</p>
|
||||||
|
<p id="elb_ug_hd3_0004_01__p1798291792415">For details about how to set up a VPC peering connection, see the Virtual Private Cloud User Guide.</p>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
<tr id="elb_ug_hd3_0004_01__row18982121792410"><td class="cellrowborder" valign="top" headers="mcps1.3.5.3.2.4.1.1 "><p id="elb_ug_hd3_0004_01__p1798271722410">In an on-premises data center</p>
|
||||||
|
</td>
|
||||||
|
<td class="cellrowborder" colspan="2" valign="top" headers="mcps1.3.5.3.2.4.1.2 "><p id="elb_ug_hd3_0004_01__p169821717152420">Connect the on-premises data center to the VPC where the load balancer is running through Direct Connect or VPN. For details about how to connect on-premises data centers to the cloud, see the Direct Connect User Guide or Virtual Private Network User Guide.</p>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
</tbody>
|
||||||
|
</table>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
<div>
|
||||||
|
<div class="familylinks">
|
||||||
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="elb_ug_hd3_0004.html">IP Addresses as Backend Servers</a></div>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
|
16
docs/elb/umn/elb_ug_hd3_0004_02.html
Normal file
16
docs/elb/umn/elb_ug_hd3_0004_02.html
Normal file
@ -0,0 +1,16 @@
|
|||||||
|
<a name="elb_ug_hd3_0004_02"></a><a name="elb_ug_hd3_0004_02"></a>
|
||||||
|
|
||||||
|
<h1 class="topictitle1">Enabling IP as a Backend</h1>
|
||||||
|
<div id="body8662426"><div class="section" id="elb_ug_hd3_0004_02__en-us_topic_0000001440018265_section1997816095314"><h4 class="sectiontitle">Scenario</h4><p id="elb_ug_hd3_0004_02__en-us_topic_0000001440018265_p1128415513530">You can enable IP as a backend for an existing dedicated load balancer.</p>
|
||||||
|
</div>
|
||||||
|
<div class="section" id="elb_ug_hd3_0004_02__en-us_topic_0000001440018265_section387118493118"><h4 class="sectiontitle">Constraints and Limitations</h4><ul id="elb_ug_hd3_0004_02__en-us_topic_0000001440018265_en-us_topic_0237163437_ul1047916271426"><li id="elb_ug_hd3_0004_02__li20197141484911">IP as a backend cannot be disabled after it is enabled.</li><li id="elb_ug_hd3_0004_02__li3656435154">The protocol of backend server groups can only be TCP, UDP, HTTP, or HTTPS.</li></ul>
|
||||||
|
</div>
|
||||||
|
<div class="section" id="elb_ug_hd3_0004_02__en-us_topic_0000001440018265_section67359557498"><h4 class="sectiontitle">Procedure</h4><ol id="elb_ug_hd3_0004_02__en-us_topic_0000001440018265_ol14514133043212"><li id="elb_ug_hd3_0004_02__en-us_topic_0000001440018265_li195153301329">Log in to the management console.</li><li id="elb_ug_hd3_0004_02__en-us_topic_0000001440018265_li149716294347">In the upper left corner of the page, click <span><img id="elb_ug_hd3_0004_02__image159710616781316" src="en-us_image_0000001747739624.png"></span> and select the desired region and project.</li><li id="elb_ug_hd3_0004_02__en-us_topic_0000001440018265_li1141022273516">Click <span><img id="elb_ug_hd3_0004_02__en-us_topic_0167652100_image762510132322" src="en-us_image_0000001747739640.png"></span> in the upper left corner to display <strong id="elb_ug_hd3_0004_02__b165124917599">Service List</strong> and choose <strong id="elb_ug_hd3_0004_02__b1967174914594">Network</strong> > <strong id="elb_ug_hd3_0004_02__b7692049145917">Elastic Load Balancing</strong>.</li><li id="elb_ug_hd3_0004_02__en-us_topic_0000001440018265_li12528192205718">On the <strong id="elb_ug_hd3_0004_02__b14575411705012">Load Balancers</strong> page, locate the load balancer and click its name.</li><li id="elb_ug_hd3_0004_02__en-us_topic_0000001440018265_li4682514589">On the <strong id="elb_ug_hd3_0004_02__b13541882835012">Summary</strong> tab, click <strong id="elb_ug_hd3_0004_02__b3562830745012">Enable</strong> next to <strong id="elb_ug_hd3_0004_02__b7508900205012">IP as a Backend</strong>.</li><li id="elb_ug_hd3_0004_02__en-us_topic_0000001440018265_li15204181935820">Click <strong id="elb_ug_hd3_0004_02__b8834882265012">OK</strong>.</li></ol>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
<div>
|
||||||
|
<div class="familylinks">
|
||||||
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="elb_ug_hd3_0004.html">IP Addresses as Backend Servers</a></div>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
|
39
docs/elb/umn/elb_ug_hd3_0004_03.html
Normal file
39
docs/elb/umn/elb_ug_hd3_0004_03.html
Normal file
@ -0,0 +1,39 @@
|
|||||||
|
<a name="elb_ug_hd3_0004_03"></a><a name="elb_ug_hd3_0004_03"></a>
|
||||||
|
|
||||||
|
<h1 class="topictitle1">Adding IP Addresses as Backend Servers</h1>
|
||||||
|
<div id="body8662426"><div class="section" id="elb_ug_hd3_0004_03__en-us_topic_0000001456696289_section7402335161"><h4 class="sectiontitle">Scenario</h4><p id="elb_ug_hd3_0004_03__en-us_topic_0000001456696289_p1258710299613">If you enable IP as a backend, you can associate backend servers with the load balancer by using their IP addresses.</p>
|
||||||
|
<p id="elb_ug_hd3_0004_03__p13475841165712">You need to get prepared for different scenarios as shown in <a href="#elb_ug_hd3_0004_03__en-us_topic_0000001439818489_table417613167431">Table 1</a>.</p>
|
||||||
|
|
||||||
|
<div class="tablenoborder"><a name="elb_ug_hd3_0004_03__en-us_topic_0000001439818489_table417613167431"></a><a name="en-us_topic_0000001439818489_table417613167431"></a><table cellpadding="4" cellspacing="0" summary="" id="elb_ug_hd3_0004_03__en-us_topic_0000001439818489_table417613167431" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Adding IP Addresses as Backend Servers</caption><thead align="left"><tr id="elb_ug_hd3_0004_03__en-us_topic_0000001420502302_row11982131792420"><th align="left" class="cellrowborder" valign="top" id="mcps1.3.1.4.2.4.1.1"><p id="elb_ug_hd3_0004_03__en-us_topic_0000001420502302_p098211711241">Where Servers Are Running</p>
|
||||||
|
</th>
|
||||||
|
<th align="left" class="cellrowborder" colspan="2" valign="top" id="mcps1.3.1.4.2.4.1.2"><p id="elb_ug_hd3_0004_03__en-us_topic_0000001420502302_p69821517162410">Preparations</p>
|
||||||
|
</th>
|
||||||
|
</tr>
|
||||||
|
</thead>
|
||||||
|
<tbody><tr id="elb_ug_hd3_0004_03__en-us_topic_0000001420502302_row498221719240"><td class="cellrowborder" valign="top" headers="mcps1.3.1.4.2.4.1.1 "><p id="elb_ug_hd3_0004_03__en-us_topic_0000001420502302_p11982161711243">In a VPC that is different from the VPC where the load balancer is running</p>
|
||||||
|
</td>
|
||||||
|
<td class="cellrowborder" colspan="2" valign="top" headers="mcps1.3.1.4.2.4.1.2 "><p id="elb_ug_hd3_0004_03__en-us_topic_0000001420502302_p1198291782410">Set up a VPC peering connection between the two VPCs.</p>
|
||||||
|
<p id="elb_ug_hd3_0004_03__en-us_topic_0000001420502302_p1798291792415">For details about how to set up a VPC peering connection, see the Virtual Private Cloud User Guide.</p>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
<tr id="elb_ug_hd3_0004_03__en-us_topic_0000001420502302_row18982121792410"><td class="cellrowborder" valign="top" headers="mcps1.3.1.4.2.4.1.1 "><p id="elb_ug_hd3_0004_03__en-us_topic_0000001420502302_p1798271722410">In an on-premises data center</p>
|
||||||
|
</td>
|
||||||
|
<td class="cellrowborder" colspan="2" valign="top" headers="mcps1.3.1.4.2.4.1.2 "><p id="elb_ug_hd3_0004_03__en-us_topic_0000001420502302_p169821717152420">Connect the on-premises data center to the VPC where the load balancer is running through Direct Connect or VPN. For details about how to connect on-premises data centers to the cloud, see the Direct Connect User Guide or Virtual Private Network User Guide.</p>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
</tbody>
|
||||||
|
</table>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
<div class="section" id="elb_ug_hd3_0004_03__section9901811192014"><h4 class="sectiontitle">Constraints and Limitations</h4><ul id="elb_ug_hd3_0004_03__ul739542812204"><li id="elb_ug_hd3_0004_03__li2039513287205">If IP as a backend is not enabled when you create a load balancer, you can enable it on the <strong id="elb_ug_hd3_0004_03__b4592823624577">Summary</strong> page of the load balancer.</li><li id="elb_ug_hd3_0004_03__li462024194310">Only private IPv4 addresses can be added as backend servers.</li></ul>
|
||||||
|
<ul id="elb_ug_hd3_0004_03__ul16395132815201"><li id="elb_ug_hd3_0004_03__li14395182882019">The backend subnet of the load balancer must have sufficient IP addresses. Otherwise, backend servers cannot be added through IP addresses. If the IP addresses are insufficient, you can add more backend subnets on the <strong id="elb_ug_hd3_0004_03__b17224374604577">Summary</strong> page of the load balancer.</li><li id="elb_ug_hd3_0004_03__li039552812205">Security group rules of backend servers added through IP addresses must allow traffic from the backend subnet of the load balancer. If traffic is not allowed, health checks will fail.</li></ul>
|
||||||
|
</div>
|
||||||
|
<div class="section" id="elb_ug_hd3_0004_03__en-us_topic_0000001456696289_section1798584315616"><h4 class="sectiontitle">Procedure</h4><ol id="elb_ug_hd3_0004_03__en-us_topic_0000001456696289_ol14514133043212"><li id="elb_ug_hd3_0004_03__en-us_topic_0000001456696289_li195153301329">Log in to the management console.</li><li id="elb_ug_hd3_0004_03__en-us_topic_0000001456696289_li149716294347">In the upper left corner of the page, click <span><img id="elb_ug_hd3_0004_03__image203037560581317" src="en-us_image_0000001747739624.png"></span> and select the desired region and project.</li><li id="elb_ug_hd3_0004_03__en-us_topic_0000001456696289_li1141022273516">Click <span><img id="elb_ug_hd3_0004_03__image170932581891635" src="en-us_image_0000001794660485.png"></span> in the upper left corner to display <strong id="elb_ug_hd3_0004_03__b27893151091635">Service List</strong> and choose <strong id="elb_ug_hd3_0004_03__b66899186391635">Network</strong> > <strong id="elb_ug_hd3_0004_03__b21673138391635">Elastic Load Balancing</strong>.</li><li id="elb_ug_hd3_0004_03__en-us_topic_0000001456696289_li20553057761">In the navigation pane on the left, choose <strong id="elb_ug_hd3_0004_03__b176726209291644">Elastic Load Balancing</strong> > <strong id="elb_ug_hd3_0004_03__b82652490491644">Backend Server Groups</strong>.</li><li id="elb_ug_hd3_0004_03__en-us_topic_0000001456696289_li0670204023612">On the <strong id="elb_ug_hd3_0004_03__b280951015201">Backend Server Groups</strong> page, click the name of the backend server group.</li><li id="elb_ug_hd3_0004_03__en-us_topic_0000001456696289_li35731251105414">Switch to the <strong id="elb_ug_hd3_0004_03__b88561114102018">Backend Servers</strong> tab and click <strong id="elb_ug_hd3_0004_03__b1985761410200">Add</strong> in the <strong id="elb_ug_hd3_0004_03__b285713146205">IP as Backend Servers</strong> area.</li><li id="elb_ug_hd3_0004_03__en-us_topic_0000001456696289_li574554155515">Specify the IP addresses, ports, and weights for the backend servers.</li><li id="elb_ug_hd3_0004_03__li11692133611294">Click <strong id="elb_ug_hd3_0004_03__b797038824577">OK</strong>.</li></ol>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
<div>
|
||||||
|
<div class="familylinks">
|
||||||
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="elb_ug_hd3_0004.html">IP Addresses as Backend Servers</a></div>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
|
14
docs/elb/umn/elb_ug_hd3_0004_04.html
Normal file
14
docs/elb/umn/elb_ug_hd3_0004_04.html
Normal file
@ -0,0 +1,14 @@
|
|||||||
|
<a name="elb_ug_hd3_0004_04"></a><a name="elb_ug_hd3_0004_04"></a>
|
||||||
|
|
||||||
|
<h1 class="topictitle1">Viewing Backend Servers</h1>
|
||||||
|
<div id="body8662426"><div class="section" id="elb_ug_hd3_0004_04__en-us_topic_0000001391415728_section14244134475711"><h4 class="sectiontitle">Scenario</h4><p id="elb_ug_hd3_0004_04__en-us_topic_0000001391415728_p1063653152314">You can view backend servers added to a backend server group, including their IP addresses, health check results, weights, and ports.</p>
|
||||||
|
</div>
|
||||||
|
<div class="section" id="elb_ug_hd3_0004_04__en-us_topic_0000001391415728_section191162211126"><h4 class="sectiontitle">Procedure</h4><ol id="elb_ug_hd3_0004_04__en-us_topic_0000001391415728_ol14514133043212"><li id="elb_ug_hd3_0004_04__en-us_topic_0000001391415728_li195153301329">Log in to the management console.</li><li id="elb_ug_hd3_0004_04__en-us_topic_0000001391415728_li149716294347">In the upper left corner of the page, click <span><img id="elb_ug_hd3_0004_04__image7656203981318" src="en-us_image_0000001747739624.png"></span> and select the desired region and project.</li><li id="elb_ug_hd3_0004_04__en-us_topic_0000001391415728_li1141022273516">Click <span><img id="elb_ug_hd3_0004_04__image159295653291635" src="en-us_image_0000001794660485.png"></span> in the upper left corner to display <strong id="elb_ug_hd3_0004_04__b172988657791635">Service List</strong> and choose <strong id="elb_ug_hd3_0004_04__b145890014191635">Network</strong> > <strong id="elb_ug_hd3_0004_04__b109937434791635">Elastic Load Balancing</strong>.</li><li id="elb_ug_hd3_0004_04__en-us_topic_0000001456696289_li20553057761">In the navigation pane on the left, choose <strong id="elb_ug_hd3_0004_04__b130339423791645">Elastic Load Balancing</strong> > <strong id="elb_ug_hd3_0004_04__b63880864991645">Backend Server Groups</strong>.</li><li id="elb_ug_hd3_0004_04__en-us_topic_0000001391415728_li0670204023612">On the <strong id="elb_ug_hd3_0004_04__b1186454712204">Backend Server Groups</strong> page, click the name of the backend server group.</li><li id="elb_ug_hd3_0004_04__en-us_topic_0000001391415728_li35731251105414">Switch to the <strong id="elb_ug_hd3_0004_04__b1438419524200">Backend Servers</strong> tab and click <strong id="elb_ug_hd3_0004_04__b12384452182015">IP as Backend Servers</strong>.</li><li id="elb_ug_hd3_0004_04__en-us_topic_0000001391415728_li889585223011">In the backend server list, view the added backend servers.</li></ol>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
<div>
|
||||||
|
<div class="familylinks">
|
||||||
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="elb_ug_hd3_0004.html">IP Addresses as Backend Servers</a></div>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
|
14
docs/elb/umn/elb_ug_hd3_0004_05.html
Normal file
14
docs/elb/umn/elb_ug_hd3_0004_05.html
Normal file
@ -0,0 +1,14 @@
|
|||||||
|
<a name="elb_ug_hd3_0004_05"></a><a name="elb_ug_hd3_0004_05"></a>
|
||||||
|
|
||||||
|
<h1 class="topictitle1">Removing Backend Servers</h1>
|
||||||
|
<div id="body8662426"><div class="section" id="elb_ug_hd3_0004_05__en-us_topic_0000001389179464_section5686131235412"><h4 class="sectiontitle">Scenario</h4><p id="elb_ug_hd3_0004_05__en-us_topic_0000001389179464_p1366417203238">You can remove backend servers from a backend server group when you do not need them to process requests.</p>
|
||||||
|
</div>
|
||||||
|
<div class="section" id="elb_ug_hd3_0004_05__en-us_topic_0000001389179464_section186206220549"><h4 class="sectiontitle">Procedure</h4><ol id="elb_ug_hd3_0004_05__en-us_topic_0000001389179464_ol14514133043212"><li id="elb_ug_hd3_0004_05__en-us_topic_0000001389179464_li195153301329">Log in to the management console.</li><li id="elb_ug_hd3_0004_05__en-us_topic_0000001389179464_li149716294347">In the upper left corner of the page, click <span><img id="elb_ug_hd3_0004_05__image184146617281318" src="en-us_image_0000001747739624.png"></span> and select the desired region and project.</li><li id="elb_ug_hd3_0004_05__en-us_topic_0000001389179464_li1141022273516">Click <span><img id="elb_ug_hd3_0004_05__image78864445691636" src="en-us_image_0000001794660485.png"></span> in the upper left corner to display <strong id="elb_ug_hd3_0004_05__b118990846691636">Service List</strong> and choose <strong id="elb_ug_hd3_0004_05__b107306124491636">Network</strong> > <strong id="elb_ug_hd3_0004_05__b202225123191636">Elastic Load Balancing</strong>.</li><li id="elb_ug_hd3_0004_05__en-us_topic_0000001456696289_li20553057761">In the navigation pane on the left, choose <strong id="elb_ug_hd3_0004_05__b202145504691645">Elastic Load Balancing</strong> > <strong id="elb_ug_hd3_0004_05__b29917237591645">Backend Server Groups</strong>.</li><li id="elb_ug_hd3_0004_05__en-us_topic_0000001389179464_li0670204023612">On the <strong id="elb_ug_hd3_0004_05__b1120273112211">Backend Server Groups</strong> page, click the name of the backend server group. </li><li id="elb_ug_hd3_0004_05__en-us_topic_0000001389179464_li1638414174311">Switch to the <strong id="elb_ug_hd3_0004_05__b374592153102057">Backend Servers</strong> tab and click <strong id="elb_ug_hd3_0004_05__b62053976102057">IP as Backend Servers</strong>.</li><li id="elb_ug_hd3_0004_05__en-us_topic_0000001389179464_li583573145517">Select the backend servers you want to remove and click <strong id="elb_ug_hd3_0004_05__b1158718438398">Remove</strong> above the backend server list.</li><li id="elb_ug_hd3_0004_05__en-us_topic_0000001389179464_li128181118115416">In the displayed dialog box, click <strong id="elb_ug_hd3_0004_05__b80213226792459">Yes</strong>.</li></ol>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
<div>
|
||||||
|
<div class="familylinks">
|
||||||
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="elb_ug_hd3_0004.html">IP Addresses as Backend Servers</a></div>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
|
20
docs/elb/umn/elb_ug_hd3_0004_06.html
Normal file
20
docs/elb/umn/elb_ug_hd3_0004_06.html
Normal file
@ -0,0 +1,20 @@
|
|||||||
|
<a name="elb_ug_hd3_0004_06"></a><a name="elb_ug_hd3_0004_06"></a>
|
||||||
|
|
||||||
|
<h1 class="topictitle1">Changing Backend Server Weights</h1>
|
||||||
|
<div id="body8662426"><div class="section" id="elb_ug_hd3_0004_06__en-us_topic_0000001392237328_section086912533919"><h4 class="sectiontitle">Scenario</h4><p id="elb_ug_hd3_0004_06__en-us_topic_0000001392237328_p39911321134014">You can change the weights specified for backend servers based on their capability to process requests.</p>
|
||||||
|
</div>
|
||||||
|
<div class="section" id="elb_ug_hd3_0004_06__section42061031115016"><h4 class="sectiontitle">Constraints and Limitations</h4><ul id="elb_ug_hd3_0004_06__en-us_topic_0000001420979186_en-us_topic_0000001391917484_ul56361441103419"><li id="elb_ug_hd3_0004_06__en-us_topic_0000001420979186_en-us_topic_0000001391917484_li26362413343">The weight ranges from <strong id="elb_ug_hd3_0004_06__b206584538174833">0</strong> to <strong id="elb_ug_hd3_0004_06__b1878924274833">100</strong>. If you set the weight of a backend server to <strong id="elb_ug_hd3_0004_06__b177478040874833">0</strong>, new requests will not be routed to this server.</li><li id="elb_ug_hd3_0004_06__en-us_topic_0000001420979186_en-us_topic_0000001391917484_li998444416345">The weights can only be specified when you select weighted round robin, weighted least connections, or source IP hash as the load balancing algorithm. For more information about load balancing algorithms, see <a href="elb_ug_hd3_0001.html#elb_ug_hd3_0001__en-us_topic_0000001384422734_section84064491587">Backend Server Weights</a>.</li></ul>
|
||||||
|
</div>
|
||||||
|
<div class="section" id="elb_ug_hd3_0004_06__en-us_topic_0000001392237328_section19705195724010"><h4 class="sectiontitle">Procedure</h4><ol id="elb_ug_hd3_0004_06__en-us_topic_0000001392237328_en-us_topic_0117477001_ol153371524105415"><li id="elb_ug_hd3_0004_06__en-us_topic_0000001392237328_li677391520332">Log in to the management console.</li><li id="elb_ug_hd3_0004_06__en-us_topic_0000001392237328_li675519100420">In the upper left corner of the page, click <span><img id="elb_ug_hd3_0004_06__image209690805381319" src="en-us_image_0000001747739624.png"></span> and select the desired region and project.</li><li id="elb_ug_hd3_0004_06__en-us_topic_0000001392237328_li83736197297">Click <span><img id="elb_ug_hd3_0004_06__image7112957991637" src="en-us_image_0000001794660485.png"></span> in the upper left corner to display <strong id="elb_ug_hd3_0004_06__b49157292391637">Service List</strong> and choose <strong id="elb_ug_hd3_0004_06__b112784579491637">Network</strong> > <strong id="elb_ug_hd3_0004_06__b106585348791637">Elastic Load Balancing</strong>.</li><li id="elb_ug_hd3_0004_06__en-us_topic_0000001456696289_li20553057761">In the navigation pane on the left, choose <strong id="elb_ug_hd3_0004_06__b199362023291646">Elastic Load Balancing</strong> > <strong id="elb_ug_hd3_0004_06__b96606783891646">Backend Server Groups</strong>.</li><li id="elb_ug_hd3_0004_06__en-us_topic_0000001392237328_en-us_topic_0117477001_li1133822465414">On the <strong id="elb_ug_hd3_0004_06__b1794653216248">Backend Server Groups</strong> page, click the name of the backend server group.</li><li id="elb_ug_hd3_0004_06__en-us_topic_0000001392237328_li9497198183116">Switch to the <strong id="elb_ug_hd3_0004_06__b42599361241">Backend Servers</strong> tab and click <strong id="elb_ug_hd3_0004_06__b18260183632417">IP as Backend Servers</strong>.</li><li id="elb_ug_hd3_0004_06__li17987104142817">Select the backend servers and click <strong id="elb_ug_hd3_0004_06__b06824401245">Modify Port/Weight</strong> above the backend server list.</li><li id="elb_ug_hd3_0004_06__en-us_topic_0000001392237328_li151816716194">In the displayed dialog box, modify weights as you need.<ul id="elb_ug_hd3_0004_06__ul1369416452316"><li id="elb_ug_hd3_0004_06__li203941035183314">Changing weights:<ul id="elb_ug_hd3_0004_06__ul14989991913"><li id="elb_ug_hd3_0004_06__li1622714565336">Changing the weight of a single backend server: Set the weight in the <strong id="elb_ug_hd3_0004_06__b121282202992644">Weight</strong> column.</li><li id="elb_ug_hd3_0004_06__li20177172893412">Changing the weights of multiple backend servers: Set the weight next to <strong id="elb_ug_hd3_0004_06__b44265718092645">Batch Modify Weights</strong> and click <strong id="elb_ug_hd3_0004_06__b15116045792645">OK</strong>.</li></ul>
|
||||||
|
<div class="note" id="elb_ug_hd3_0004_06__note917792819344"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="elb_ug_hd3_0004_06__p19177162843413">You can change the weights of multiple backend servers to <strong id="elb_ug_hd3_0004_06__b96346835492651">0</strong> so they will not receive requests from the load balancer.</p>
|
||||||
|
</div></div>
|
||||||
|
</li></ul>
|
||||||
|
</li><li id="elb_ug_hd3_0004_06__li940935754114">Click <strong id="elb_ug_hd3_0004_06__b869913317570">OK</strong>.</li></ol>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
<div>
|
||||||
|
<div class="familylinks">
|
||||||
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="elb_ug_hd3_0004.html">IP Addresses as Backend Servers</a></div>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
|
@ -1,27 +0,0 @@
|
|||||||
<a name="elb_ug_hd_0000"></a><a name="elb_ug_hd_0000"></a>
|
|
||||||
|
|
||||||
<h1 class="topictitle1">Backend Server</h1>
|
|
||||||
<div id="body1554880414452"></div>
|
|
||||||
<div>
|
|
||||||
<ul class="ullinks">
|
|
||||||
<li class="ulchildlink"><strong><a href="elb_ug_hd_0001.html">Overview</a></strong><br>
|
|
||||||
</li>
|
|
||||||
<li class="ulchildlink"><strong><a href="elb_ug_hd_0007.html">Configuring Security Group Rules for Backend Servers (Dedicated Load Balancers)</a></strong><br>
|
|
||||||
</li>
|
|
||||||
<li class="ulchildlink"><strong><a href="elb_ug_hd_0002.html">Configuring Security Group Rules for Backend Servers (Shared Load Balancers)</a></strong><br>
|
|
||||||
</li>
|
|
||||||
<li class="ulchildlink"><strong><a href="elb_ug_hd_0003.html">Adding or Removing Backend Servers (Dedicated Load Balancers)</a></strong><br>
|
|
||||||
</li>
|
|
||||||
<li class="ulchildlink"><strong><a href="en-us_topic_0052569729.html">Adding or Removing Backend Servers (Shared Load Balancers)</a></strong><br>
|
|
||||||
</li>
|
|
||||||
<li class="ulchildlink"><strong><a href="elb_ug_hd_0005.html">Configuring Hybrid Load Balancing</a></strong><br>
|
|
||||||
</li>
|
|
||||||
<li class="ulchildlink"><strong><a href="elb_ug_hd_0008.html">Configuring Weights for Backend Servers</a></strong><br>
|
|
||||||
</li>
|
|
||||||
<li class="ulchildlink"><strong><a href="elb_ug_hd_0006.html">Configuring Slow Start (Dedicated Load Balancers)</a></strong><br>
|
|
||||||
</li>
|
|
||||||
<li class="ulchildlink"><strong><a href="elb_ug_hd_0004.html">Enabling Removal Protection for Backend Servers</a></strong><br>
|
|
||||||
</li>
|
|
||||||
</ul>
|
|
||||||
</div>
|
|
||||||
|
|
@ -1,30 +0,0 @@
|
|||||||
<a name="elb_ug_hd_0001"></a><a name="elb_ug_hd_0001"></a>
|
|
||||||
|
|
||||||
<h1 class="topictitle1">Overview</h1>
|
|
||||||
<div id="body1554880414455"><p id="elb_ug_hd_0001__p6397172603620">A backend server is a cloud server added to a backend <span id="elb_ug_hd_0001__text134779184156">server</span> group associated with a load balancer. When you add a listener to a load balancer, you can create or select a backend <span id="elb_ug_hd_0001__text01565413152">server</span> group to receive requests from the load balancer by using the port and protocol you specify for the backend <span id="elb_ug_hd_0001__text12774182671815">server</span> group and the load balancing algorithm you select.</p>
|
|
||||||
<p id="elb_ug_hd_0001__p1426214183417">After a new server is added to the associated backend <span id="elb_ug_hd_0001__ph18409284911">server</span> group for which the health check is configured, the load balancer will check its running status. If the backend <span id="elb_ug_hd_0001__ph116211646174912">server</span> responds normally, it is declared healthy. If the backend <span id="elb_ug_hd_0001__ph1589916341298">server</span> does not respond normally, the load balancer periodically checks its health for multiple times. Only after the backend server is considered healthy, it can receive requests from the load balancer.</p>
|
|
||||||
<p id="elb_ug_hd_0001__p9967115115312">You can adjust the number of backend servers to ensure stable and reliable service with the minimum budget. Load balancers can distribute requests across backend <span id="elb_ug_hd_0001__ph125150113503">server</span>s in different AZs to prevent SPOFs. You must ensure that at least one backend <span id="elb_ug_hd_0001__ph12220153895011">server</span> is working normally in each AZ.</p>
|
|
||||||
<p id="elb_ug_hd_0001__p698841804714">On the ELB console, you can view the load balancer that the backend server is associated with by the IP address or ID of the backend server.</p>
|
|
||||||
<p id="elb_ug_hd_0001__p20820195012131">If a backend server is stopped or restarted, connections established with the server will be disconnected, and data being transmitted over these connections will be lost. Configure the retry function on the clients to prevent data loss.</p>
|
|
||||||
<div class="section" id="elb_ug_hd_0001__section9765648163914"><h4 class="sectiontitle">Notes</h4><p id="elb_ug_hd_0001__p39801457124614">When you add backend <span id="elb_ug_hd_0001__text1464419382514">server</span>s, note the following:</p>
|
|
||||||
<ul id="elb_ug_hd_0001__ul239818617405"><li id="elb_ug_hd_0001__li73980634016">Backend servers must be in the same VPC as the load balancer if IP as a backend is not enabled.</li><li id="elb_ug_hd_0001__li183983674015">For ease of management and maintenance, backend <span id="elb_ug_hd_0001__text1487084671110">server</span>s must run the same OS.</li><li id="elb_ug_hd_0001__li1399166134017">You can set a weight for each server in the backend <span id="elb_ug_hd_0001__text8503125112613">server</span> group. The larger the weight is, the higher proportion of requests the backend <span id="elb_ug_hd_0001__text2797123062610">server</span> receives.</li><li id="elb_ug_hd_0001__li1439920620407">If you enable sticky sessions, the proportions of requests processed by backend <span id="elb_ug_hd_0001__text15786540172820">server</span>s may become unbalanced. In this case, disable sticky sessions and check the requests received by each backend server.</li></ul>
|
|
||||||
</div>
|
|
||||||
<div class="section" id="elb_ug_hd_0001__section196816516169"><h4 class="sectiontitle">Slow Start</h4><p id="elb_ug_hd_0001__en-us_topic_0236111261_en-us_topic_0164706626_p148351859155716">After you enable slow start, the load balancer linearly increases the proportion of requests to send to backend servers in this mode. When the slow start duration elapses, the load balancer sends full share of requests to backend servers and exits the slow start mode.</p>
|
|
||||||
</div>
|
|
||||||
<div class="p" id="elb_ug_hd_0001__p187471544136">When you enable slow start, note the following:<ul id="elb_ug_hd_0001__en-us_topic_0236111261_ul512118279397"><li id="elb_ug_hd_0001__en-us_topic_0236111261_li103585207417">Slow start can only be enabled for HTTP and HTTPS backend server groups.</li><li id="elb_ug_hd_0001__en-us_topic_0236111261_li576916302045">If slow start is enabled, only the weighted round robin algorithm can be used.</li><li id="elb_ug_hd_0001__en-us_topic_0236111261_li191885612382">Slow start can be enabled only for new backend servers. If a backend server group has no backend servers, slow start will not take effect for the first backend server added to the backend server group.</li><li id="elb_ug_hd_0001__en-us_topic_0236111261_li5449663391">When the health check function is enabled, slow start takes effect after backend servers are detected healthy. The slow start duration will not stop even if the health check is abnormal due to network exceptions or other reasons.</li><li id="elb_ug_hd_0001__en-us_topic_0236111261_li19788110396">When the health check function is disabled, slow start takes effect immediately.</li><li id="elb_ug_hd_0001__en-us_topic_0236111261_li1856810328391">After the slow start duration elapses, backend servers will not enter the slow start mode again.</li></ul>
|
|
||||||
</div>
|
|
||||||
<div class="note" id="elb_ug_hd_0001__note01614312493"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="elb_ug_hd_0001__p1716115315493">The slow start function applies only to dedicated load balancers.</p>
|
|
||||||
</div></div>
|
|
||||||
<div class="section" id="elb_ug_hd_0001__section201861524101718"><h4 class="sectiontitle">IP as Backend Servers</h4><p id="elb_ug_hd_0001__en-us_topic_0236111261_p1326872512913">If you enable the IP as a Backend feature, in addition to ECSs and BMSs, you can also add IP as backend servers that are NOT in the VPC of the load balancer. The backend servers can be in a VPC connected through a VPC peering connection, or in an on-premises data center at the other end of a Direct Connect or VPN connection.</p>
|
|
||||||
<div class="p" id="elb_ug_hd_0001__p4240181011357">When you add IP as backend servers, note the following:<ul id="elb_ug_hd_0001__ul1124091083511"><li id="elb_ug_hd_0001__li224018103355">If you do not enable the function when you create a load balancer, you can still enable it on the <strong id="elb_ug_hd_0001__b12229759123016">Summary</strong> page of the load balancer.</li><li id="elb_ug_hd_0001__li72401109355">Only IPv4 addresses can be added as backend servers.</li><li id="elb_ug_hd_0001__li6240610193517">Configure the VPC routes correctly to ensure that backend servers are reachable. For details, see <a href="elb_ug_hd_0003.html">Adding or Removing Backend Servers (Dedicated Load Balancers)</a>.</li><li id="elb_ug_hd_0001__li16240210173513">If you enable IP as a backend for a load balancer, you can add only TCP, HTTP, and HTTPS listeners to the load balancer.</li><li id="elb_ug_hd_0001__li9240201010354">The subnet where the load balancer works must have sufficient IP addresses (at least 16 IP addresses). You can add more subnets for more IP addresses on the <strong id="elb_ug_hd_0001__b3259172819326">Summary</strong> page of the load balancer.</li><li id="elb_ug_hd_0001__li9240810163510">Security group rules of IP as backend servers must allow traffic from the subnet of the load balancer. Otherwise, health checks will fail.</li><li id="elb_ug_hd_0001__li6240810153514">IP as backend cannot be disabled after it is enabled.</li><li id="elb_ug_hd_0001__li112411310143517">A maximum of 492 servers can be associated with a load balancer.</li><li id="elb_ug_hd_0001__li479093210352">Source IP addresses of the clients cannot be passed to IP as backend servers. </li></ul>
|
|
||||||
</div>
|
|
||||||
<div class="note" id="elb_ug_hd_0001__note1630361504"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="elb_ug_hd_0001__p1463012614507">The IP as a backend function applies only to dedicated load balancers.</p>
|
|
||||||
</div></div>
|
|
||||||
</div>
|
|
||||||
</div>
|
|
||||||
<div>
|
|
||||||
<div class="familylinks">
|
|
||||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="elb_ug_hd_0000.html">Backend Server</a></div>
|
|
||||||
</div>
|
|
||||||
</div>
|
|
||||||
|
|
File diff suppressed because it is too large
Load Diff
File diff suppressed because it is too large
Load Diff
@ -1,16 +1,16 @@
|
|||||||
<a name="elb_ug_hd_0004"></a><a name="elb_ug_hd_0004"></a>
|
<a name="elb_ug_hd_0004"></a><a name="elb_ug_hd_0004"></a>
|
||||||
|
|
||||||
<h1 class="topictitle1">Enabling Removal Protection for Backend Servers</h1>
|
<h1 class="topictitle1">Enabling Removal Protection for a Backend Server Group</h1>
|
||||||
<div id="body8662426"><div class="section" id="elb_ug_hd_0004__en-us_topic_0000001124594383_section1063251192613"><h4 class="sectiontitle">Scenarios</h4><p id="elb_ug_hd_0004__en-us_topic_0000001124594383_p1071917299262">Dedicated load balancers allow you to enable removal protection for associated backend servers to prevent them from being removed by accident.</p>
|
<div id="body8662426"><div class="section" id="elb_ug_hd_0004__en-us_topic_0000001124594383_section1063251192613"><h4 class="sectiontitle">Scenarios</h4><p id="elb_ug_hd_0004__en-us_topic_0000001124594383_p1071917299262">Dedicated load balancers allow you to enable the removal protection option for a backend server group to prevent the servers in it from being removed by accident.</p>
|
||||||
</div>
|
</div>
|
||||||
<div class="section" id="elb_ug_hd_0004__en-us_topic_0000001124594383_section199829311277"><h4 class="sectiontitle">Procedure</h4><ol id="elb_ug_hd_0004__en-us_topic_0000001124594383_ol7973192482819"><li id="elb_ug_hd_0004__en-us_topic_0000001124594383_li677391520332">Log in to the management console.</li><li id="elb_ug_hd_0004__en-us_topic_0000001124594383_li675519100420">In the upper left corner of the page, click <span><img id="elb_ug_hd_0004__en-us_topic_0240829509_image1542118117117" src="en-us_image_0000001747739624.png"></span> and select the desired region and project.</li><li id="elb_ug_hd_0004__li59941052152319">Hover on <span><img id="elb_ug_hd_0004__en-us_topic_0167652100_image762510132322" src="en-us_image_0000001794660485.png"></span> in the upper left corner to display <strong id="elb_ug_hd_0004__en-us_topic_0167652100_b9121102522212">Service List</strong> and choose <strong id="elb_ug_hd_0004__en-us_topic_0167652100_b61222025142217">Network</strong> > <strong id="elb_ug_hd_0004__en-us_topic_0167652100_b4124425142210">Elastic Load Balancing</strong>. </li><li id="elb_ug_hd_0004__en-us_topic_0000001124594383_li786163214298">On the <strong id="elb_ug_hd_0004__en-us_topic_0000001124594383_b434181818314">Load Balancers</strong> page, locate the load balancer and click its name.</li><li id="elb_ug_hd_0004__en-us_topic_0000001124594383_li2831329135812">Click <strong id="elb_ug_hd_0004__en-us_topic_0000001124594383_b11374201693211">Backend Server Groups</strong>, locate the backend server group, and click its name.</li><li id="elb_ug_hd_0004__en-us_topic_0000001124594383_li662115566309">In the <strong id="elb_ug_hd_0004__b8559841441">Basic Information</strong> area on the right, enable <strong id="elb_ug_hd_0004__b9560141442">Removal Protection</strong>.</li></ol>
|
<div class="section" id="elb_ug_hd_0004__en-us_topic_0000001124594383_section199829311277"><h4 class="sectiontitle">Procedure</h4><ol id="elb_ug_hd_0004__en-us_topic_0000001124594383_ol7973192482819"><li id="elb_ug_hd_0004__en-us_topic_0000001124594383_li677391520332">Log in to the management console.</li><li id="elb_ug_hd_0004__en-us_topic_0000001124594383_li675519100420">In the upper left corner of the page, click <span><img id="elb_ug_hd_0004__image42721748172815" src="en-us_image_0000001747739624.png"></span> and select the desired region and project.</li><li id="elb_ug_hd_0004__li59941052152319">Click <span><img id="elb_ug_hd_0004__image31713519285" src="en-us_image_0000001794660485.png"></span> in the upper left corner to display <strong id="elb_ug_hd_0004__b9171151132813">Service List</strong> and choose <strong id="elb_ug_hd_0004__b1519205162810">Network</strong> > <strong id="elb_ug_hd_0004__b32018516287">Elastic Load Balancing</strong>.</li><li id="elb_ug_hd_0004__en-us_topic_0000001124594383_li786163214298">On the <strong id="elb_ug_hd_0004__en-us_topic_0000001124594383_b434181818314">Load Balancers</strong> page, locate the load balancer and click its name.</li><li id="elb_ug_hd_0004__li45162719114">On the <strong id="elb_ug_hd_0004__b1834924244610">Listeners</strong> tab, locate the target listener. In the <strong id="elb_ug_hd_0004__b1535011423463">Default Backend Server Group</strong> column, click <strong id="elb_ug_hd_0004__b035110428468">View/Add Backend Server</strong>.</li><li id="elb_ug_hd_0004__li186192421315">Click the <strong id="elb_ug_hd_0004__b1835117243519">Summary</strong> tab and enable <strong id="elb_ug_hd_0004__b390417393513">Removal Protection</strong>.</li></ol>
|
||||||
<div class="note" id="elb_ug_hd_0004__en-us_topic_0000001124594383_note8738203063713"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="elb_ug_hd_0004__en-us_topic_0000001124594383_p2738143013716">Disable <strong id="elb_ug_hd_0004__en-us_topic_0000001124594383_b153075183311">Removal Protection</strong> if you want to delete a backend server group or remove a cloud server or an IP address from the backend server group.</p>
|
<div class="note" id="elb_ug_hd_0004__en-us_topic_0000001124594383_note8738203063713"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="elb_ug_hd_0004__en-us_topic_0000001124594383_p2738143013716">Disable <strong id="elb_ug_hd_0004__en-us_topic_0000001124594383_b153075183311">Removal Protection</strong> if you want to delete a backend server group or remove a cloud server or an IP address from the backend server group.</p>
|
||||||
</div></div>
|
</div></div>
|
||||||
</div>
|
</div>
|
||||||
</div>
|
</div>
|
||||||
<div>
|
<div>
|
||||||
<div class="familylinks">
|
<div class="familylinks">
|
||||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="elb_ug_hd_0000.html">Backend Server</a></div>
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="elb_ug_hdg_0000.html">Backend Server Group</a></div>
|
||||||
</div>
|
</div>
|
||||||
</div>
|
</div>
|
||||||
|
|
||||||
|
Some files were not shown because too many files have changed in this diff Show More
Loading…
x
Reference in New Issue
Block a user