and more in a single search tool across platforms. Read the announcement here. |
12/11/2023 11:49 AM - edited 12/11/2023 11:50 AM
Background:
We have an internal tenant for our organization and have been working on deploying the CPAM module. We had completed the setup of a HashiCorp Vault on it. Recently, we received access to the new instance of the tenant (v23.11) and would like to migrate the vault to the new tenant. Is there a way to do that? If so, how? Or do we need to recreate the vault on the new upgraded instance?
12/18/2023 06:29 AM
@thesvg Thanks for posting your question. Few questions before we can determine if the migration has to be done or not.
In these situations, it is ideal to maintain the existing data (connections, endpoints, Sec Systems, etc.) so that existing vault url and setup could be re-used without the need for any migration.
Thanks,
Nagesh K
12/19/2023 06:48 AM - edited 12/19/2023 06:53 AM
Thank you @NageshK for your prompt response. To address your questions:
Given this information, could you kindly provide guidance on how we can efficiently reuse the credential vault and establish it within our new environment? Your assistance would be greatly appreciated.
Thank you!
12/20/2023 01:24 PM
@thesvg Thanks for the info. If you are not looking to migrate any specific credentials and also not planning to migrate the connections and endpoints, why do you need to reuse the vault from 23.5 version?
Thanks
Nagesh K
12/22/2023 07:54 AM - edited 12/22/2023 08:00 AM
@NageshK thanks for your feedback. I am trying to understand if we need to migrate the vault, at all. Or do we just reuse our current vault url and tokens to establish a new connection. I am assuming the latter from your replies.
01/05/2024 08:38 AM
@thesvg sorry for the dealy in response. Yes, as you do not have anything specific to bring over from existing setup, you can use either the vault that comes with the new EIC setup (23.11 setup). This will be a cleaner implementation.
Thanks,
Nagesh K