Secret store components

Dapr integrates with secret stores to provide apps and other components with secure storage and access to secrets such as access keys and passwords. Each secret store component has a name and this name is used when accessing a secret.

As with other building block components, secret store components are extensible and can be found in the components-contrib repo.

The type of secret store is determined by the type field, and things like connection strings and other metadata are put in the section.

Different will have different specific fields that would need to be configured. For example, when configuring a secret store which uses AWS Secrets Manager the file would look like this:

• Kubernetes

To run locally, create a components dir containing the YAML file and provide the path to the command with the flag --components-path.

To deploy in Kubernetes, assuming your component file is named , run: