Versions Compared

Key

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

Applies to:Image RemovedKyvos Enterprise  Image RemovedKyvos Cloud (Managed Services on AWS)  Image RemovedKyvos Azure Marketplace

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

(error) Kyvos Azure Marketplace   (error) Kyvos GCP Marketplace (error) Kyvos Single Node Installation (Kyvos SNI)   Image RemovedKyvos Free (Limited offering for AWS)

...

You can create external functions for use with the Kyvos cluster and use them at the time of cluster deployment using the Kyvos Manager wizard.

Panel
panelIconIdatlassian-warning
panelIcon:warning:
bgColor#FFEBE6

Warning

Download the azure_functions.json and azure_functions_secure.json (for secured functions) files provided in the the Azure Installation Files folder before proceeding.

You can also create secured Functions which can be used for deploying the cluster with enhanced security (enables advanced security for Storage Account, Key Vault, and Virtual Machines).

Aura tab collection
settings{"generalSettings":{"tabSpacing":0,"tabWidth":100,"tabHeight":45,"direction":"horizontal"},"activeSettings":{"backgroundColor":{"color":"#f58227"},"text":{"fontSize":14,"color":"#000000","textAlign":"left","fontWeight":"bold"}},"inactiveSettings":{"backgroundColor":{"color":"#e2e2e2"},"text":{"fontSize":14,"color":"#000000","textAlign":"left","fontWeight":"bold"},"border":{"top":true,"left":true,"right":true,"bottom":true,"width":1,"style":"solid","color":"#cccecf"}},"contentSettings":{"backgroundColor":{"color":"#fff"},"padding":{"top":10,"right":10,"bottom":10,"left":10},"border":{"style":"solid","width":1,"top":true,"bottom":true,"left":true,"right":true,"color":"#cccecf"}},"hoverSettings":{"backgroundColor":{"color":"#cccecf"},"text":{"fontSize":14,"color":"#000000","textAlign":"left","fontWeight":"normal"}}}
tab1
Aura tab
titleAzure Functions
Aura tabtitleAzure Secured Functions
paramsJTdCJTIyZ2VuZXJhbCUyMiUzQSU3QiUyMnRhYlNwYWNpbmclMjIlM0EwJTJDJTIydGFiV2lkdGglMjIlM0ExMDAlMkMlMjJ0YWJIZWlnaHQlMjIlM0E1MCUyQyUyMmRpcmVjdGlvbiUyMiUzQSUyMmhvcml6b250YWwlMjIlN0QlMkMlMjJjb250ZW50JTIyJTNBJTdCJTIyYmFja2dyb3VuZENvbG9yJTIyJTNBJTdCJTIyY29sb3IlMjIlM0ElMjIlMjNmZmYlMjIlN0QlMkMlMjJib3JkZXIlMjIlM0ElN0IlMjJzdHlsZSUyMiUzQSUyMnNvbGlkJTIyJTJDJTIyd2lkdGglMjIlM0ExJTJDJTIydG9wJTIyJTNBdHJ1ZSUyQyUyMmJvdHRvbSUyMiUzQXRydWUlMkMlMjJsZWZ0JTIyJTNBdHJ1ZSUyQyUyMnJpZ2h0JTIyJTNBdHJ1ZSUyQyUyMmNvbG9yJTIyJTNBJTdCJTIybGlnaHQlMjIlM0ElMjIlMjNjY2NlY2YlMjIlN0QlN0QlMkMlMjJwYWRkaW5nJTIyJTNBJTdCJTIydG9wJTIyJTNBMTAlMkMlMjJyaWdodCUyMiUzQTEwJTJDJTIyYm90dG9tJTIyJTNBMTAlMkMlMjJsZWZ0JTIyJTNBMTAlN0QlN0QlMkMlMjJhY3RpdmUlMjIlM0ElN0IlMjJiYWNrZ3JvdW5kQ29sb3IlMjIlM0ElN0IlMjJjb2xvciUyMiUzQSU3QiUyMmxpZ2h0JTIyJTNBJTIyJTIzZjU4MjI3JTIyJTdEJTdEJTJDJTIydGV4dCUyMiUzQSU3QiUyMmZvbnRTaXplJTIyJTNBMTYlMkMlMjJjb2xvciUyMiUzQSU3QiUyMmxpZ2h0JTIyJTNBJTIyJTIzMDAwMDAwJTIyJTdEJTJDJTIydGV4dEFsaWduJTIyJTNBJTIybGVmdCUyMiUyQyUyMmZvbnRXZWlnaHQlMjIlM0ElMjJib2xkJTIyJTdEJTdEJTJDJTIyaG92ZXIlMjIlM0ElN0IlMjJiYWNrZ3JvdW5kQ29sb3IlMjIlM0ElN0IlMjJjb2xvciUyMiUzQSUyMiUyM2RmZTFlNiUyMiU3RCUyQyUyMnRleHQlMjIlM0ElN0IlMjJmb250U2l6ZSUyMiUzQTE4JTJDJTIyY29sb3IlMjIlM0ElMjIlMjM1ZTZjODQlMjIlMkMlMjJ0ZXh0QWxpZ24lMjIlM0ElMjJsZWZ0JTIyJTJDJTIyZm9udFdlaWdodCUyMiUzQSUyMmxpZ2h0ZXIlMjIlN0QlN0QlMkMlMjJpbmFjdGl2ZSUyMiUzQSU3QiUyMmJhY2tncm91bmRDb2xvciUyMiUzQSU3QiUyMmNvbG9yJTIyJTNBJTIyJTIzZjRmNWY3JTIyJTdEJTJDJTIydGV4dCUyMiUzQSU3QiUyMmZvbnRTaXplJTIyJTNBMTYlMkMlMjJjb2xvciUyMiUzQSUyMiUyMzVlNmM4NCUyMiUyQyUyMnRleHRBbGlnbiUyMiUzQSUyMmxlZnQlMjIlMkMlMjJmb250V2VpZ2h0JTIyJTNBJTIybGlnaHRlciUyMiU3RCUyQyUyMmJvcmRlciUyMiUzQSU3QiUyMnRvcCUyMiUzQXRydWUlMkMlMjJsZWZ0JTIyJTNBdHJ1ZSUyQyUyMnJpZ2h0JTIyJTNBdHJ1ZSUyQyUyMmJvdHRvbSUyMiUzQXRydWUlMkMlMjJ3aWR0aCUyMiUzQTElMkMlMjJzdHlsZSUyMiUzQSUyMnNvbGlkJTIyJTJDJTIyY29sb3IlMjIlM0ElN0IlMjJsaWdodCUyMiUzQSUyMiUyM2NjY2VjZiUyMiU3RCU3RCU3RCU3RA==
Aura tab
summaryAzure Functions
paramsJTdCJTIydGl0bGUlMjIlM0ElMjJBenVyZSUyMEZ1bmN0aW9ucyUyMiU3RA==
  1. Log in to the Azure portal, and navigate to Deploy custom template.

  2. On the Custom Deployment page, click the Build your own template in the editor option.

  3. On the Edit Template page, click Load File.

  4. Upload the azure_functions.json file.

  5. Click Save.

  6. The Custom Deployment page is loaded with parameters required for deployment.

  7. Here, enter the details as:

