Versions Compared

Old Version 42

changes.mady.by.user Sarabjeet Kaur

Saved on

compared with

New Version Current

changes.mady.by.user Sarabjeet Kaur

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

From Kyvos 2024.2 onwards, the Load Balancer entry for the Marketplace has been automated for AWS and Azure. However, for Kyvos Enterprise and GCP Marketplace, you still need to perform manual steps for Load Balancer Entry.
If the automation fails to manage the load balancer entry for any reason, you need to perform the manual steps mentioned in this section.

Panel
panelIconIdatlassian-note
panelIcon:note:
bgColor#DEEBFF

Note

  • When the application is able to identify the Load Balancer details, the inputs will be auto-populated and non-editable. However, if the application is unable to identify Load Balancer details, you must add the details manually, which is a one-time activity.

  • For the GCP Marketplace, if a Load Balancer was not created during deployment, Kyvos Manager will prompt for Load Balancer details if one has already been configured manually, to facilitate further automation.

This section describes the Load Configuration manual steps for:

...

For cloud environments where Load Balancer is used, after adding the Kyvos Manager service, you need to remove add the entry of Kyvos Manager nodes in the:

...

For GCP, you

  1. You must configure Load Balancer

. To do this, refer to the Configuring External Load Balancer for GCP section

  1. as a prerequisite.

  2. Go the Instance Group used in Load Balancer.

  3. Edit the Instance Group.

  4. From the VM Instances list, select the VMs on which you want to use this backend service.

  5. In the Port Mapping area, click Add Port.

    1. Port name as km-https and Port number as 9443 (TLS). For non-TLS ports, use 8080.

      image-20240125-132312.pngImage Modified

  6. Click Save.

Aura tab collection
paramsJTdCJTIyZ2VuZXJhbCUyMiUzQSU3QiUyMnRhYlNwYWNpbmclMjIlM0EwJTJDJTIydGFiV2lkdGglMjIlM0ExMDAlMkMlMjJ0YWJIZWlnaHQlMjIlM0E1MCUyQyUyMmRpcmVjdGlvbiUyMiUzQSUyMmhvcml6b250YWwlMjIlN0QlMkMlMjJjb250ZW50JTIyJTNBJTdCJTIyYmFja2dyb3VuZENvbG9yJTIyJTNBJTdCJTIyY29sb3IlMjIlM0ElMjIlMjNmZmYlMjIlN0QlMkMlMjJib3JkZXIlMjIlM0ElN0IlMjJzdHlsZSUyMiUzQSUyMnNvbGlkJTIyJTJDJTIyd2lkdGglMjIlM0ExJTJDJTIydG9wJTIyJTNBdHJ1ZSUyQyUyMmJvdHRvbSUyMiUzQXRydWUlMkMlMjJsZWZ0JTIyJTNBdHJ1ZSUyQyUyMnJpZ2h0JTIyJTNBdHJ1ZSUyQyUyMmNvbG9yJTIyJTNBJTdCJTIybGlnaHQlMjIlM0ElMjIlMjNjY2NlY2YlMjIlN0QlN0QlMkMlMjJwYWRkaW5nJTIyJTNBJTdCJTIydG9wJTIyJTNBMTAlMkMlMjJyaWdodCUyMiUzQTEwJTJDJTIyYm90dG9tJTIyJTNBMTAlMkMlMjJsZWZ0JTIyJTNBMTAlN0QlN0QlMkMlMjJhY3RpdmUlMjIlM0ElN0IlMjJiYWNrZ3JvdW5kQ29sb3IlMjIlM0ElN0IlMjJjb2xvciUyMiUzQSU3QiUyMmxpZ2h0JTIyJTNBJTIyJTIzZjU4MjI3JTIyJTdEJTdEJTJDJTIydGV4dCUyMiUzQSU3QiUyMmZvbnRTaXplJTIyJTNBMTYlMkMlMjJjb2xvciUyMiUzQSU3QiUyMmxpZ2h0JTIyJTNBJTIyJTIzMDAwMDAwJTIyJTdEJTJDJTIydGV4dEFsaWduJTIyJTNBJTIybGVmdCUyMiUyQyUyMmZvbnRXZWlnaHQlMjIlM0ElMjJib2xkJTIyJTdEJTdEJTJDJTIyaG92ZXIlMjIlM0ElN0IlMjJiYWNrZ3JvdW5kQ29sb3IlMjIlM0ElN0IlMjJjb2xvciUyMiUzQSUyMiUyM2RmZTFlNiUyMiU3RCUyQyUyMnRleHQlMjIlM0ElN0IlMjJmb250U2l6ZSUyMiUzQTE4JTJDJTIyY29sb3IlMjIlM0ElMjIlMjM1ZTZjODQlMjIlMkMlMjJ0ZXh0QWxpZ24lMjIlM0ElMjJsZWZ0JTIyJTJDJTIyZm9udFdlaWdodCUyMiUzQSUyMmxpZ2h0ZXIlMjIlN0QlN0QlMkMlMjJpbmFjdGl2ZSUyMiUzQSU3QiUyMmJhY2tncm91bmRDb2xvciUyMiUzQSU3QiUyMmNvbG9yJTIyJTNBJTIyJTIzZjRmNWY3JTIyJTdEJTJDJTIydGV4dCUyMiUzQSU3QiUyMmZvbnRTaXplJTIyJTNBMTYlMkMlMjJjb2xvciUyMiUzQSUyMiUyMzVlNmM4NCUyMiUyQyUyMnRleHRBbGlnbiUyMiUzQSUyMmxlZnQlMjIlMkMlMjJmb250V2VpZ2h0JTIyJTNBJTIybGlnaHRlciUyMiU3RCUyQyUyMmJvcmRlciUyMiUzQSU3QiUyMnRvcCUyMiUzQXRydWUlMkMlMjJsZWZ0JTIyJTNBdHJ1ZSUyQyUyMnJpZ2h0JTIyJTNBdHJ1ZSUyQyUyMmJvdHRvbSUyMiUzQXRydWUlMkMlMjJ3aWR0aCUyMiUzQTElMkMlMjJzdHlsZSUyMiUzQSUyMnNvbGlkJTIyJTJDJTIyY29sb3IlMjIlM0ElN0IlMjJsaWdodCUyMiUzQSUyMiUyM2NjY2VjZiUyMiU3RCU3RCU3RCU3RA==
Aura tab
summaryAWS
paramsJTdCJTIydGl0bGUlMjIlM0ElMjJBV1MlMjIlN0Q=

  1. Open the AWS console.

  2. Locate the target group associated with the load balancer used. This can be done in two ways, depending on the scenario.

    1. Case 1: When the stack is used for deployment, and the Load Balancer is created as a part of it, In this case, perform the following steps.

      1. Navigate to CloudFormation > Stacks > <STACK-NAME>

      2. Click the Resources tab.

      3. Search for KyvosManagerAlbTargetGroup, and then click it.

      4. In the Resources section, do the following:

        1. Click the link in the Physical ID column. It will open a new tab.

        2. Click the link in the Name column.

          image-20240117-090901.png

    2. Case 2 : Go to EC2 > Target groups.
      On the Target groups page, perform the following steps.

      1. Locate your target group by name and click the target group.

      2. This will open the Target Group details page.

      3. On the page, verify it by checking the value displays for Load balancer.

        image-20240109-164454.png

  3. Click the Health checks tab in the Target group details section.

  4. Click Edit.

  5. Under Health check path, change the health check path to /kyvosmanager/kmha/activeKyvosManagerInstance

  6. Click Save changes. The Health check changes are saved now.

  7. Click on the Targets tab in the Target group details section.

    image-20240119-082059.png

  8. Click Register targets.

  9. Select the newly added Kyvos Manager instance ID from Instance ID column under Available instances.

  10. Enter the required port under Ports for the selected instances.

  11. Click Include as pending below. It will show the added instance under the Review targets section.

  12. Click Register pending targets. It will register the pending targets to the Target group.

