Versions Compared

Old Version 47

changes.mady.by.user Sarabjeet Kaur

Saved on

compared with

New Version 48

changes.mady.by.user Sarabjeet Kaur

Saved on

Key

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

Applies to: (error) Kyvos Enterprise  (tick) Kyvos Cloud (SaaS on AWS) (tick) Kyvos AWS Marketplace

...

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 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:

...

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, 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 <>.

  13. Change the path to /kyvosmanager/kmhakyvos/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

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

  1. Go the Instance Group used in Load Balancer.

  2. Edit the Instance Group.

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

    image-20240125-132312.png

  4. Click Save.

...