Enabling Secrets Manager on AWS after upgrade
Applies to: Kyvos Enterprise Kyvos Cloud (SaaS on AWS) Kyvos AWS Marketplace
Kyvos Azure Marketplace  Kyvos GCP Marketplace Kyvos Single Node Installation (Kyvos SNI)
If your cluster was deployed without AWS Secrets Manager, you can enable it later through the Kyvos Manager at the time of the upgrade.
Prerequisites
To enable the Secret Manager on AWS from KM after the upgrade, you must have a Secret Manager with the IAM role which is being used in the Kyvos Stack as per your Kyvos version.
To create the Secret Manager as mentioned above, perform the following:
Go to the EMR Configuration page on Kyvos Manager.
On the Secrets fields, provide your Secret Manager.Â
In the HCatalog Library Path, add the path /usr/share/aws/aws-java-sdk/aws-java-sdk-secretsmanager-*.jarÂ
Click the Apply button from the top-right of the page to update the EMR configuration.
Restart BI servers from the Actions menu on the Dashboard page.
Enabling Secrets Manager on AWS after upgrade
Go to Manage Credentials > Switch Secret Store, and select the Migrate Password to Secrets Manager checkbox.
Click the Apply button from the top-right of the page.
Restart BI servers from the Actions menu on the Dashboard page.
Copyright Kyvos, Inc. All rights reserved.