- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.
11-18-2024 11:01 AM
Hi Everyone.
Need some help with integration of EVD with Cloud DBs. We are trying to implement EVD to export the data from CyberArk Vault and import that to the Database in Cloud (AWS & Azure)?
We reviewed the CyberArk documentation for EVD implementation, however we didn't find the option to export the data to Cloud Database as the documentation says we have to run the PowerShell script using the same Domain user that has access to Database too. Also CyberArk recommend to run EVD and DB on the same server which is not a great approach when things are moving to the Cloud.
I want to understand how we can upload the data to MS SQL database in AWS RDS with Local DB Cred.
Appreciate if you can point us to the right documentation or provide us steps to do that.
We went through these docs already.
https://community.cyberark.com/s/article/Export-Vault-Data-Quick-Start
https://docs.cyberark.com/pam-self-hosted/14.2/en/content/pas%20inst/evd-install.htm
11-27-2024 07:10 AM
For any advanced configuration of EVD I recommend creating your own scripts that
a) retrieves the relevant datasets to CSV files using EVD, and then
b) uploads the CSV files to tables in your database using an appropriate command-line ETL for the database provider of your choice (eg SQL*Loader for Oracle, BCP utility for MSSQL), and then
c) deletes the CSV files
How you manage the credentials for BCP or SQL*Lite is up to you, really, probably best handled with credential-provider (CP). The builtin SQL import option simply uses BCP and relies on integrated windows credentials afaik, which is why it only works for on-premises SQL servers.
You may find difficulties when the data that EVD pulls contains newline characters, or a mixture of commas and double-quotes (description fields can contain such data, and reason fields). I spent some time designing truly reliable import routines for Oracle or MSSQL, the best tip I would give is to use a multi-character field delimeter such as ##!!## to ensure you get really unique data - but even then I found I sometimes needed to run a bit of code on the CSV files to fix them up before they would reliably import SQL*Loader or BCP - and considering getting a database tech with experience of bulk-imports to get the job done properly.
11-28-2024 05:46 AM
Hi @Vivek Rautela
It seems that Jon Musker provided an answer to your question. Could you kindly let us know if this solution helped?
If so, please mark the answer as 'Select as Best' to assist other community members.
Thank you, Liad
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!

