The Akeyless Dev Hub

If you're looking for help with the only zero-trust, SaaS, unified platform for secrets management - you've come to the right place.

This is our documentation and updates center.

Documentation

Static secrets vs. dynamic secrets

Static SecretsStatic Secrets - A key and value used for access. Akeyless encrypts key values using our patented technology. Static keys can be used to store and manage your passwords, API tokens, SSH keys, and even PII or Credit Card Numbers. are secrets that you create and update manually with values that remain the same through time. Typically, static secrets are used when you want to protect passwords, API tokens, and even personal identifiers (PII) or credit card numbers.

Dynamic SecretsDynamic Secrets - Dynamic secrets are generated every time they are accessed, and so they are safer than static secrets by nature. Once used, the credentials are no longer valid and cannot be reused. This is done by awarding credentials to a [producer](doc:producers) and then applying the producer to a dynamic secret. The dynamic secret exposes temporal credentials to your users when allowed. For different sets of permissions, create different sets of producers and secrets. are secrets that are generated every time they are accessed, using the permissions you've defined in advance. In this way, users can access the configured third-party tool for a temporary period of time with a defined set of permissions. You can create dynamic secrets for third-party tools such as RabbitMQ and AWS and you can configure multiple dynamic secrets for the same tool in order to granularly control the breadth of access enabled as well.

This section describes in detail how to work with:

Updated 2 months ago

Static secrets vs. dynamic secrets


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.