Aura tab
summaryAzure
paramsJTdCJTIydGl0bGUlMjIlM0ElMjJBenVyZSUyMiU3RA==

  1. Open Azure console.

  2. Go to Deployment in the Settings section.

  3. Click the deployment.

  4. Expand the Deployment details section.

  5. Search for Application gateway.

    image-20240117-081748.png

  6. Click Application gateway resource link.

  7. Select Backend pools display in the left pane under Settings.

  8. Click KyvosManagerLoadBalancerBackEndPool.

  9. Under Backend targets Select Target type as Virtual Machine and Select newly added Kyvos Manager Virtual machine in Target.

  10. Click Save. The virtual Machine is added to the backend pool targets.

  11. Go to Health probe in the Settings section.

  12. Click KyvosManagerLoadBalancerHealthProbe.

  13. Change the path to /kyvosmanager/kmha/activeKyvosManagerInstance.

  14. Click Test

  15. After successful test, click Save.

    image-20240119-081756.png
Aura tab
summaryGCP
paramsJTdCJTIydGl0bGUlMjIlM0ElMjJHQ1AlMjIlN0Q=
Panel
panelIconIdatlassian-note
panelIcon:note:
bgColor#DEEBFF

...

  1. On the Health Checks section, change the path to /kyvosmanager/.

    image-20240419-103236.pngImage Added

  2. Click Save.

Removing Kyvos Manager nodes entry
Anchor
Remvoing
Remvoing

For cloud environments where Load Balancer is used, after removing the Kyvos Manager service, you need to remove the entry of Kyvos Manager nodes in the :

...

Aura tab collection
paramsJTdCJTIyZ2VuZXJhbCUyMiUzQSU3QiUyMnRhYlNwYWNpbmclMjIlM0EwJTJDJTIydGFiV2lkdGglMjIlM0ExMDAlMkMlMjJ0YWJIZWlnaHQlMjIlM0E1MCUyQyUyMmRpcmVjdGlvbiUyMiUzQSUyMmhvcml6b250YWwlMjIlN0QlMkMlMjJjb250ZW50JTIyJTNBJTdCJTIyYmFja2dyb3VuZENvbG9yJTIyJTNBJTdCJTIyY29sb3IlMjIlM0ElMjIlMjNmZmYlMjIlN0QlMkMlMjJib3JkZXIlMjIlM0ElN0IlMjJzdHlsZSUyMiUzQSUyMnNvbGlkJTIyJTJDJTIyd2lkdGglMjIlM0ExJTJDJTIydG9wJTIyJTNBdHJ1ZSUyQyUyMmJvdHRvbSUyMiUzQXRydWUlMkMlMjJsZWZ0JTIyJTNBdHJ1ZSUyQyUyMnJpZ2h0JTIyJTNBdHJ1ZSUyQyUyMmNvbG9yJTIyJTNBJTdCJTIybGlnaHQlMjIlM0ElMjIlMjNjY2NlY2YlMjIlN0QlN0QlMkMlMjJwYWRkaW5nJTIyJTNBJTdCJTIydG9wJTIyJTNBMTAlMkMlMjJyaWdodCUyMiUzQTEwJTJDJTIyYm90dG9tJTIyJTNBMTAlMkMlMjJsZWZ0JTIyJTNBMTAlN0QlN0QlMkMlMjJhY3RpdmUlMjIlM0ElN0IlMjJiYWNrZ3JvdW5kQ29sb3IlMjIlM0ElN0IlMjJjb2xvciUyMiUzQSU3QiUyMmxpZ2h0JTIyJTNBJTIyJTIzZjU4MjI3JTIyJTdEJTdEJTJDJTIydGV4dCUyMiUzQSU3QiUyMmZvbnRTaXplJTIyJTNBMTYlMkMlMjJjb2xvciUyMiUzQSU3QiUyMmxpZ2h0JTIyJTNBJTIyJTIzMDAwMDAwJTIyJTdEJTJDJTIydGV4dEFsaWduJTIyJTNBJTIybGVmdCUyMiUyQyUyMmZvbnRXZWlnaHQlMjIlM0ElMjJib2xkJTIyJTdEJTdEJTJDJTIyaG92ZXIlMjIlM0ElN0IlMjJiYWNrZ3JvdW5kQ29sb3IlMjIlM0ElN0IlMjJjb2xvciUyMiUzQSUyMiUyM2RmZTFlNiUyMiU3RCUyQyUyMnRleHQlMjIlM0ElN0IlMjJmb250U2l6ZSUyMiUzQTE4JTJDJTIyY29sb3IlMjIlM0ElMjIlMjM1ZTZjODQlMjIlMkMlMjJ0ZXh0QWxpZ24lMjIlM0ElMjJsZWZ0JTIyJTJDJTIyZm9udFdlaWdodCUyMiUzQSUyMmxpZ2h0ZXIlMjIlN0QlN0QlMkMlMjJpbmFjdGl2ZSUyMiUzQSU3QiUyMmJhY2tncm91bmRDb2xvciUyMiUzQSU3QiUyMmNvbG9yJTIyJTNBJTIyJTIzZjRmNWY3JTIyJTdEJTJDJTIydGV4dCUyMiUzQSU3QiUyMmZvbnRTaXplJTIyJTNBMTYlMkMlMjJjb2xvciUyMiUzQSUyMiUyMzVlNmM4NCUyMiUyQyUyMnRleHRBbGlnbiUyMiUzQSUyMmxlZnQlMjIlMkMlMjJmb250V2VpZ2h0JTIyJTNBJTIybGlnaHRlciUyMiU3RCUyQyUyMmJvcmRlciUyMiUzQSU3QiUyMnRvcCUyMiUzQXRydWUlMkMlMjJsZWZ0JTIyJTNBdHJ1ZSUyQyUyMnJpZ2h0JTIyJTNBdHJ1ZSUyQyUyMmJvdHRvbSUyMiUzQXRydWUlMkMlMjJ3aWR0aCUyMiUzQTElMkMlMjJzdHlsZSUyMiUzQSUyMnNvbGlkJTIyJTJDJTIyY29sb3IlMjIlM0ElN0IlMjJsaWdodCUyMiUzQSUyMiUyM2NjY2VjZiUyMiU3RCU3RCU3RCU3RA==
Aura tab
summaryAWS
paramsJTdCJTIydGl0bGUlMjIlM0ElMjJBV1MlMjIlN0Q=

  1. Open AWS console.

  2. Locate the target group associated with the load balancer used. This can be done in two ways, depending on the scenario.

    1. Case1: When stack is used for deployment and Load Balancer is created as a part of it.

      1. Navigate to CloudFormation > Stacks > <STACK-NAME>

      2. Click on the Resources tab.

      3. Search for KyvosManagerAlbTargetGroup.

      4. Click the link in the Physical ID column.

      5. Click the link in Name column.

    2. Case2 : Go to EC2 > Target groups.

      1. Locate your target group by name and verify it by checking the value displays for Load balancer in the Target group details page.

      2. Click the Targets tab in Target group details section.

      3. Select the instance ID to be deregistered under the Registered targets list.

        image-20240119-081554.png

      4. Click Deregister.

