The AWS secrets engine generates AWS access credentials dynamically based on
IAM policies.

Reference: https://www.vaultproject.io/api-docs/secret/aws

The database secrets engine is used to manage dynamically-issued credentials
for users of a database backend such as mysql, postgresql, mongodb, etc. The
vault server uses a privileged 'root' user to create new users with randomized
passwords on-demand for callers.

Reference: https://www.vaultproject.io/api-docs/secret/databases

The kv secrets engine is used to store arbitrary secrets within the
configured physical storage for Vault. Writing to a key in the kv-v1 backend
will replace the old value; sub-fields are not merged together.

Reference: https://www.vaultproject.io/api-docs/secret/kv/kv-v1

The kv secrets engine is used to store arbitrary secrets within the
configured physical storage for Vault. Writing to a key in the kv-v1 backend
will replace the old value; sub-fields are not merged together.

Reference: https://www.vaultproject.io/api-docs/secret/kv/kv-v1

The transit secrets engine handles cryptographic functions on data
in-transit. It can also be viewed as "cryptography as a service" or
"encryption as a service". The transit secrets engine can also sign and
verify data; generate hashes and HMACs of data; and act as a source of random
bytes.

Reference: https://www.vaultproject.io/api-docs/secret/transit