Multi-Target Classic Key Provisioning
Overview
This feature allows a single Akeyless Classic Key to be provisioned and managed centrally while being simultaneously mapped to multiple external KMS across different cloud environments.
Provisioning via CLI
Multi-target provisioning workflow can also be performed using the Akeyless CLI. Using the CLI, a single Classic Key can be associated with multiple external targets by repeating the target association step.
Step 1: Create a Classic Key
akeyless create-classic-key \
--name my-shared-key \
--alg AES256GCMStep 2: Create External Targets
AWS KMS Target
akeyless target-create-aws \
--name aws-kms-target \
--access-key-id <ACCESS_KEY_ID> \
--access-key <ACCESS_KEY>Azure Key Vault Target
akeyless target-create-azure-kv \
--name azure-kv-target \
--tenant-id <TENANT_ID> \
--client-id <CLIENT_ID> \
--client-secret <CLIENT_SECRET> \
--vault-name <KEY_VAULT_NAME>GCP KMS Target
akeyless target-create-gcp \
--name gcp-kms-target \
--project-id <GCP_PROJECT_ID> \
--location <LOCATION> \
--key-ring <KEY_RING> \
--service-account-key <SERVICE_ACCOUNT_JSON>Step 3: Associate the Same Classic Key with Each Target
akeyless assoc-target-item \
--name my-shared-key \
--target-name aws-kms-target
akeyless assoc-target-item \
--name my-shared-key \
--target-name azure-kv-target
akeyless assoc-target-item \
--name my-shared-key \
--target-name gcp-kms-targetProvisioning via Console
Step 1: Create or Select a Classic Key
- In the Akeyless Console, navigate to Items
- Create a new Classic Key or select an existing one
- Open the key to view its details
Step 2: Open the Provisioning Tab
- Inside the Classic Key view, navigate to the Provisioning tab
- This tab displays all external targets currently attached to the key
Step 3: Attach an External Target
- Click Attach
- Enter the External Key Name
- This is the key name that will be created in the external KMS
- Each target may use a different external key name if required
- Select the target (for example, an AWS KMS target)
- Choose the provisioning mode:
- Click Save
Step 4: Verify the Provisioned Target
- After saving, return to the Provisioning tab
- Confirm that the new target appears in the targets list
- Verify:
- External Key Name
- Target type
- Target path
Step 5: Repeat for Additional Targets
To provision the same Classic Key to another external system:
- Click Attach again
- Select a different target (AWS, Azure, GCP, Thales, etc.)
- Provide a new External Key Name if needed
- Save the configuration
You can repeat this process multiple times, each time adding another external target while continuing to manage a single Classic Key in Akeyless.
Updated about 10 hours ago
