CLI Reference
This section describes the available CLI commands that you can use when working with Akeyless.
If you need help in context, check out the help flag (-h)
General Flags
--profile, --token: Use a specific profile (located at $HOME/.akeyless/profiles) or a temporary access token
--uid-token: The universal identity token, required only for universal_identity authentication
-h, --help: Display help information
--json[=false]: Set the output format to JSON
--jq-expression: Provide a jQuery expression to filter result output
--no-creds-cleanup[=false]: Do not clean local temporary expired credentials
akeyless -h
akeyless <command> -h, --help
akeyless <command> --debugCommands
configure
configureConfigure client profile
For profile creation, default-profile behavior, and precedence rules, see CLI Profiles.
Usage
akeyless configureFlags
--profile[=default]: The profile name to configure
--access-id: Access ID
--access-key: Access Key
--access-type[=access_key]: Access Type, options: [access_key/password/azure_ad/saml/oidc/aws_iam/gcp/k8s/cert/oci/kerberos]
--admin-password: Password (relevant only for access-type=password)
--admin-email: Email (relevant only for access-type=password)
--account-id: Account ID (relevant only for access-type=password where the email address is associated with more than one account)
--oidc-sp: OIDC Service Provider (relevant only for access-type=oidc, inferred if empty), supported SPs: google, github
--azure-ad-object-id: Azure Active Directory ObjectId (relevant only for access-type=azure_ad)
--azure-cloud[=AzureCloud]: Azure cloud environment to use. Values: AzureCloud (default), AzureUSGovernment, AzureChinaCloud (relevant only for access-type=azure_ad)
--gcp-audience: GCP audience to use in signed JWT (relevant only for access-type=gcp)
--gateway-url: Default Gateway URL used for API calls
--k8s-auth-config-name: The Kubernetes Auth config name (relevant only for access-type=k8s)
--k8s-token-path[=/var/run/secrets/kubernetes.io/serviceaccount/token]: An optional path to a projected service account token inside the pod, for use instead of the default service account token (relevant only for access-type=k8s)
--cert-file-name: Name of the certificate file to use (relevant only for access-type=cert)
--cert-data: Certificate data encoded in Base64. Used if file was not provided (relevant only for access-type=cert in Curl Context)
--key-file-name: Name of the private key file to use (relevant only for access-type=cert)
--key-data: Private key data encoded in Base64. Used if file was not provided (relevant only for access-type=cert in Curl Context)
--cert-issuer-name: Certificate Issuer Name
--cert-username: The username to sign in the SSH certificate (use a comma-separated list for more than one username)
--public-key-file-path: Path to a file from which the identity (private key) for public key authentication is read
--oci-auth-type[=apikey]: The type of OCI configuration to use, options: [instance/apikey/resource] (relevant only for access-type=oci)
--oci-group-ocid: A list of Oracle Cloud IDs groups (relevant only for access-type=oci)
--default-location-prefix: Default path prefix for item, target, and auth method names
--legacy-signing-alg-name: Set this option to output legacy ([email protected]) signing algorithm name in the certificate
--krb5conf-file-path: Path to a valid krb5.conf file specifying the settings and parameters required for Kerberos authentication (relevant only for access-type=kerberos)
--krb5conf-file-data: Base64-encoded content of a valid krb5.conf file (relevant only for access-type=kerberos in Curl Context)
--keytab-file-path: Path to a valid keytab file containing the user entry (relevant only for access-type=kerberos)
--keytab-file-data: Base64-encoded content of a valid keytab file (relevant only for access-type=kerberos in Curl Context)
--disable-kerberos-fast[=true]: Disable the Kerberos FAST negotiation (relevant only for access-type=kerberos)
--gateway-spn: Optional, the service principal name of the gateway as registered in LDAP (for example, HTTP/gateway) (relevant only for access-type=kerberos)
--kerberos-token: Optional, Kerberos token for the gateway SPN, used by SPNEGO for authentication (relevant only for access-type=kerberos)
--kerberos-username: Optional, the username for the entry within the keytab to authenticate via Kerberos (relevant only for access-type=kerberos)
delete-item
delete-itemDelete an item or an item version
Usage
akeyless delete-item -n <Item name>Flags
-n, --name: Required, Item name
--version[=-1]: The specific version you want to delete - 0=last version, -1=entire item with all versions (default)
--delete-in-days: The number of days to wait before deleting the item (relevant for keys only)
--delete-immediately[=false]: When delete-in-days=-1, must be set
--accessibility[=regular]: For an item in a user's personal folder [regular/personal]
delete-items
delete-itemsDeletes multiple items from a given path
Usage
akeyless delete-items -p <Path\do\delete\items>Flags
-p, --path: Required, Path to delete the items from
describe-item
describe-itemGets the item details
Flags
-n, --name: Item name
-d, --display-id: The display ID of the item
-I, --item-id: Item ID of the item
--show-versions[=false]: Include all item versions in reply
--gateway-details[=false]: Output will include additional gateway details (For example, cluster URL)
--bastion-details[=false]: Output will include additional bastion details
--services-details[=false]: Include all associated services details
--accessibility[=regular]: For an item in a user's personal folder [regular/personal]
Output
With only --name specified, the command returns all details about the specified item except for its version.
When a version number is specified, the command returns all details about the specified item for the specified version.
When --show-versions is specified, the command returns all details about the specified item including a full list of versions, their creation dates, and their encryption keys for any version for which a key other than the default was used.
get-account-settings
get-account-settingsGet the settings of the account
get-cloud-identity
get-cloud-identityGet a Cloud Identity token.
Usage
akeyless get-cloud-identity --cloud-provider <cloud provider>Flags
--cloud-provider: Cloud provider (azure_ad/aws_iam/gcp/oci)
--azure_ad_object_id: Azure Active Directory ObjectId (relevant only for cloud-provider=azure_ad)
--azure-cloud[=AzureCloud]: Azure cloud environment to use. Values: AzureCloud (default), AzureUSGovernment, AzureChinaCloud
--gcp-audience[=akeyless.io]: GCP audience to use in signed JWT (relevant only for cloud-provider=gcp)
--oci-auth-type[=apikey]: The type of the OCI configuration to use [instance/apikey/resource] (relevant only for cloud-provider=oci)
--oci-group-ocid: A list of required groups OCIDs (relevant only for cloud-provider=oci)
--describe-sub-claims: Describe the cloud identity sub-claims
--url_safe: Escapes the token so it can be safely placed inside a URL query
--debug[=false]: Turn on debug logging
For broader authentication context, see CLI Reference - Authentication.
get-default-profile
get-default-profileDisplay current default profile information.
For default-profile behavior and precedence, see CLI Profiles.
Usage
akeyless get-default-profileFlags
--profile, --token: Use a specific profile (located at $HOME/.akeyless/profiles) or a temporary access token
--uid-token: The universal identity token (required only for universal_identity authentication)
--json[=false]: Set output format to JSON
--jq-expression: JQ expression to filter result output
--no-creds-cleanup[=false]: Do not clean local temporary expired credentials
get-tags
get-tagsGet all tags of selected item
Usage
akeyless get-tags --name <Item Name>Flags
-n, --name: Required, The item name
list-items
list-itemsList of all accessible items
Flags
-t, --type: The item types list of the requested items. If it is empty, all item types are returned, options: [key, static-secret, dynamic-secret, rotated-secret, ssh-cert-issuer, pki-cert-issuer, classic-key]
--sub-types: Optional the items sub types
--filter: Filter by item name or part of it
--tag: Filter by item tag
--sra-only[=false]: Filter by items with SRA functionality enabled
--advanced-filter: Filter by item name, username, website, or part of it
--ara-only[=false]: Filter by items with Agentic Runtime Authority functionality enabled
--current-folder[=false]: List only items in the current folder (excludes subfolders)
--modified-after: List only secrets modified after the specified date (in Unix time)
--path: Path to folder
--pagination-token: Next page reference
--auto-pagination[=enabled]: Retrieve all items using pagination, when disabled retrieving only first 1000 items
--minimal-view: Show only basic information of the items
--accessibility[=regular]: For an item in a user's personal folder, options: [regular/personal]
list-sra-bastions
list-sra-bastionsLists all Secure Remote Access (SRA) bastions in the account.
For command usage, flags, and behavior notes, see CLI Reference - Gateway Secure Remote Access.
move-objects
move-objectsMoves or renames folders and their contents in bulk. Both --source and --target must be folder paths. This command does not move an individual object.
Usage
akeyless move-objects --source <Source path to move the objects from> \
--target <Target path to move the objects to> \
--objects-type <The objects type to move (item/auth_method/role)>Flags
-s, --source: Required, Source path to move the objects from
-t, --target: Required, Target path to move the objects to
-o, --objects-type[=item]: The objects type to move (item/auth_method/role)
mcp
mcpStarts the general Akeyless MCP server so MCP-compatible AI clients can interact with Akeyless tools.
Usage
akeyless mcp \
--gateway-url https://<your-gateway-url>:8000/api/v2 \
--profile <profile-name>Flags
--gateway-url: Required, Gateway URL
--profile: Use an existing CLI profile
--access-type: Authentication method when not using --profile, options: [access_key/password/saml/ldap/k8s/azure_ad/oidc/aws_iam/universal_identity/jwt/gcp/cert/oci/kerberos]
--access-id: Access ID for the selected authentication method
--access-key: Access Key (relevant for access-type=access_key)
For MCP concepts and integration setup, see MCPs.
mcp-runtime-authority
mcp-runtime-authorityStarts the MCP server for Agentic Runtime Authority runtime-query tools.
Usage
akeyless mcp-runtime-authority \
--gateway-url https://<your-gateway-url>:8000 \
--secret-name /demo/apps/analytics/postgres-ro \
--profile <profile-name>Flags
--gateway-url: Required, Gateway URL
--secret-name: Optional default secret path for database query workflows
--profile: Use an existing CLI profile
--access-type: Authentication method when not using --profile, options: [access_key/password/saml/ldap/k8s/azure_ad/oidc/aws_iam/universal_identity/jwt/gcp/cert/oci/kerberos]
--access-id: Access ID for the selected authentication method
--access-key: Access Key (relevant for access-type=access_key)
For Runtime Authority behavior and workflow context, see Agentic Runtime Authority.
set-item-state
set-item-stateSet an item's state (Enabled, Disabled)
Usage
akeyless set-item-state --name <Current item name> \
--desired-state <Desired item state [Enabled, Disabled]>Flags
-n, --name: Required, Current item name
-s, --desired-state: Required, Desired item state
set-default-profile
set-default-profileSet the default profile for CLI commands.
This command sets the default profile used when --profile is not specified and persists the value in ~/.akeyless/settings.
For default-profile behavior and precedence, see CLI Profiles.
Usage
akeyless set-default-profile --profile <Profile name>Flags
--profile: The profile name to set as default
--json[=false]: Set output format to JSON
--jq-expression: JQ expression to filter result output
--no-creds-cleanup[=false]: Do not clean local temporary expired credentials
runtime-authority
runtime-authorityExecute a target query or service action through the Gateway runtime authority endpoint.
Usage
akeyless runtime-authority \
--name /demo/apps/analytics/postgres-ro \
--payload 'SELECT current_user, current_database();' \
--agent-id ai-assistant-01 \
--gateway-url https://<your-gateway-url>:8000 \
--profile <profile-name>Flags
-n, --name: Required, Full path of the Akeyless secret (dynamic or rotated)
--payload: Required, Query or action to run (for example SQL or aws s3 ls)
--agent-id: Required, Agent identifier for auditing
-u, --gateway-url: Required, Gateway URL
--profile: Use an existing CLI profile
unconfigure
unconfigureRemove configuration of client profile
Usage
akeyless unconfigure --profile <Profile name>update
updateUpdate the Akeyless CLI version or change to a prior version
Usage
akeyless updateFlags
-v, --version[=latest]: Provide the CLI version to update to, by default, the latest version is used
-s, --show-changelog: Show the changelog between the current version and the latest version
-r, --artifact-repository: Alternative CLI repository URL, for example, https://artifacts.site2.akeyless.io
update-account-settings
update-account-settingsUpdates account settings.
Note: The operation is allowed only for admin user
Flags
--company-name: Update Company Name of account
--phone: Update Phone number of account
--address: Update Address of account
--city: Update City of account
--country: Update Country of account
--postal-code: Update Postal Code of account
--jwt-ttl-default: default JWT TTL for Auth Method authentication (in minutes)
--jwt-ttl-min: minimum allowed JWT TTL for Auth Method authentication (in minutes)
--jwt-ttl-max: maximum allowed JWT TTL for Auth Method authentication (in minutes)
--max-versions: Maximum versions of a given item-type, valid range [1, 300]. When item version exceeds this number, the oldest versions will be deleted
--item-type: Associated with max-versions
--default-versioning: If set to true, new item version will be created on each update
--force-new-versions: If set to true, new version will be created on update
--dp-enable-classic-key-protection: Set to update protection with classic keys state meter
--default-sharing-link-ttl: Set to update the default TTL in minutes for sharing item, number between 60 min to 30 days (43200 minute)
--password-policy-password-length: "13-1": "Password length between 5 - to 50 characters
--password-policy-contains-capital-letters: Password must contain capital letters
--password-policy-contains-lower-letters: Password must contain lower case letters
--password-policy-contains-numbers: Password must contain numbers
--password-policy-contains-special-characters: Password must contain special characters
--items-deletion-protection: Set to update the default behavior of new items creations deletion protection attribute [true/false]
--default-key-name: Set the account default key based on the DFC key item name. Use "set-original-akeyless-default-key" to revert to using the original default key of the account. Empty string will change nothing
--invalid-characters[=notReceivedInvalidCharacter]: Characters that cannot be used for items/targets/roles/auths/event_forwarder names
--lock-default-key: Lock the account's default protection key, if set - users will not be able to use a different protection key, relevant only if default-key-name is configured [true/false]
--usage-event-enable: Enable event for objects that have not been used or changed [true/false]
--usage-event-object-type: Usage event is supported for Auth Method or secrets-and-keys [auth/item]
--usage-event-interval: Interval by days for unused objects. Default and minimum interval is 90 days
--dynamic-secret-max-ttl-enable: Set a maximum TTL for Dynamic Secrets [true/false]
--dynamic-secret-max-ttl: Set the maximum TTL for Dynamic Secrets
--max-rotation-interval-enable: Set a maximum rotation interval for Rotated Secrets auto rotation settings [true/false]
--max-rotation-interval: Set the maximum rotation interval for Rotated Secrets auto rotation settings
--bound-ips: A default list of comma-separated CIDR block that are allowed to authenticate
--lock-bound-ips: Lock bound-ips setting globally in the account
--gw-bound-ips: A default list of comma-separated CIDR block that acts as a trusted Gateway entity
--lock-gw-bound-ips: Lock bound-ips setting globally in the account
--enable-password-expiration: Enable password expiration policy [true/false]
--password-expiration-days: Specifies the number of days that a password is valid before it must be changed. A default value of 90 days is used
--password-expiration-notification-days: Specifies the number of days before a user receives notification that their password will expire. A default value of 14 days is used
--hide-personal-folder: Controls the visibility of the personal folder, this setting hides the personal folder for users.
--hide-static-password: Hide static secret's password type [true/false].
--enable-default-certificate-expiration-event: Enable how many days before the expiration of the certificate would you like to be notified. [true/false].
--default-certificate-expiration-notification-days: How many days before the expiration of the certificate would you like to be notified. To specify multiple events, use argument multiple times: --default-certificate-expiration-notification-days 1, --default-certificate-expiration-notification-days 5.
--allowed-email-domains: Limits email sharing to the specified domains. Relevant only when item sharing is enabled. By default, all domains are allowed.
--enable-ai-insights: Enable AI insights [true/false]
--enable-item-sharing: Enable sharing items [true/false]
--item-locking-enabled: Enable item locking feature [true/false]
--lock-allowed-client-type: Lock the allowed-client-type setting in the account [true/false]
--lock-max-ttl: Set the maximum TTL for item and target locks in minutes
update-item
update-itemUpdate item name and description
Critical:
Secret versioning
No updates made with
update-itemcan be saved as part of new versions, which means that these changes override existing data. If you wish to track these updates as part of secret versioning, first create a new version withupdate-version-val. You can create a new version value using the same value for the current version if you don't want to actually change the value. Thereafter, runupdate-item.
Usage
akeyless update-item --name <Item name> \
--new-name <New item name>Flags
-n, --name: Required, Current item name
--new-name: New item name
--description[=default_metadata]: Description of the object
--add-tag: List of new tags to attach to this item. To specify multiple tags, repeat the flag: --add-tag Tag1 --add-tag Tag2
--rm-tag: List of existing tags to remove from this item. To specify multiple tags, repeat the flag: --rm-tag Tag1 --rm-tag Tag2
--max-versions: Set the maximum number of versions, limited by account settings defaults
--secure-access-enable: Enable or disable Secure Remote Access [true/false]
--secure-access-certificate-issuer: Path to the SSH Certificate Issuer for Akeyless Secure Access
--secure-access-api: Secure Access SSH control API endpoint, for example https://my.sra-server:9900 (relevant only for SSH cert issuer)
--secure-access-ssh: Secure Access SSH server, for example my.sra-server:22 (relevant only for SSH cert issuer)
--secure-access-ssh-creds-user: SSH username used to connect to target server, and must be in the allowed users list (relevant only for SSH cert issuer)
--secure-access-use-internal-ssh-access: Use internal SSH access
--secure-access-ssh-creds: Secret values that contain SSH credentials, either private key or password [password/private-key] (relevant only for Static Secret or Rotated Secret)
--secure-access-host: Target servers for connections. To specify multiple hosts, repeat this flag
--secure-access-add-host: List of new hosts to attach to SRA servers host. To specify multiple hosts, repeat the flag: --secure-access-add-host host1 --secure-access-add-host host2
--secure-access-rm-host: List of existing hosts to remove from SRA servers host. To specify multiple hosts, repeat the flag: --secure-access-rm-host host1 --secure-access-rm-host host2
--secure-access-url: Destination URL to inject secrets
--secure-access-web-browsing[=false]: Secure browser via Akeyless Secure Remote Access (SRA)
--secure-access-web-proxy[=false]: Web proxy via Akeyless Secure Remote Access (SRA)
--secure-access-rdp-domain: Required when the Dynamic Secret is used for a domain user (relevant only for RDP Dynamic Secret)
--secure-access-rdp-user: Override the RDP domain username
--secure-access-rd-gateway-server: RD Gateway server (relevant only for RDP)
--secure-access-allow-external-user: Allow providing an external user for domain users [true/false]
--secure-access-db-schema: DB schema (relevant only for DB Dynamic Secret)
--secure-access-db-name: DB name (relevant only for DB)
--secure-access-aws-account-id: AWS account ID (relevant only for AWS)
--secure-access-aws-region: AWS region (relevant only for AWS)
--secure-access-aws-native-cli: AWS native CLI (relevant only for AWS)
--secure-access-cluster-endpoint: Kubernetes cluster endpoint URL (relevant only for EKS/GKE/K8s Dynamic Secret)
--secure-access-dashboard-url: Kubernetes dashboard URL (relevant only for Kubernetes)
--secure-access-allow-port-forwading: Enable port forwarding when using CLI access (relevant only for EKS/GKE/K8s Dynamic Secret)
--host-provider: Host provider type [explicit/target] (relevant only for Secure Remote Access of SSH cert issuer, LDAP rotated secret, and LDAP dynamic secret)
--secure-access-gateway: Defines which Gateway (Gateway URL) is related to a secret item
--rotate-after-disconnect[=false]: Post-session rotation policy for SRA [use false to disable rotation, true or 0 for immediate rotation at disconnect, or a positive integer N to delay rotation by N minutes]
Examples: --rotate-after-disconnect true, --rotate-after-disconnect 0, --rotate-after-disconnect 15
--change-event: Trigger an event when a secret value changes [true/false] (relevant only for Static Secret)
-e, --expiration-event-in: Number of days before certificate expiration to notify. To specify multiple events, repeat the flag: --expiration-event-in 1 --expiration-event-in 5
-c, --cert-file-path: Path to a file containing the certificate in PEM format. Used for updating RSA keys certificates
--cert-file-data: PEM certificate in Base64 format. Used for updating RSA keys certificates
--certificate-format: Format of the returned certificate [pem/der]
--item-custom-fields: Additional custom fields to associate with the item. To specify multiple fields, repeat the flag: --item-custom-fields field1=value1 --item-custom-fields field2=value2
--gcp-sm-regions: GCP Secret Manager regions for regional secrets (comma-separated). USC with GCP targets only
--lock-during-sra-session: Lock this secret for read and update while an SRA session is active
--usc-tags: Comma-separated list of tags to apply to all secrets created or synced on the remote Universal Secrets Connector (USC) (USC items only)
--use-tags-as-filter: Whether to filter the USC secret list using the specified usc-tags values [true/false] (USC items only)
--accessibility[=regular]: For an item in a user's personal folder [regular/personal]
--delete-protection: Protection from accidental deletion of this object [true/false]
folder management
folder managementCommands for managing folders in the account
folder create
folder createCreates a new folder
Usage
akeyless folder create \
--name <Folder Name> \
--type[=items] <Folder Type> \
--accessibility[=regular] <[regular/personal]>folder update
folder updateUpdates a new folder
Usage
akeyless folder update \
--name <Folder Name> \
--type[=items] <Folder Type> \
--accessibility[=regular] <[regular/personal]>folder get
folder getGet information of a folder
Usage
akeyless folder get \
--name <Folder Name> \
--type[=items] <Folder Type> \
--accessibility[=regular] <[regular/personal]>folder delete
folder deleteDeletes a new folder
Usage
akeyless folder delete \
--name <Folder Name> \
--type[=items] <Folder Type> \
--accessibility[=regular] <[regular/personal]>CLI Agent
agent start
agent startStart Akeyless Agent
Accepted alias: agent-start.
Usage
akeyless agent startFlags
-f, --config-file-path: The path to the agent config file
agent status
agent statusGet Akeyless Agent status
Accepted alias: agent-status.
Usage
akeyless agent statusagent stop
agent stopStop Akeyless Agent
Accepted alias: agent-stop.
Usage
akeyless agent stopaccount-custom-field
account-custom-fieldCommands to interact with custom fields.
Subcommands
create
delete
get
list
update
account-custom-field create
account-custom-field createCreate a new custom field in the account.
Accepted alias: account-custom-field-create.
Usage
akeyless account-custom-field create \
--object-type <Object type> \
--name <Custom field name> \
--required[=false]Flags
-o, --object[=ITEM]: The object to create the custom field for
-t, --object-type: Required, The object type to create the custom field for, for example STATIC_SECRET, DYNAMIC_SECRET, or ROTATED_SECRET
-n, --name: Required, Custom field name
-r, --required[=false]: Specify whether the custom field is mandatory
account-custom-field delete
account-custom-field deleteDelete a custom field from the account.
Accepted alias: account-custom-field-delete.
Usage
akeyless account-custom-field delete \
--id <Custom field ID>Flags
-i, --id: Required, Custom field ID
account-custom-field get
account-custom-field getRetrieve a custom field.
Accepted alias: account-custom-field-get.
Usage
akeyless account-custom-field get \
--id <Custom field ID>Flags
-i, --id: Required, Custom field ID
account-custom-field list
account-custom-field listRetrieve a list of custom fields in the account.
Accepted alias: account-custom-field-list.
Usage
akeyless account-custom-field list \
--object <Object type> \
--object-type <Custom field object type>Flags
-o, --object: Filter by object
-t, --object-type: Filter by object type
account-custom-field update
account-custom-field updateUpdate an existing custom field in the account.
Accepted alias: account-custom-field-update.
Usage
akeyless account-custom-field update \
--id <Custom field ID> \
--name <New custom field name> \
--required[=false]Flags
-i, --id: Required, Custom field ID
-n, --name: New custom field name
-r, --required[=false]: Specify whether the custom field is mandatory
Group Management
Commands for creating, viewing, listing, and updating groups.
create-group
create-groupCreate a new group.
Group names must start with /, must not end with /, and cannot contain *. Group aliases cannot contain *, /, +, ?, or .. The command also requires a non-empty user-assignment payload supplied with --user-assignment or --user-assignment-file.
Usage
akeyless create-group \
--name <Group name> \
--group-alias <Group alias> \
--user-assignment <User assignment JSON>Flags
-n, --name: Required, Group name
-g, --group-alias: Required, Short group alias
--description: Description of the object
-u, --user-assignment: Required, JSON string defining the user assignment for this group. Must contain at least one element
-f, --user-assignment-file: Path to a file containing the user-assignment JSON. Provide this instead of --user-assignment
delete-group
delete-groupDelete a group.
Usage
akeyless delete-group \
--name <Group name>Flags
-n, --name: Required, Group name
get-group
get-groupReturn information about a group.
Usage
akeyless get-group \
--name <Group name>Flags
-n, --name: Required, Group name
list-groups
list-groupsList groups.
Usage
akeyless list-groupsFlags
--filter: Filter by group name or part of it
--pagination-token: Next page reference
update-group
update-groupUpdate a group.
The existing --name value and any --new-name value must follow the same group-name rules as create-group. This command also requires a non-empty user-assignment payload supplied with --user-assignment or --user-assignment-file.
Usage
akeyless update-group \
--name <Group name> \
--group-alias <Group alias> \
--user-assignment <User assignment JSON>Flags
-n, --name: Required, Group name
--new-name: New group name
-g, --group-alias: Required, Short group alias
--description: Description of the object
-u, --user-assignment: Required, JSON string defining the user assignment for this group. Must contain at least one element
-f, --user-assignment-file: Path to a file containing the user-assignment JSON. Provide this instead of --user-assignment
OIDC Applications
Commands for creating and updating OIDC applications and rotating their client secrets.
create-oidc-app
create-oidc-appCreate a new OIDC application.
This command requires a non-empty permission-assignment payload supplied with --permission-assignment or --permission-assignment-file.
Usage
akeyless create-oidc-app \
--name <OIDC application name> \
--redirect-uris <Comma-separated redirect URIs> \
--permission-assignment <Permission assignment JSON>Flags
-n, --name: Required, OIDC application name
-r, --redirect-uris: Comma-separated list of allowed redirect URIs
-s, --scopes[=openid]: Comma-separated list of allowed scopes
-a, --audience: Comma-separated list of allowed audiences
--public: Set this flag if the app is public and cannot keep secrets
-p, --permission-assignment: Required unless --permission-assignment-file is provided. JSON string defining the permission assignment for this app. Must contain at least one element
-f, --permission-assignment-file: Required unless --permission-assignment is provided. Path to a file containing the permission-assignment JSON
--item-custom-fields: Additional custom fields to associate with the item. Repeat the flag to add multiple fields
-t, --tag: Add tags attached to this object. Repeat the flag to add multiple tags
-k, --key: Key used to encrypt the OIDC application
--description: Description of the object
--accessibility[=regular]: Accessibility for an item in a user's personal folder [regular/personal]
--delete-protection: Protection from accidental deletion of this object [true/false]
rotate-oidc-client-secret
rotate-oidc-client-secretRotate an OIDC client secret.
Usage
akeyless rotate-oidc-client-secret \
--name <OIDC application name>Flags
-n, --name: Required, OIDC application name
update-oidc-app
update-oidc-appUpdate an existing OIDC application.
This command requires a non-empty permission-assignment payload supplied with --permission-assignment or --permission-assignment-file.
Usage
akeyless update-oidc-app \
--name <OIDC application name> \
--redirect-uris <Comma-separated redirect URIs> \
--permission-assignment <Permission assignment JSON>Flags
-n, --name: Required, OIDC application name
-r, --redirect-uris: Comma-separated list of allowed redirect URIs
-s, --scopes[=openid]: Comma-separated list of allowed scopes
-a, --audience: Comma-separated list of allowed audiences
--public: Set this flag if the app is public and cannot keep secrets
-p, --permission-assignment: Required unless --permission-assignment-file is provided. JSON string defining the permission assignment for this app. Must contain at least one element
-f, --permission-assignment-file: Required unless --permission-assignment is provided. Path to a file containing the permission-assignment JSON
-k, --key: Key used to encrypt the OIDC application
policy
policyCommands to manage account policies.
Subcommands
create
delete
get
list
update
policy create
policy createCommand to create a policy in the account.
Subcommands
keys
policy create keys
policy create keysCreate a new keys policy.
Provide at least one configuration flag in addition to --path. --allowed-key-types and --allowed-key-names are mutually exclusive. If you set --object-types targets, do not also set --max-rotation-interval-days or --allowed-algorithms. When --object-types is omitted, the policy applies to both items and targets.
Usage
akeyless policy create keys \
--path <Policy path>Flags
-p, --path: Required, The path the policy refers to
--max-rotation-interval-days: Maximum automatic key-rotation interval
--allowed-algorithms: Allowed key algorithms, for example RSA2048,AES128GCM
--allowed-key-types: Allowed key protection types, dfc or classic-key
--allowed-key-names: Allowed protection key names. Use default-account-key to enforce the account default protection key
-t, --object-types: Object types this policy applies to, items or targets
policy delete
policy deleteDelete an account policy by ID.
Usage
akeyless policy delete \
--id <Policy ID>Flags
-i, --id: Required, Policy ID
policy get
policy getRetrieve an account policy by ID.
Usage
akeyless policy get \
--id <Policy ID>Flags
-i, --id: Required, Policy ID
policy list
policy listList account policies.
Usage
akeyless policy listFlags
--paths: Filter by exact policy paths
--types: Filter by policy types
--object-type: Filter by object types, items or targets
--aggregate: Aggregate missing configurations from parent policies. Requires --paths
policy update
policy updateUpdate an existing account policy.
Subcommands
keys
policy update keys
policy update keysUpdate an existing keys policy.
Provide at least one update flag. --allowed-key-types and --allowed-key-names are mutually exclusive. If you set --object-types targets, do not also set --max-rotation-interval-days or --allowed-algorithms.
Usage
akeyless policy update keys \
--id <Policy ID>Flags
-i, --id: Required, Policy ID
-p, --path: New policy path
--max-rotation-interval-days: Maximum automatic key-rotation interval
--allowed-algorithms: Allowed key algorithms, for example RSA2048,AES128GCM
--allowed-key-types: Allowed key protection types, dfc or classic-key
--allowed-key-names: Allowed protection key names. Use default-account-key to enforce the account default protection key
-t, --object-types: Object types this policy applies to, items or targets
delete-personal-folder
delete-personal-folderDelete a personal folder.
Usage
akeyless delete-personal-folder \
--unique-id <Account unique ID>Flags
--unique-id: Unique identifier of the account whose personal folder is to be deleted
--access-id: Access ID of the user whose personal folder is targeted for deletion by an administrator
get-analytics-data
get-analytics-dataGet analytics and usage report data for the authenticated account.
Analytics data is generated asynchronously, so recent activity may take time to appear in the report.
Usage
akeyless get-analytics-dataOutput
Returns analytics and usage report data, including:
date_updatedanalytics_datausage_reportsclients_usage_reports
For operation-level response schema details, see Get analytics data.
Flags
This command does not define command-specific flags beyond the global CLI flags shown above.
Run akeyless get-analytics-data --help to see available options.
kubeconfig-generate
kubeconfig-generateGenerate a unified kubeconfig for Kubernetes Dynamic Secrets.
Provide exactly one selector mode: --name or --tag. If you use --tag, only one tag value is supported.
Usage
akeyless kubeconfig-generate \
--name <Dynamic secret name> \
--out <Output file path>Flags
-n, --name: Dynamic secret name. Repeat the flag to include multiple dynamic secrets
-t, --tag: Tag attached to the Dynamic Secret. At present, only one tag is supported
-o, --out[=kubeconfig.json]: Kubeconfig output file path
lock-item
lock-itemLock a static secret item.
Usage
akeyless lock-item \
--name <Item name>Flags
--name: Required, Item name
--lock-ttl[=60]: Lock time to live in minutes
--actions[=update,read]: Comma-separated blocked actions
unlock-item
unlock-itemUnlock a static secret item.
Usage
akeyless unlock-item \
--name <Item name>Flags
-n, --name: Required, Item name
