Manage secrets for apps in Azure Spring Cloud with Key Vault
summary
A concrete path for secrets emerges: use Azure Key Vault Secret Spring Boot starter, add the starter to the pom, push nonsecrets to the Spring Cloud config server, put DB credentials (database name login password server full name) into Azure Key Vault, enable a system managed identity, set access policies and supply the Key Vault URI as a profile. Demo uses Azure Spring Cloud hosting a pet‑clinic app and a MySQL server behind an API gateway and shows the app exposes no secrets yet still connects successfully.
AI-written summary · about
chapters (7)
- 0:00Start
- 0:20Managing Secrets in Azure Key Vault
- 1:32Reason Why You Would Use Secrets
- 2:23Demo
- 2:44Azure Key Vault
- 5:10Application Properties
- 7:31Azure Key Vault Uri
related talks
47mManaging your Secrets in a Cloud Environment
51mManage Distributed Configuration and Secrets with Spring Cloud and Vault
36mManage Distributed Secrets in Applications on Cloud Foundry With Spring Cloud Vault
10mCan you keep it a secret?
42mSpring Vault - managing secrets at scale
53mSecuring Spring Applications with Hashicorp Vault
47mThe Secret to Handling Dynamic Secrets
52mManaging Spring Boot Application Secrets