AWSJTdCJTIydGl0bGUlMjIlM0ElMjJBV1MlMjIlN0Q=

Open the AWS console.
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.
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.
Click the Health checks tab in the Target group details section.
Click Edit.
Under Health check path, change the health check path to /kyvosmanager/kmha/activeKyvosManagerInstance
Click Save changes. The Health check changes are saved now.
Click on the Targets tab in the Target group details section.
Click Register targets.
Select the newly added Kyvos Manager instance ID from Instance ID column under Available instances.
Enter the required port under Ports for the selected instances.
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.

AzureJTdCJTIydGl0bGUlMjIlM0ElMjJBenVyZSUyMiU3RA==

Open Azure console.
Go to Deployment in the Settings section.
Click the deployment.
Expand the Deployment details section.
Search for Application gateway.
Click Application gateway resource link.
Select Backend pools display in the left pane under Settings.
Click KyvosManagerLoadBalancerBackEndPool.
Under Backend targets Select Target type as Virtual Machine and Select newly added Kyvos Manager Virtual machine in Target.
Click Save. The virtual Machine is added to the backend pool targets.
Go to Health probe in the Settings section.
Click KyvosManagerLoadBalancerHealthProbe.
Change the path to /kyvosmanager/kmha/activeKyvosManagerInstance.
Click Test
After successful test, click Save.

GCPJTdCJTIydGl0bGUlMjIlM0ElMjJHQ1AlMjIlN0Q=

:note:atlassian-note#DEEBFF

For GCP, you must configure Load Balancer. To do this, refer to the https://kyvosdocumentation.atlassian.net/wiki/spaces/KD20241/pages/45352219 section.

Go the Instance Group used in Load Balancer.
Edit the Instance Group.
From the VM Instances list, select the VMs on which you want to use this backend service.
Click Save.