Aura tab
summaryAzure
paramsJTdCJTIydGl0bGUlMjIlM0ElMjJBenVyZSUyMiU3RA==

  1. Open Azure console.

  2. Go to deployment.

  3. Go to the deployment details.

  4. Search for the type Application gateway.

  5. Click Application gateway in the resource link.

  6. Go to Backend pools display in the left menu under Settings.

  7. Click KyvosManagerLoadBalancerBackEndPool.

  8. Under Backend targets, click the Delete button against the Kyvos Manager virtual machine to be removed.

  9. Click Save.

Aura tab
summaryGCP
paramsJTdCJTIydGl0bGUlMjIlM0ElMjJHQ1AlMjIlN0Q=

  1. Go Open GCP Console.

  2. In the Search bar, enter Instance Groups. A list of Instance groups is displayed.

  3. Select the Instance Group used in Load Balancer.

  4. Edit the Instance Group.

  5. Using the minus icon in the VM Instances list, you can remove the VMs that you no longer From the Select VMs list, select the VMs on which you want to use this backend service and click Ok.

  6. Go the Instance Group used in Load Balancer.

  7. Edit the Instance Group.

  8. Using the minus icon in the VM Instances list, you can remove the VMs that you no longer require for this backend service.

    image-20240125-132542.png

  9. Click Save.

...

For cloud environments where Load Balancer is used, after adding the Kyvos Manager service, you need to remove add the entry of Kyvos Manager nodes in the:

...

For GCP, you

  1. You must configure Load Balancer

. To do this, refer to the Configuring External Load Balancer for GCP section.

  1. Go the as a prerequisite.

  2. Go the Instance Group used in Load Balancer.

  3. Edit the Instance Group.

  4. From the VM Instances list, select the VMs on which you want to use this backend service. You must select the VMs used for the Kyvos Webserver node.

  5. In the Port Mapping area, click Add Port.

    • Port name as kyvos-https and Port number as 8443 (TLS) For non-TLS ports, use 8081.

      image-20240125-132312.pngImage Modified

  6. Click Save.

