Manage distributed configuration and secrets with Spring Cloud and Vault
Andreas Falk at Spring I/O 2017
Running multiple instances of microservices as docker images or in the cloud is widely adopted these days.
But what about your configuration and secrets? Do you spread all values using application local property files? Do you still store secrets in clear text?
In case you are encrypting passwords where do you store the key to decrypt these? Do you already rotate database credentials regularly?
In this session you will learn how to externalize your configuration using spring cloud config and store your secrets safely using the recently released spring cloud vault config project.
First I will give you a short demo on how to externalize all your application configuration values to a git repository.
Then after a general introduction into vault you will see how spring cloud vault config facilitates the integration of vault into your application.
After this session you hopefully will be well prepared to start using externalized configuration and to stop ever storing secrets again in an unsafe way.
But what about your configuration and secrets? Do you spread all values using application local property files? Do you still store secrets in clear text?
In case you are encrypting passwords where do you store the key to decrypt these? Do you already rotate database credentials regularly?
In this session you will learn how to externalize your configuration using spring cloud config and store your secrets safely using the recently released spring cloud vault config project.
First I will give you a short demo on how to externalize all your application configuration values to a git repository.
Then after a general introduction into vault you will see how spring cloud vault config facilitates the integration of vault into your application.
After this session you hopefully will be well prepared to start using externalized configuration and to stop ever storing secrets again in an unsafe way.