Page Comparison

...

Aura tab collection

params

JTdCJTIyZ2VuZXJhbCUyMiUzQSU3QiUyMnRhYlNwYWNpbmclMjIlM0EwJTJDJTIydGFiV2lkdGglMjIlM0ExMDAlMkMlMjJ0YWJIZWlnaHQlMjIlM0E1MCUyQyUyMmRpcmVjdGlvbiUyMiUzQSUyMmhvcml6b250YWwlMjIlN0QlMkMlMjJjb250ZW50JTIyJTNBJTdCJTIyYmFja2dyb3VuZENvbG9yJTIyJTNBJTdCJTIyY29sb3IlMjIlM0ElMjIlMjNmZmYlMjIlN0QlMkMlMjJib3JkZXIlMjIlM0ElN0IlMjJzdHlsZSUyMiUzQSUyMnNvbGlkJTIyJTJDJTIyd2lkdGglMjIlM0ExJTJDJTIydG9wJTIyJTNBdHJ1ZSUyQyUyMmJvdHRvbSUyMiUzQXRydWUlMkMlMjJsZWZ0JTIyJTNBdHJ1ZSUyQyUyMnJpZ2h0JTIyJTNBdHJ1ZSUyQyUyMmNvbG9yJTIyJTNBJTdCJTIybGlnaHQlMjIlM0ElMjIlMjNjY2NlY2YlMjIlN0QlN0QlMkMlMjJwYWRkaW5nJTIyJTNBJTdCJTIydG9wJTIyJTNBMTAlMkMlMjJyaWdodCUyMiUzQTEwJTJDJTIyYm90dG9tJTIyJTNBMTAlMkMlMjJsZWZ0JTIyJTNBMTAlN0QlN0QlMkMlMjJhY3RpdmUlMjIlM0ElN0IlMjJiYWNrZ3JvdW5kQ29sb3IlMjIlM0ElN0IlMjJjb2xvciUyMiUzQSU3QiUyMmxpZ2h0JTIyJTNBJTIyJTIzZjU4MjI3JTIyJTdEJTdEJTJDJTIydGV4dCUyMiUzQSU3QiUyMmZvbnRTaXplJTIyJTNBMTYlMkMlMjJjb2xvciUyMiUzQSU3QiUyMmxpZ2h0JTIyJTNBJTIyJTIzMDAwMDAwJTIyJTdEJTJDJTIydGV4dEFsaWduJTIyJTNBJTIybGVmdCUyMiUyQyUyMmZvbnRXZWlnaHQlMjIlM0ElMjJib2xkJTIyJTdEJTdEJTJDJTIyaG92ZXIlMjIlM0ElN0IlMjJiYWNrZ3JvdW5kQ29sb3IlMjIlM0ElN0IlMjJjb2xvciUyMiUzQSUyMiUyM2RmZTFlNiUyMiU3RCUyQyUyMnRleHQlMjIlM0ElN0IlMjJmb250U2l6ZSUyMiUzQTE4JTJDJTIyY29sb3IlMjIlM0ElMjIlMjM1ZTZjODQlMjIlMkMlMjJ0ZXh0QWxpZ24lMjIlM0ElMjJsZWZ0JTIyJTJDJTIyZm9udFdlaWdodCUyMiUzQSUyMmxpZ2h0ZXIlMjIlN0QlN0QlMkMlMjJpbmFjdGl2ZSUyMiUzQSU3QiUyMmJhY2tncm91bmRDb2xvciUyMiUzQSU3QiUyMmNvbG9yJTIyJTNBJTIyJTIzZjRmNWY3JTIyJTdEJTJDJTIydGV4dCUyMiUzQSU3QiUyMmZvbnRTaXplJTIyJTNBMTYlMkMlMjJjb2xvciUyMiUzQSUyMiUyMzVlNmM4NCUyMiUyQyUyMnRleHRBbGlnbiUyMiUzQSUyMmxlZnQlMjIlMkMlMjJmb250V2VpZ2h0JTIyJTNBJTIybGlnaHRlciUyMiU3RCUyQyUyMmJvcmRlciUyMiUzQSU3QiUyMnRvcCUyMiUzQXRydWUlMkMlMjJsZWZ0JTIyJTNBdHJ1ZSUyQyUyMnJpZ2h0JTIyJTNBdHJ1ZSUyQyUyMmJvdHRvbSUyMiUzQXRydWUlMkMlMjJ3aWR0aCUyMiUzQTElMkMlMjJzdHlsZSUyMiUzQSUyMnNvbGlkJTIyJTJDJTIyY29sb3IlMjIlM0ElN0IlMjJsaWdodCUyMiUzQSUyMiUyM2NjY2VjZiUyMiU3RCU3RCU3RCU3RA==

Aura tab

summary	AWS
params	JTdCJTIydGl0bGUlMjIlM0ElMjJBV1MlMjIlN0Q=

Open the AWS console.
In the search bar, type Target groups. A list is displayed. Click Target groups.
On the Target groups page, click Create target group.
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	Enter Protocol as HTTP or HTTPS. 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/

Click Next. The Register Targets page is displayed.
Select the instance from the list that is used for running Kyvos Reporting Service.
Enter the port 8080 for the selected instance that is used for running Kyvos Reporting Service.
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.
Click Create Target Group. The target group is created. After creating Target group, you need to configure Load Balancer for Listener
Navigate EC2 > Load Balancer and then search for the Load Balancer that is being used for Kyvos Web Portal.
Click the Listeners and rules tab.
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.
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

summary	Azure
params	JTdCJTIydGl0bGUlMjIlM0ElMjJBenVyZSUyMiU3RA==

Open Azure console.
Go to Deployment in the Settings section.
Click the deployment.
Expand the Deployment details section.
Search for Application gateway.
Image Removed
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
On the Home page, click Managed resource group.
In the Search bar, type Load Balancer. Select the required Load Balancer from the list.
In the Settings section of the left pane, click Backend Pool. On the Backend Pools page, click Add.
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 Added
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.
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 Added
After adding a listener, you need to add Backend Settings display in the Settings section.
Click Backend settings, the Backend settings dialog is displayed.
On the Backend Settings dialog box, complete the fields as shown in the following page.
Image Added
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.
After saving the Backend settings, select the Frontend IP configurations from the Settings section display in the left pane.
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 Added
After verifying Frontend IP configurations, click a Rule display in the Settings section. On the Rules page, click Add.
Image Added
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.
After creating a rule, click Health probes from the Settings section display in the left pane. On the Health Probes page, click Add.
Image Added
On the Health probe dialog, complete the following fields.
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 the HTTP response status code match.
9. Select backend settings from the list.
10. Click Test to verify the backend health before adding the health probe.
11. Click Test. After successful test, click Save.
Image Removed

Aura tab

summary	GCP
params	JTdCJTIydGl0bGUlMjIlM0ElMjJHQ1AlMjIlN0Q=

Panel

panelIconId	atlassian-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.

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.

...

Versions Compared

Old Version 41

New Version 42

Key