Aura tab collection
paramsJTdCJTIyZ2VuZXJhbCUyMiUzQSU3QiUyMnRhYlNwYWNpbmclMjIlM0EwJTJDJTIydGFiV2lkdGglMjIlM0ExMDAlMkMlMjJ0YWJIZWlnaHQlMjIlM0E1MCUyQyUyMmRpcmVjdGlvbiUyMiUzQSUyMmhvcml6b250YWwlMjIlN0QlMkMlMjJjb250ZW50JTIyJTNBJTdCJTIyYmFja2dyb3VuZENvbG9yJTIyJTNBJTdCJTIyY29sb3IlMjIlM0ElMjIlMjNmZmYlMjIlN0QlMkMlMjJib3JkZXIlMjIlM0ElN0IlMjJzdHlsZSUyMiUzQSUyMnNvbGlkJTIyJTJDJTIyd2lkdGglMjIlM0ExJTJDJTIydG9wJTIyJTNBdHJ1ZSUyQyUyMmJvdHRvbSUyMiUzQXRydWUlMkMlMjJsZWZ0JTIyJTNBdHJ1ZSUyQyUyMnJpZ2h0JTIyJTNBdHJ1ZSUyQyUyMmNvbG9yJTIyJTNBJTdCJTIybGlnaHQlMjIlM0ElMjIlMjNjY2NlY2YlMjIlN0QlN0QlMkMlMjJwYWRkaW5nJTIyJTNBJTdCJTIydG9wJTIyJTNBMTAlMkMlMjJyaWdodCUyMiUzQTEwJTJDJTIyYm90dG9tJTIyJTNBMTAlMkMlMjJsZWZ0JTIyJTNBMTAlN0QlN0QlMkMlMjJhY3RpdmUlMjIlM0ElN0IlMjJiYWNrZ3JvdW5kQ29sb3IlMjIlM0ElN0IlMjJjb2xvciUyMiUzQSU3QiUyMmxpZ2h0JTIyJTNBJTIyJTIzZjU4MjI3JTIyJTdEJTdEJTJDJTIydGV4dCUyMiUzQSU3QiUyMmZvbnRTaXplJTIyJTNBMTYlMkMlMjJjb2xvciUyMiUzQSU3QiUyMmxpZ2h0JTIyJTNBJTIyJTIzMDAwMDAwJTIyJTdEJTJDJTIydGV4dEFsaWduJTIyJTNBJTIybGVmdCUyMiUyQyUyMmZvbnRXZWlnaHQlMjIlM0ElMjJib2xkJTIyJTdEJTdEJTJDJTIyaG92ZXIlMjIlM0ElN0IlMjJiYWNrZ3JvdW5kQ29sb3IlMjIlM0ElN0IlMjJjb2xvciUyMiUzQSUyMiUyM2RmZTFlNiUyMiU3RCUyQyUyMnRleHQlMjIlM0ElN0IlMjJmb250U2l6ZSUyMiUzQTE4JTJDJTIyY29sb3IlMjIlM0ElMjIlMjM1ZTZjODQlMjIlMkMlMjJ0ZXh0QWxpZ24lMjIlM0ElMjJsZWZ0JTIyJTJDJTIyZm9udFdlaWdodCUyMiUzQSUyMmxpZ2h0ZXIlMjIlN0QlN0QlMkMlMjJpbmFjdGl2ZSUyMiUzQSU3QiUyMmJhY2tncm91bmRDb2xvciUyMiUzQSU3QiUyMmNvbG9yJTIyJTNBJTIyJTIzZjRmNWY3JTIyJTdEJTJDJTIydGV4dCUyMiUzQSU3QiUyMmZvbnRTaXplJTIyJTNBMTYlMkMlMjJjb2xvciUyMiUzQSUyMiUyMzVlNmM4NCUyMiUyQyUyMnRleHRBbGlnbiUyMiUzQSUyMmxlZnQlMjIlMkMlMjJmb250V2VpZ2h0JTIyJTNBJTIybGlnaHRlciUyMiU3RCUyQyUyMmJvcmRlciUyMiUzQSU3QiUyMnRvcCUyMiUzQXRydWUlMkMlMjJsZWZ0JTIyJTNBdHJ1ZSUyQyUyMnJpZ2h0JTIyJTNBdHJ1ZSUyQyUyMmJvdHRvbSUyMiUzQXRydWUlMkMlMjJ3aWR0aCUyMiUzQTElMkMlMjJzdHlsZSUyMiUzQSUyMnNvbGlkJTIyJTJDJTIyY29sb3IlMjIlM0ElN0IlMjJsaWdodCUyMiUzQSUyMiUyM2NjY2VjZiUyMiU3RCU3RCU3RCU3RA==
Aura tab
summaryAWS
paramsJTdCJTIydGl0bGUlMjIlM0ElMjJBV1MlMjIlN0Q=

  1. Open the AWS console.

  2. Locate the target group associated with the load balancer used with the cluster. This can be done in two ways, depending on the scenario.

    1. Case 1: When the stack is used for deployment, and the Load Balancer is created as a part of it, In this case, perform the following steps.

      1. Navigate to CloudFormation > Stacks > <STACK-NAME>

      2. Click the Resources tab.

      3. Search for KyvosManagerAlbTargetGroup, and then click it. In the Resources section, target group with the name starting with KyvosTG-<STACK-NAME> or KyvosWebServer-<STACK-NAME> and then click it.

      4. In the Resources section, do the following:

        1. Click the link in the Physical ID column. It will open a new tab.

        2. Click the link in the Name column.

          image-20240117-090901.png

    2. Case 2 : Go to EC2 > Target groups.
      On the Target groups page, perform the following steps.

      1. Locate your target group by name and click the target group.

      2. This will open the Target Group details page.

      3. On the page, verify it by checking the value displays for Load balancer.

        image-20240109-164454.png

  3. Click the Health checks tab in the Target group details section.

  4. Click Edit.

  5. Under Health check path, change the health check path to /kyvosmanagerkyvos/kmha/activeKyvosManagerInstance

  6. Click Save changes. The Health check changes are saved now.

  7. Click on the Targets tab in the Target group details section.

    image-20240119-082059.png

  8. Click Register targets.

  9. Select the newly added Kyvos Manager instance ID from Instance ID column under Available instances.

  10. Enter the required port under Ports for the selected instances.

  11. Click Include as pending below. It will show the added instance under the Review targets section.

  12. Click Register pending targets. It will register the pending targets to the Target group.

Aura tab
summaryAzure
paramsJTdCJTIydGl0bGUlMjIlM0ElMjJBenVyZSUyMiU3RA==

  1. Open Azure console.

  2. Go to Deployment in the Settings section.

  3. Click the deployment.

  4. Expand the Deployment details section.

  5. Search for Application gateway.

    image-20240117-081748.png

  6. Click Application gateway resource link.

  7. Select Backend pools display in the left pane under Settings.

  8. Click KyvosManagerLoadBalancerBackEndPool WebPortalLoadBalancerBackEndPool.

  9. Under Backend targets Select Target type as Virtual Machine and Select newly added Kyvos Manager Virtual machine in Target.

  10. Click Save. The virtual Machine is added to the backend pool targets.

  11. Go to Health probe in the Settings section.

  12. Click KyvosManagerLoadBalancerHealthProbe WebPortalLoadBalancerHealthProbe.

  13. Change the path to /kyvosmanagerkyvos/kmha/activeKyvosManagerInstance.

  14. Click Test

  15. After successful test, click Save.

    image-20240119-081756.png
Aura tab
summaryGCP
paramsJTdCJTIydGl0bGUlMjIlM0ElMjJHQ1AlMjIlN0Q=
Panel
panelIconIdatlassian-note
panelIcon:note:
bgColor#DEEBFF

...

  1. In the Search bar, enter Load Balancer. A list is displayed. Select the required load balancer.

  2. In the Backends section, click the Health check link.

  3. On the Health Check section, change the path to /kyvos/.

    image-20240125-130321.pngImage Added

  4. Click Save.

Removing nodes entry
Anchor
RemvoingWPS
RemvoingWPS

...

