Versions Compared

Old Version 39

changes.mady.by.user Sarabjeet Kaur

Saved on

compared with

New Version 40

changes.mady.by.user Sarabjeet Kaur

Saved on

Key

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

...

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.

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 you want to include in the 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

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

  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.

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

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

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

  8. Click the Listeners and rules tab.

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

    Anchor
    step13
    step13

    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.

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

    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.

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

    6. Verify the path and click Next.

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

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

    9. Enter Priority as 2.

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

  10. If you want to use a new protocol:port that is a listener, select Add listener. The Add Listener page is displayed. Ensure that the new port should be reachable.

    Anchor
    step14
    step14

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

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.

Removing nodes entry
Anchor

...

Removingnodeentry

...

Removingnodeentry

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=
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 you want to delete.

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

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 the 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 list.

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

  4. Click Save.