Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 56 Next »

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

(tick) Kyvos Azure Marketplace   (tick) Kyvos GCP Marketplace (error) Kyvos Single Node Installation (Kyvos SNI)


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.

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:

Kyvos Manager Service

Adding Kyvos Manager nodes entry

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

  • Target group (AWS) of Load Balancer

  • Backend Targets (Azure) of Load Balancer

  • Instance Group (GCP) of Load Balancer

Removing Kyvos Manager nodes entry

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 :

  • Target group (AWS) of Load Balancer

  • Backend Targets (Azure) of Load Balancer

  • Instance Group (GCP) of Load Balancer

Kyvos Web Portal Service

Adding nodes entry

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

  • Target group (AWS) of Load Balancer

  • Backend Targets (Azure) of Load Balancer

  • Instance Group (GCP) of Load Balancer

Removing nodes entry

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 :

  • Target group (AWS) of Load Balancer

  • Backend Targets (Azure) of Load Balancer

  • Instance Group (GCP) of Load Balancer

Kyvos Reporting Service

Adding nodes entry

For cloud environments where Load Balancer is used, after adding the Kyvos Reporting service, you need to perform the following two steps:

  1. Creation of

    • Target group (AWS) of Load Balancer

    • Backend Targets (Azure) of Load Balancer

    • Instance Group (GCP) of Load Balancer

  2. Configure Load Balancer for Listener

Removing nodes entry

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 :

  • Target group (AWS) of Load Balancer

  • Backend Targets (Azure) of Load Balancer

  • Instance Group (GCP) of Load Balancer

  • No labels