Configuring Hashicorp Vault Instance for storing Secrets

• Overview
• Prerequisites

Overview

The VDK Control Service allows for the optional configuration of a Hashicorp Vault instance for storing secrets. This allows data jobs users to store sensitive data encrypted in Vault, rather than using properties which are stored in plain text in the VDK Control Service database.

As part of this tutorial you will learn how to configure the VDK Control Service to use Hashicorp Vault to store Secrets. This is a two step process:

• configuring AppRoles in Hashicorp vault and obtaining the required configuration
• configuration changes in the VDK Control Service

Who is this article for?

This article is for VDK Control Service Infrastructure Operators.

Estimated Time Commitment

If you have running instances of the VDK Control Service and Hashicorp Vault, the completion of this tutorial should take 15 to 30 minutes.

Prerequisites

1. A VDK Control Service installation Install VDK Control Service with custom SDK
2. A running instance of Hashicorp Vault

[ Edit: First step ]

[ Edit: When asking users to carry out a step, explain the reasoning behind the action and the expected result. ]

[ Edit: Part 1 ]

[ Edit: Part one instructions. ]

[ Edit: Part 2 ]

[ Edit: Part two instructions. ]

Tip: [ If applicable: place your tip here or anywhere else ]

[ Edit: Second Step ]

[ Edit: Explain the reasoning and expected result. ]

[ Edit if applicable: Part 1 ]

[ Edit if applicable: instructions ]

Wrap-up

[ Edit: Congratulations on completing this tutorial! (Edit this part as you feel, with your free-form congrats sentence) ]

Conclusion

[ Edit: Summarize important lessons you'd like users to take away from the tutorial. ]

What's Next?

[ Edit: Help users along their journey by providing the next steps - these might be recommended reading, supplementary resources, or even another tutorial. ]

Checklist before publishing

• I have read the Versatile Data Kit Tutorial guidelines.
• Is the goal clear and can be found within the first 30 seconds of opening your tutorial?
• Are the steps clear and actionable for accomplishing the task your reader needed help with?
• Is it possible to complete your tutorial within 15-30 minutes?
• Do you have at least 1-2 images/visuals/media in your tutorial?
• Did you spell-check and proofread? Grammarly
• Is it easy to read? Hemingway. Quillbot is good for fluency and paraphrasing.
• Did you check and fix the accessibility issues? WAVE
• Is there a Call to Action / Next Steps?
• Test with a user if the tutorial is understandable - if applicable and if possible