Basic overall flow of the settings

This section describes the basic flow for setting Managed Load Balancer.

< Overall flow chart >

transition_of_status

Create a Managed Load Balancer:from Create to Deploy

The procedure for creating a new one is as follows.

  • "Create" a Managed Load Blancer. At this stage, the Managed Load Balancer has not been configured with device connections or policies for the customer's network.

  • "Add" the settings according to the customer's environment. Each added setting (policy, health monitor, etc.) will initially put it in a state of "Waiting for Change Setting".

  • By executing "Deploy" of Managed Load Balancer instance, Managed Load Balancer instance is actually created and the settings are applied.

ManagedLB_flow-create
  1. Create a Managed Load Balancer instance and connect to your logical network.

  2. Add settings.

    1. Network settings (Add if it is needed)

      1. Connect your Managed Load Balancer instance to your logical network.
      2. Configure static routes for Managed Load Balancer.

    2. Load balancing settings

      < When protocol is L4(TCP/UDP)>

      1. Configure the function to periodically monitor the failure of the load balancing target (real server).
      2. Configure the function to check connection requests to the Managed Load Balancer using the specified IP address, port number, and protocol.
      3. Configure the grouping function of the load balancing target (real server) of Managed Load Balancer.
      4. In the policy setting, associate the health monitor and target group with the listener, and configure the algorithm and persistence method.
      5. How to configure Source NAT and X-Forwarded-For  (If necessary, please set.)
        Enable the Source NAT function that translates the IP address when communicating from the target of load balancing to the outside.

      < When protocol is HTTP >

      1. Configure the function to periodically monitor the failure of the load balancing target (real server).
      2. Configure the function to check connection requests to the Managed Load Balancer using the specified IP address, port number, and protocol.
      3. Configure the grouping function of the load balancing target (real server) of Managed Load Balancer.
      4. In the policy setting, associate the health monitor and target group with the listener, and configure the algorithm and persistence method.
        If you want to redirect to the sorry page, set it here.
        Set the transfer destination path in the setting of rule.
      5. How to configure Source NAT and X-Forwarded-For  (If necessary, please set.)
        Enable the Source NAT function that translates the IP address when communicating from the target of load balancing to the outside.
        (For http/https, X-Forwarded-For is automatically added when the Source NAT function is enabled.)

      < When protocol is HTTPS >

      1. Configure the function to periodically monitor the failure of the load balancing target (real server).
      2. Configure the function to check connection requests to the Managed Load Balancer using the specified IP address, port number, and protocol.
      3. Configure the grouping function of the load balancing target (real server) of Managed Load Balancer.
      4. Upload your SSL certificate.
      5. In the policy setting, associate the health monitor and target group with the listener, and select the algorithm, persistence method, SSL certificate, and TLS policy.
        If you want to redirect to the sorry page, set it here.
        Set the transfer destination path in the setting of rule.
      6. How to configure Source NAT and X-Forwarded-For  (If necessary, please set.)
        Enable the Source NAT function that translates the IP address when communicating from the target of load balancing to the outside.
        (For http/https, X-Forwarded-For is automatically added when the Source NAT function is enabled.)

  3. Apply the settings added in 2 to the Managed Load Balancer instance and deploy it.
    Billing starts when construction is completed.

Note

It is not possible to "Deploy" only with the network settings. Please "Deploy" after adding load balancing settings.


Change Managed Load Balancer settings:from Edit to Apply

The procedure for changing the settings is as follows.

  • When you edit each function, a new configuration file is created as a "Waiting for Change Setting".

  • Apply them all to the Managed Load Balancer instance.

While waiting for changes, the status of each function will be "UPDATE_STAGED" or "DELETE_STAGED", however the status of the Managed Load Balancer itself will remain "Active".

transition_of_status_2
  1. Execute the below item for which you want to change the settings.
  1. Apply the settings edited in 1 to the Managed Load Balancer instance.

Note

It may take several minutes to ten minutes to apply. For the impact on communication by applying the settings, chesk "Switching Managed Load Balancer instances for configuration changes and failure recovery" and "Synchronization specification".


Cancel the changes of settings before they are applied.

"Waiting for Change Setting" can be canceled before they are applied.


Update SSL certificate

When updating the SSL certificate, you can update it by uploading the additional SSL certificate in advance and changing the linkage to the policy.

  1. Add a set of certificates in addition to the ones you have been using so far.
  2. Edit policy settings and rule settings. On the policy screen, change the name of the newly added SSL certificate.
  3. Apply the settings edited in 2 to the Managed Load Balancer instance.

Note

It may take several minutes to ten minutes to apply. For the impact on communication by applying the settings, chesk "Switching Managed Load Balancer instances for configuration changes and failure recovery" and "Synchronization specification".


Delete Managed Load Balancer

Delete Managed Load Balancers. (Once deleted, it cannot be recovered.)