Aura tab collection
paramsJTdCJTIyZ2VuZXJhbCUyMiUzQSU3QiUyMnRhYlNwYWNpbmclMjIlM0EwJTJDJTIydGFiV2lkdGglMjIlM0ExMDAlMkMlMjJ0YWJIZWlnaHQlMjIlM0E1MCUyQyUyMmRpcmVjdGlvbiUyMiUzQSUyMmhvcml6b250YWwlMjIlN0QlMkMlMjJjb250ZW50JTIyJTNBJTdCJTIyYmFja2dyb3VuZENvbG9yJTIyJTNBJTdCJTIyY29sb3IlMjIlM0ElMjIlMjNmZmYlMjIlN0QlMkMlMjJib3JkZXIlMjIlM0ElN0IlMjJzdHlsZSUyMiUzQSUyMnNvbGlkJTIyJTJDJTIyd2lkdGglMjIlM0ExJTJDJTIydG9wJTIyJTNBdHJ1ZSUyQyUyMmJvdHRvbSUyMiUzQXRydWUlMkMlMjJsZWZ0JTIyJTNBdHJ1ZSUyQyUyMnJpZ2h0JTIyJTNBdHJ1ZSUyQyUyMmNvbG9yJTIyJTNBJTdCJTIybGlnaHQlMjIlM0ElMjIlMjNjY2NlY2YlMjIlN0QlN0QlMkMlMjJwYWRkaW5nJTIyJTNBJTdCJTIydG9wJTIyJTNBMTAlMkMlMjJyaWdodCUyMiUzQTEwJTJDJTIyYm90dG9tJTIyJTNBMTAlMkMlMjJsZWZ0JTIyJTNBMTAlN0QlN0QlMkMlMjJhY3RpdmUlMjIlM0ElN0IlMjJiYWNrZ3JvdW5kQ29sb3IlMjIlM0ElN0IlMjJjb2xvciUyMiUzQSU3QiUyMmxpZ2h0JTIyJTNBJTIyJTIzZjU4MjI3JTIyJTdEJTdEJTJDJTIydGV4dCUyMiUzQSU3QiUyMmZvbnRTaXplJTIyJTNBMTYlMkMlMjJjb2xvciUyMiUzQSU3QiUyMmxpZ2h0JTIyJTNBJTIyJTIzMDAwMDAwJTIyJTdEJTJDJTIydGV4dEFsaWduJTIyJTNBJTIybGVmdCUyMiUyQyUyMmZvbnRXZWlnaHQlMjIlM0ElMjJib2xkJTIyJTdEJTdEJTJDJTIyaG92ZXIlMjIlM0ElN0IlMjJiYWNrZ3JvdW5kQ29sb3IlMjIlM0ElN0IlMjJjb2xvciUyMiUzQSUyMiUyM2RmZTFlNiUyMiU3RCUyQyUyMnRleHQlMjIlM0ElN0IlMjJmb250U2l6ZSUyMiUzQTE4JTJDJTIyY29sb3IlMjIlM0ElMjIlMjM1ZTZjODQlMjIlMkMlMjJ0ZXh0QWxpZ24lMjIlM0ElMjJsZWZ0JTIyJTJDJTIyZm9udFdlaWdodCUyMiUzQSUyMmxpZ2h0ZXIlMjIlN0QlN0QlMkMlMjJpbmFjdGl2ZSUyMiUzQSU3QiUyMmJhY2tncm91bmRDb2xvciUyMiUzQSU3QiUyMmNvbG9yJTIyJTNBJTIyJTIzZjRmNWY3JTIyJTdEJTJDJTIydGV4dCUyMiUzQSU3QiUyMmZvbnRTaXplJTIyJTNBMTYlMkMlMjJjb2xvciUyMiUzQSUyMiUyMzVlNmM4NCUyMiUyQyUyMnRleHRBbGlnbiUyMiUzQSUyMmxlZnQlMjIlMkMlMjJmb250V2VpZ2h0JTIyJTNBJTIybGlnaHRlciUyMiU3RCUyQyUyMmJvcmRlciUyMiUzQSU3QiUyMnRvcCUyMiUzQXRydWUlMkMlMjJsZWZ0JTIyJTNBdHJ1ZSUyQyUyMnJpZ2h0JTIyJTNBdHJ1ZSUyQyUyMmJvdHRvbSUyMiUzQXRydWUlMkMlMjJ3aWR0aCUyMiUzQTElMkMlMjJzdHlsZSUyMiUzQSUyMnNvbGlkJTIyJTJDJTIyY29sb3IlMjIlM0ElN0IlMjJsaWdodCUyMiUzQSUyMiUyM2NjY2VjZiUyMiU3RCU3RCU3RCU3RA==
Aura tab
summaryAWS
paramsJTdCJTIydGl0bGUlMjIlM0ElMjJBV1MlMjIlN0Q=

  1. Open AWS console.

  2. Locate the target group associated with the load balancer used. This can be done in two ways, depending on the scenario.

    1. Case1: When stack is used for deployment and Load Balancer is created as a part of it.

      1. Navigate to CloudFormation > Stacks > <STACK-NAME>

      2. Click on the Resources tab.

      3. Search for KyvosManagerAlbTargetGroup.

      4. Click the link in the Physical ID column.

      5. Click the link in Name column.

    2. Case2 : Go to EC2 > Target groups.

      1. Locate your target group by name and verify it by checking the value displays for Load balancer in the Target group details page.

      2. Click the Targets tab in Target group details section.

      3. Select the instance ID to be deregistered under the Registered targets list.

        image-20240119-081554.png

      4. Click Deregister.

Aura tab
summaryAzure
paramsJTdCJTIydGl0bGUlMjIlM0ElMjJBenVyZSUyMiU3RA==

  1. Open Azure console.

  2. Go to deployment.

  3. Go to the deployment details.

  4. Search for the type Application gateway.

  5. Click Application gateway in the resource link.

  6. Go to Backend pools display in the left menu under Settings.

  7. Click KyvosManagerLoadBalancerBackEndPool.

  8. Under Backend targets, click the Delete button against the Kyvos Manager virtual machine to be removed.

  9. Click Save.

Aura tab
summaryGCP
paramsJTdCJTIydGl0bGUlMjIlM0ElMjJHQ1AlMjIlN0Q=

  1. Go the Instance Group used in Load Balancer.

  2. Edit the Instance Group.

  3. Using the minus icon in the VM Instances list, you can remove the VMs that you no longer require for this backend service.

    image-20240125-132542.pngImage Removedimage-20240419-105254.pngImage Added

  4. Click Save.

Kyvos Reporting Service
Anchor
KyvosRS
KyvosRS

Adding nodes entry
Anchor
Adding
Adding

...

The target machine must be up and running.

  1. In the Listener Configuration section, enter the required Protocol and Port.

  2. In the Routing actions section, select Forward to target groups.

  3. Select the Target group from the list that you wan to use for forwarding to request to Kyvos Reporting Service.

  4. Click Add. The listener is added to the Load balancer.