Parameter

Description 

Subscription

Your account subscription.

Subscription Resource group

Enter the name of your resource group. The resource group is a collection of resources that share the same lifecycle, permissions, and policies.

Region

Choose the Azure region that's right for you and your customers. Not every resource is available in every region.

Managed Identity Name

Enter the name of User-Managed Identity to be attached with all Kyvos VMs.

Managed Identity Resource Group Name

The Name of Resource Group in which Managed Identity is deployed.

Kyvos Work Dir

Enter the path for the Kyvos work directory.

Additional Tags

Enter the additional tags to put on all resources.
Use the syntax as: {"Key1": "Value1", "Key2" : "Value2"}

Storage Account Name

Enter the name of the Storage Account to be used for Kyvos.

Storage Account Container Name

Enter the name of the Container in Storage Account which will be used for Kyvos.

Storage Account Resource Group

Enter the name of the Resource Group in which the Storage Account is deployed.

Azure Function Crontab

 Crontab entry to call Azure functions for use with cluster scheduling.

  1. Click Review and create.
    The Outputs page will display the Function name. Copy it and keep it handy for deployment.

Aura tab
summaryAzure Secured Functions
paramsJTdCJTIydGl0bGUlMjIlM0ElMjJBenVyZSUyMFNlY3VyZWQlMjBGdW5jdGlvbnMlMjIlN0Q=
  1. Log in to the Azure portal, and navigate to Deploy custom template.

  2. On the Custom Deployment page, click the Build your own template in the editor option.

  3. On the Edit Template page, click Load File.

  4. Upload the azure_functions_secure.json file.

  5. Click Save.

  6. The Custom Deployment page is loaded with parameters required for deployment.

  7. Here, enter the details as:

Parameter

Description 

Subscription

Your account subscription.

Subscription Resource group

Enter the name of your resource group. The resource group is a collection of resources that share the same lifecycle, permissions, and policies.

Region

Choose the Azure region that's right for you and your customers. Not every resource is available in every region.

Azure Function Subnet Name

Name of the Subnet in which the Azure function will be deployed.

Kyvos Instance Subnet

Name of the Subnet in which the Kyvos cluster is deployed.

Managed Identity Name

Enter the name of User-Managed Identity to be attached with all Kyvos VMs.

Managed Identity Resource Group Name

The Name of Resource Group in which Managed Identity is deployed.

Kyvos Work Dir

Enter the path for the Kyvos work directory.

Additional Tags

Enter the additional tags to put on all resources.
Use the syntax as: {"Key1": "Value1", "Key2" : "Value2"}

Storage Account Name

Enter the name of the Storage Account to be used for Kyvos.

Storage Account Container Name

Enter the name of Container in Storage Account which will be used for Kyvos.

Storage Account Resource Group

Enter the name of the Resource Group in which the Storage Account is deployed.

Azure Function Crontab

Crontab entry to call Azure functions for use with cluster scheduling.

  1. Click Review and create.
    The Outputs page will display the Function name. Copy it and keep it handy for deployment.

Aura tab
summaryPost Deployment steps
paramsJTdCJTIydGl0bGUlMjIlM0ElMjJQb3N0JTIwRGVwbG95bWVudCUyMHN0ZXBzJTIwJTIyJTdE

Once you have deployed the cluster with externally created Secured Functions, you need to perform the following steps after deployment.

  1. Go to the Key Vault created in Azure Deployment.

  2. Navigate to Networking.

  3. Click on Selected Network > Add existing Virtual Networks.

  4. Choose the Virtual network, then select the same Subnet where you have launched your secured Functions.
    You can find the subnet in the inputs of Deployment of Azure Function. Look for the value of the AzureFunctionSubnetName parameter.

  5. Similarly, go to Storage Account associated with Kyvos deployment and perform steps 2 to 5 for the storage account.