Reference
Akeyless
Import static secrets from an Akeyless vault. We never write back.
Import static secrets from an Akeyless vault. We never write back.
Connection
| What | This provider |
|---|---|
| Vendor | Akeyless |
| Key | akeyless-secrets |
| Availability | available. You can connect it today. |
| Credential we hold | akeyless-access-key |
| Values read back | yes |
| Activation | immediate |
Directions
| Direction | What it does |
|---|---|
import | We read names and values out of the store into your environment. |
Conflict policies
| Direction | Policies you can pick |
|---|---|
import | skip_existing, new_version, fail |
How syncs work says what each one does.
Connect
Paste a credential from the vendor. We seal it and never show it again.
| Field | Label | Kind | Required | What it is |
|---|---|---|---|---|
accessId | Access ID | secret; we mask it here and seal it | yes | |
accessKey | Access Key | secret; we mask it here and seal it | yes | From an API Key auth method. We trade these for a short-lived token and store none. |
Mapping fields
You answer these once per environment you map.
| Field | Label | Kind | Required | Advanced | What it is |
|---|---|---|---|---|---|
pathPrefix | Item path | text | yes | no | One path per sync. We do not walk subfolders, since two of them can hold one name. |
Required permissions
We probe for these when we verify the connection.
| Permission | Directions | Blocking | Without it |
|---|---|---|---|
list | import | yes | Preview cannot list what is under this path. |
read | import | yes | Import cannot read any values. |