Aura tab collection
paramsJTdCJTIyZ2VuZXJhbCUyMiUzQSU3QiUyMnRhYlNwYWNpbmclMjIlM0EwJTJDJTIydGFiV2lkdGglMjIlM0ExMDAlMkMlMjJ0YWJIZWlnaHQlMjIlM0E1MCUyQyUyMmRpcmVjdGlvbiUyMiUzQSUyMmhvcml6b250YWwlMjIlN0QlMkMlMjJjb250ZW50JTIyJTNBJTdCJTIyYmFja2dyb3VuZENvbG9yJTIyJTNBJTdCJTIyY29sb3IlMjIlM0ElMjIlMjNmZmYlMjIlN0QlMkMlMjJib3JkZXIlMjIlM0ElN0IlMjJzdHlsZSUyMiUzQSUyMnNvbGlkJTIyJTJDJTIyd2lkdGglMjIlM0ExJTJDJTIydG9wJTIyJTNBdHJ1ZSUyQyUyMmJvdHRvbSUyMiUzQXRydWUlMkMlMjJsZWZ0JTIyJTNBdHJ1ZSUyQyUyMnJpZ2h0JTIyJTNBdHJ1ZSUyQyUyMmNvbG9yJTIyJTNBJTdCJTIybGlnaHQlMjIlM0ElMjIlMjNjY2NlY2YlMjIlN0QlN0QlMkMlMjJwYWRkaW5nJTIyJTNBJTdCJTIydG9wJTIyJTNBMTAlMkMlMjJyaWdodCUyMiUzQTEwJTJDJTIyYm90dG9tJTIyJTNBMTAlMkMlMjJsZWZ0JTIyJTNBMTAlN0QlN0QlMkMlMjJhY3RpdmUlMjIlM0ElN0IlMjJiYWNrZ3JvdW5kQ29sb3IlMjIlM0ElN0IlMjJjb2xvciUyMiUzQSU3QiUyMmxpZ2h0JTIyJTNBJTIyJTIzZjU4MjI3JTIyJTdEJTdEJTJDJTIydGV4dCUyMiUzQSU3QiUyMmZvbnRTaXplJTIyJTNBMTYlMkMlMjJjb2xvciUyMiUzQSU3QiUyMmxpZ2h0JTIyJTNBJTIyJTIzMDAwMDAwJTIyJTdEJTJDJTIydGV4dEFsaWduJTIyJTNBJTIybGVmdCUyMiUyQyUyMmZvbnRXZWlnaHQlMjIlM0ElMjJib2xkJTIyJTdEJTdEJTJDJTIyaG92ZXIlMjIlM0ElN0IlMjJiYWNrZ3JvdW5kQ29sb3IlMjIlM0ElN0IlMjJjb2xvciUyMiUzQSUyMiUyM2RmZTFlNiUyMiU3RCUyQyUyMnRleHQlMjIlM0ElN0IlMjJmb250U2l6ZSUyMiUzQTE4JTJDJTIyY29sb3IlMjIlM0ElMjIlMjM1ZTZjODQlMjIlMkMlMjJ0ZXh0QWxpZ24lMjIlM0ElMjJsZWZ0JTIyJTJDJTIyZm9udFdlaWdodCUyMiUzQSUyMmxpZ2h0ZXIlMjIlN0QlN0QlMkMlMjJpbmFjdGl2ZSUyMiUzQSU3QiUyMmJhY2tncm91bmRDb2xvciUyMiUzQSU3QiUyMmNvbG9yJTIyJTNBJTIyJTIzZjRmNWY3JTIyJTdEJTJDJTIydGV4dCUyMiUzQSU3QiUyMmZvbnRTaXplJTIyJTNBMTYlMkMlMjJjb2xvciUyMiUzQSUyMiUyMzVlNmM4NCUyMiUyQyUyMnRleHRBbGlnbiUyMiUzQSUyMmxlZnQlMjIlMkMlMjJmb250V2VpZ2h0JTIyJTNBJTIybGlnaHRlciUyMiU3RCUyQyUyMmJvcmRlciUyMiUzQSU3QiUyMnRvcCUyMiUzQXRydWUlMkMlMjJsZWZ0JTIyJTNBdHJ1ZSUyQyUyMnJpZ2h0JTIyJTNBdHJ1ZSUyQyUyMmJvdHRvbSUyMiUzQXRydWUlMkMlMjJ3aWR0aCUyMiUzQTElMkMlMjJzdHlsZSUyMiUzQSUyMnNvbGlkJTIyJTJDJTIyY29sb3IlMjIlM0ElN0IlMjJsaWdodCUyMiUzQSUyMiUyM2NjY2VjZiUyMiU3RCU3RCU3RCU3RA==
Aura tab
summaryAWS
paramsJTdCJTIydGl0bGUlMjIlM0ElMjJBV1MlMjIlN0Q=

  1. Open the AWS console.

  2. In the search bar, type Target groups. A list is displayed. Click Target groups.

  3. On the Target groups page, click Create target group.

  4. On the Specify group details page, complete the following:

Area

Parameter

Description

Basic Configuration

Choose a target type

Select the Instances option for the target type.

Target group name

Enter a unique target group name.
For example, KyvosRepoting

Protocol: Port

  1. Enter Protocol as HTTP or HTTPS.

  2. Enter port as 8080.

NOTE:

  • The recommended option is to use the same protocol as used for Kyvos Web Portal.

  • If you use the existing port that is already in use, then modify the already existing rule for that port. Refer to step 13, as mentioned below.
    In case, you use a new port, add a new rule for that port. Refer to step 14, as mentioned below.

IP address type

Select the IPv4 option.

VPC

Select the VPC with the instances that of the cluster on which you want to include in the create a target group.

Protocol version

Select the HTTP 1 option.

Health Checks

Health check protocol

Select the Health check Protocol as HTTP.

Health check path

Enter the health check path as
/kyvosreporting/

