Example: Matching Cloud Secrets to Vault Accounts

The following examples, show the same secrets present on the cloud provider side and in the Vault after a sync run.

AWS

cloudsyncsecret1, cloudtest, and cloudtest2 exist in AWS Secrets Manager (us-east-1) and appear under Vault > Cloud Provider > AWS > us-east-1 with the same names.

Figure – AWS Secrets Manager – Secrets List (us-east-1)

Figure – Vault > Cloud Provider > AWS > us-east-1

Microsoft Azure

azure-secret1, serviceaccount, and test exist in the KronPAMSecretsVault Key Vault and appear under Vault > Cloud Provider > Azure > KronPAMSecretsVault-East US with the same names.

Figure – Azure Key Vault – Secrets List

Figure – Vault > Cloud Provider > Azure > KronPAMSecretsVault-East US

Google Cloud Platform

serviceaccount exists in GCP Secret Manager and appears under Vault > Cloud Provider > GCP > kronpam with the same name.

Figure – GCP Secret Manager – Secret Versions (serviceaccount)

Figure – Vault > Cloud Provider > GCP > kronpam

The Actions menu of a cloud-synced Vault account matches exactly what was described above - only a restricted set of options is available (Permissions, Show Notes, Configure Notifications, Checkout Secret Data, Show Old Secret Data):

Figure – Select Action – Cloud-Synced Vault Account (Azure example)