AWS_KyvosReportingServiceImage Added

  1. Click Next. The Register Targets page is displayed.

    image-20240416-081634.pngImage Added

  2. Select the instance from the list that is used for running Kyvos Reporting Service.

  3. Enter the port 8080 for the selected instance that is used for running Kyvos Reporting Service.

  4. Click Include as pending below. It will show the added instance under the Review targets section. Click Register pending targets. It will register the pending targets to the Target group.

    image-20240416-082252.pngImage Added

  5. Click Create Target Group. The target group is created. After creating Target group, you need to configure Load Balancer for Listener.

    image-20240416-082441.pngImage Added

  6. Navigate EC2 > Load Balancer and then search for the Load Balancer that is being used for Kyvos Web Portal.

    image-20240416-083719.pngImage Added

  7. Click the Listeners and rules tab.

  8. If using an existing protocol:port that is listener, select the Add Rule option.

    Anchor
    step13
    step13

    image-20240416-083839.pngImage Added

    1. From the Manage rules list, select Add Rule.
      While adding a rule on the Add Rule wizard, the following fields are mandatory.

    2. Select Protocol: Port checkbox. In the Port field, enter 80.

    3. Enter a unique name for the rule, and then click Next. For example, KyvosReportingRule.

      image-20240416-085352.pngImage Added

    4. On the Details rule conditions section, click Add Condition, and then click Next. Select the Rule condition type as Path from the list and click Confirm.

      image-20240416-090838.pngImage Added

    5. On the Add condition section, add the Path section as /kyvosreporting and /kyvosreporting/* with ‘or’ condition. Click Confirm.

      image-20240416-091107.pngImage Added

    6. Verify the path and click Next.

    7. In the Action types section, select the Forward to target groups option.

      image-20240416-091327.pngImage Added

    8. Select the target group that is used for configuring Kyvos Reporting from the list, and then click Next.
      Note: Keep the remaining settings unchanged.

    9. Enter Priority as 2. Click Next. 3.
      NOTE: For AWS Marketplace, it should be 3 and for AWS Managed Service, the Priority must be set as 2.

      image-20240416-091631.pngImage Added

    10. Click Next. Confirm the Rule details and click Create. The rule is created.
      You can also delete the rule that you have created.

  9. If you want to use a new protocol:port that is a listener, select Add listener. The Add Listener page is displayed.

    Anchor
    step14
    step14

    NOTE: Ensure that the new LB port should must be reachable.
Anchor
step14step14
Aura tab
summaryAzure
paramsJTdCJTIydGl0bGUlMjIlM0ElMjJBenVyZSUyMiU3RA==

  • Open Azure console.

    • On the Home page, click Managed resource group
    Panel
    panelIconIdatlassian-note
    panelIcon:note:
    bgColor#DEEBFF

    Note

    To add a Load Balancer entry to Azure Marketplace, please contact Kyvos Support, as this action can only be performed through an Azure publisher account.

    1. Open Azure console.

    2. In the Search bar, type Load Balancer. Select the required Load Balancer from the list. enter Managed application center.

    3. Go to Marketplace application.

    4. Select your Kyvos application.

    5. Click Managed resource group and then search for application gateway.

      image (58).pngImage Added

    6. In the Settings section of the left pane, click Backend Pool. On the Backend Pools page, click Add.

    7. On the Add backend Pool dialog box,

      1. Enter a name for the backend pool. For Example, KyvosReportingbackendpool

      2. Select No to add backend pool without targets.

      3. Select the Virtual Machine option from Target Type list, and then select the Kyvos Reporting Service node from Target list that you have already added.

      4. Click Save. The backend pool is added.

        image (51).png

    8. After adding backend pool, click Listener in the Settings section display in the left pane of the page. The Listeners page is displayed. Click Add.

    9. On the Listeners page, add Listener’s details such as,

      1. Enter name of the listener.

      2. Select Protocol as HTTP and Port as 8080.

      3. Select Listener type as Basic.

      4. Click Add. The Listener is added.

        image (52).png

    10. After adding a listener, you need to add Backend Settings display in the Settings section.

    11. Click Backend settings, the Backend settings dialog is displayed.

    12. On the Backend Settings dialog box, complete the fields as shown in the following page.

      image (53).png

      NOTE: First you need to select the No display in the Use a custom probe section and save without it. You must update it after creating the Health probe.
      The Backend settings are now saved.

    13. After saving the Backend settings, select the Frontend IP configurations from the Settings section display in the left pane.

    14. On the Frontend IP configurations page, ensure that the frontend IP address has Public IP configured. This IP will be used for Kyvos Reporting URL.

      image (54).png

    15. After verifying Frontend IP configurations, click a Rule display in the Settings section. On the Rules page, click Add.

      image (55).png

    16. On the Rules page, complete the fields as shown in the following image.

      1. Enter a rule name.

      2. Enter Priority as 4.

      3. Click the Backend Targets tab, and then select the backend target and backend settings you have created.

      4. Click Save. The rule is created.

    17. After creating a rule, click Health probes from the Settings section display in the left pane. On the Health Probes page, click Add.

      image (56).png

    18. On the Health probe dialog, complete the following fieldsfields.

    19. Go the Instance Group used in Load Balancer.

    20. Edit the Instance Group.

    21. From the VM Instances list, select the VMs on which you want to use this backend service.

      image-20240125-132312.pngImage Removed

      1. Enter a name for the health probe.

      2. Select protocol.

      3. Select the No option to pick host name from backend settings.

      4. Enter the Host name.

      5. Enter the Kyvos Reporting path as /kyvosreporting/

      6. Enter Interval (seconds), Timeout (seconds), Unhealthy threshold.

      7. Select the Yes option to use probe matching conditions.

      8. Enter a name for the health probethe HTTP response status code match.

      9. Select protocolbackend settings from the list that you have created.

      10. Select the No option to pick host name from backend settings.

      11. Enter the Host name.

      12. Enter the Kyvos Reporting path as /kyvosreporting/

      13. Enter Interval (seconds), Timeout (seconds), Unhealthy threshold.

      14. Select the Yes option to use probe matching conditions.

      15. Enter the HTTP response status code match.

      16. Select backend settings from the list.

      17. Click Test to verify the backend health before adding the health probe.

      18. Click Test. After successful test, click Save.

    Aura tab
    summaryGCP
    paramsJTdCJTIydGl0bGUlMjIlM0ElMjJHQ1AlMjIlN0Q=
    Panel
    panelIconIdatlassian-note
    panelIcon:note:
    bgColor#DEEBFF

    For GCP, you must configure Load Balancer. To do this, refer to the Configuring External Load Balancer for GCP section.

      1. Click Test to verify the backend health before adding the health probe.

      2. Click Test. After successful test, click Save.

    Aura tab
    summaryGCP
    paramsJTdCJTIydGl0bGUlMjIlM0ElMjJHQ1AlMjIlN0Q=

    1. You must configure Load Balancer as a prerequisite.

    2. Go the Instance Group used in Load Balancer.

    3. Edit the Instance Group.

    4. From the VM Instances list, select the VMs on which you want to use this backend service.

    5. In the Port Mapping area, click Add Port.

      • Port name as kyvosreporting-https and Port number as 8080.

      • Port name as kyvosreporting-http and Port number as 8080.

        image-20240419-104056.pngImage Added

    6. Click Save.

    7. In the Search bar, enter Load Balancer. A list is displayed. Select the required load balancer.

    8. In the Backends section, click the Health check link.

    9. On the Health Check section, change the path to /kyvosreporting/.

      image-20240419-104311.pngImage Added

    10. Click Save.

    Removing nodes entry
    Anchor
    Removingnodeentry
    Removingnodeentry

    ...

    Aura tab collection
    paramsJTdCJTIyZ2VuZXJhbCUyMiUzQSU3QiUyMnRhYlNwYWNpbmclMjIlM0EwJTJDJTIydGFiV2lkdGglMjIlM0ExMDAlMkMlMjJ0YWJIZWlnaHQlMjIlM0E1MCUyQyUyMmRpcmVjdGlvbiUyMiUzQSUyMmhvcml6b250YWwlMjIlN0QlMkMlMjJjb250ZW50JTIyJTNBJTdCJTIyYmFja2dyb3VuZENvbG9yJTIyJTNBJTdCJTIyY29sb3IlMjIlM0ElMjIlMjNmZmYlMjIlN0QlMkMlMjJib3JkZXIlMjIlM0ElN0IlMjJzdHlsZSUyMiUzQSUyMnNvbGlkJTIyJTJDJTIyd2lkdGglMjIlM0ExJTJDJTIydG9wJTIyJTNBdHJ1ZSUyQyUyMmJvdHRvbSUyMiUzQXRydWUlMkMlMjJsZWZ0JTIyJTNBdHJ1ZSUyQyUyMnJpZ2h0JTIyJTNBdHJ1ZSUyQyUyMmNvbG9yJTIyJTNBJTdCJTIybGlnaHQlMjIlM0ElMjIlMjNjY2NlY2YlMjIlN0QlN0QlMkMlMjJwYWRkaW5nJTIyJTNBJTdCJTIydG9wJTIyJTNBMTAlMkMlMjJyaWdodCUyMiUzQTEwJTJDJTIyYm90dG9tJTIyJTNBMTAlMkMlMjJsZWZ0JTIyJTNBMTAlN0QlN0QlMkMlMjJhY3RpdmUlMjIlM0ElN0IlMjJiYWNrZ3JvdW5kQ29sb3IlMjIlM0ElN0IlMjJjb2xvciUyMiUzQSU3QiUyMmxpZ2h0JTIyJTNBJTIyJTIzZjU4MjI3JTIyJTdEJTdEJTJDJTIydGV4dCUyMiUzQSU3QiUyMmZvbnRTaXplJTIyJTNBMTYlMkMlMjJjb2xvciUyMiUzQSU3QiUyMmxpZ2h0JTIyJTNBJTIyJTIzMDAwMDAwJTIyJTdEJTJDJTIydGV4dEFsaWduJTIyJTNBJTIybGVmdCUyMiUyQyUyMmZvbnRXZWlnaHQlMjIlM0ElMjJib2xkJTIyJTdEJTdEJTJDJTIyaG92ZXIlMjIlM0ElN0IlMjJiYWNrZ3JvdW5kQ29sb3IlMjIlM0ElN0IlMjJjb2xvciUyMiUzQSUyMiUyM2RmZTFlNiUyMiU3RCUyQyUyMnRleHQlMjIlM0ElN0IlMjJmb250U2l6ZSUyMiUzQTE4JTJDJTIyY29sb3IlMjIlM0ElMjIlMjM1ZTZjODQlMjIlMkMlMjJ0ZXh0QWxpZ24lMjIlM0ElMjJsZWZ0JTIyJTJDJTIyZm9udFdlaWdodCUyMiUzQSUyMmxpZ2h0ZXIlMjIlN0QlN0QlMkMlMjJpbmFjdGl2ZSUyMiUzQSU3QiUyMmJhY2tncm91bmRDb2xvciUyMiUzQSU3QiUyMmNvbG9yJTIyJTNBJTIyJTIzZjRmNWY3JTIyJTdEJTJDJTIydGV4dCUyMiUzQSU3QiUyMmZvbnRTaXplJTIyJTNBMTYlMkMlMjJjb2xvciUyMiUzQSUyMiUyMzVlNmM4NCUyMiUyQyUyMnRleHRBbGlnbiUyMiUzQSUyMmxlZnQlMjIlMkMlMjJmb250V2VpZ2h0JTIyJTNBJTIybGlnaHRlciUyMiU3RCUyQyUyMmJvcmRlciUyMiUzQSU3QiUyMnRvcCUyMiUzQXRydWUlMkMlMjJsZWZ0JTIyJTNBdHJ1ZSUyQyUyMnJpZ2h0JTIyJTNBdHJ1ZSUyQyUyMmJvdHRvbSUyMiUzQXRydWUlMkMlMjJ3aWR0aCUyMiUzQTElMkMlMjJzdHlsZSUyMiUzQSUyMnNvbGlkJTIyJTJDJTIyY29sb3IlMjIlM0ElN0IlMjJsaWdodCUyMiUzQSUyMiUyM2NjY2VjZiUyMiU3RCU3RCU3RCU3RA==
    Aura tab
    summaryAWS
    paramsJTdCJTIydGl0bGUlMjIlM0ElMjJBV1MlMjIlN0Q=
    Panel
    panelIconIdatlassian-note
    panelIcon:note:
    bgColor#DEEBFF

    Before deleting target group, you must delete the rule that is using that target group.

    Step:1 Removing a rule

    1. Open AWS console.

    2. Go to EC2 > Load balancers, and then navigate to the Load balancer you have created. The Load balancer page is displayed.

    3. Navigate to the Listening and rules section, and then select the rule from the list that you want to delete.

    4. From the Actions list, select Delete rule. On the confirmation message, click Delete. The rule is deleted.

      image-20240416-091843.pngImage Added

    Step:2 Removing Target group

    1. Navigate EC2 > Load Balancer and then search for the Load Balancer that is being used for Kyvos Reporting Service.

    2. Click the Listeners and rules tab.

    3. If you use the existing listener is the same then , you must delete the rule associated with that listener that is forwarding request to the Kyvos Reporting Target group. If you are using a listener that is having a single rule, then the listener is itself deleted.

    4. Go to EC2 > Target groups.

    5. Search your target group that is being used for Kyvos Reporting.

    6. Select the target group and then click Delete from the Actions listthe target group and then click Delete from the Actions list.

    Step:3 Removing the listener

    If you have added a new listener, in this case, you must remove the listener.

    Aura tab
    summaryAzure
    paramsJTdCJTIydGl0bGUlMjIlM0ElMjJBenVyZSUyMiU3RA==JTdCJTIydGl0bGUlMjIlM0ElMjJBenVyZSUyMiU3RA==
    Panel
    panelIconIdatlassian-note
    panelIcon:note:
    bgColor#DEEBFF

    Note

    To remove a Load Balancer entry from Azure Marketplace, please contact Kyvos Support, as this action can only be performed through an Azure publisher account.

    1. Open Azure console.

    2. Go to deployment Kyvos Application.

    3. Go to the deployment details.

    4. Search for the type Application gateway.

    5. Click Application gateway in the resource link.

    6. Go to Backend pools display in the left menu under Settings.

    7. Click KyvosManagerLoadBalancerBackEndPool.

    8. Under Backend targets, click the Delete button against the Kyvos Manager virtual machine to be removed.

    9. Click SaveClick Managed resource group.

    10. In overview tab, search for application gateway

    11. Delete a rule that you have created.

    12. Delete a backend pool that you have created.

    13. Delete backend settings that you have created.

    14. Delete listener that you have created.  

    15. Delete health probe that you have created.

    Aura tab
    summaryGCP
    paramsJTdCJTIydGl0bGUlMjIlM0ElMjJHQ1AlMjIlN0Q=

    1. Go Open GCP Console.

    2. In the Search bar, enter Instance Groups. A list of Instance groups is displayed.

    3. Select the Instance Group which is used in backend Service of Load Balancer.

    4. Edit the Instance Group.

    5. Using the minus icon in the VM Instances list, you can remove the VMs that you no longer require for this backend service.

      image-20240125-132542.pngImage Removedimage-20240419-105055.pngImage Added

    6. Click Save.