Cloud Targets

Azure

You can define an Azure AD target to be used with Azure AD dynamic secrets or Azure AD rotated secrets.

Create an Azure AD Target from the CLI

To create an Azure AD target from the CLI, run the following command:

akeyless create-azure-target \
--name <target name> \
--client-id <Azure client/application id> \
--tenant-id <Azure tenant id> \
--client-secret <Azure client secret>

Where:

  • name: A unique name of the target. The name can include the path to the virtual folder where you want to create the new target, using slash / separators. If the folder does not exist, it will be created together with the target.

  • client-id: The Application ID of the admin user that will be used to authenticate Akeyless with Azure.

  • client-secret: The client secret of the admin user that will be used to authenticate Akeyless with Azure.

  • tenant-id: Your Azure Tenant ID.

You can find the complete list of parameters for this command in the CLI Reference - Akeyless Targets section.

Create an Azure AD Target in the Akeyless Console

  1. Log in to the Akeyless Console, and go to Targets > New > Cloud Targets > Azure.

  2. Define a Name of the target, and specify the Location as a path to the virtual folder where you want to create the new target, using slash / separators. If the folder does not exist, it will be created together with the target

  3. Choose your preferred authentication mode by selecting one of the options:

    • Check the Use Credentials radio button to authenticate with the Azure AD admin user credentials.

    • Check the Use Gateway's Cloud Identity option to authenticate with the Gateway's Cloud IAM.

📘

Note

Use Gateway's Cloud Identity relevant for cases where your Gateway uses Azure service principal to authenticate against Akeyless.
For example, when you set up a Dynamic Secret for Azure, the target can be used for the temporary Azure service principals creation.

  1. Define the remaining parameters as follows:
  • Azure Client ID (Application ID): If you selected the Use Credentials option in the previous step, specify the Application ID of the admin user that will be used to authenticate Akeyless with Azure AD.

  • Azure Client Secret: Provide the client secret of the admin user that will be used to authenticate Akeyless with Azure AD.

  • Azure Tenant ID: Specify your Azure Tenant ID.

  • Subscription ID: If this target is for the Azure Storage account, then provide Azure Subscription ID.

  • Resource Group Name: Specify the Resource Group name in your Azure Subscription.

  • Resource Name: Provide the name of the relevant Resource.

  • Protection key: To enable Zero-Knowledge, select a key with a Customer Fragment. For more information about Zero-Knowledge, see Implement Zero Knowledge.

  1. Click Save.

Create an Azure Storage Account Target from the CLI

To create a new Azure Target for an Azure Storage Account, run the following command in the CLI:

akeyless create-azure-target \
--name <target name> \
--tenant-id <Azure Tenant ID> \
--client-id <Azure client id> \
--client-secret <Azure client secret> \
--subscription-id <Subscription ID> \
--resource-group-name <Resource Group name> \
--resource-name <Resource name>

Where:

  • name: A unique name of the target. The name can include the path to the virtual folder where you want to create the new secret, using slash / separators. If the folder does not exist, it will be created together with the target.

  • tenant-id: The ID of your Azure tenant.

  • client-id: The client ID of the App with the “Storage Account Key Operator Service Role“ permissions that is assigned to the Azure Storage account.

  • client-secret: The client secret of the App with the “Storage Account Key Operator Service Role“ permissions that is assigned to the Azure Storage account.

  • subscription-id: The ID of a Subscription that contains the Azure Storage account.

  • resource-group-name: The name of the Resource Group to which your Azure Storage account belongs.

  • resource-name: The name of the Azure Storage account.

GCP

You can define a GCP target to be used with GCP dynamic secrets.

Create a GCP Target from the CLI

To create a GCP target from the CLI, run the following command:

akeyless create-gcp-target \
--name <target name> \
--gcp-key-file-path <Path to the service account private key> \
--gcp-sa-email <GCP service account email>

Where:

  • name: A unique name of the target. The name can include the path to the virtual folder where you want to create the new target, using slash / separators. If the folder does not exist, it will be created together with the target.

  • gcp-key-file-path: A path to the file with the base64-encoded private key of the service account.

  • gcp-sa-email: The GCP service account email.

You can find the complete list of parameters for this command in the CLI Reference - Akeyless Targets section.

Create a GCP Target in the Akeyless Console

  1. Log in to the Akeyless Console, and go to Targets > New > Cloud Targets > GCP.

  2. Define a Name of the target, and specify the Location as a path to the virtual folder where you want to create the new target, using slash / separators. If the folder does not exist, it will be created together with the target

  3. Choose your preferred authentication mode by selecting one of the options:

    • Check the Use Credentials radio button to authenticate with the GCP admin user credentials.

    • Check the Use Gateway's Cloud Identity radio button to authenticate with the Gateway's Cloud IAM.

📘

Note

Use Gateway's Cloud Identity relevant for cases where your Gateway uses a GCP service account to authenticate against Akeyless.

For example, when you set up a Dynamic Secret for GCP, the target can be used for the temporary GCP service account keys creation.

  1. Define the remaining parameters as follows:
  • Service Account Email: If you selected the Use Credentials option in the previous step, specify the super-user service account email that will be used to authenticate Akeyless with GCP.

  • Service Account Key: Provide a base64-encoded private key of the super-user service account.

  • Protection key: To enable Zero-Knowledge, select a key with a Customer Fragment. For more information about Zero-Knowledge, see Implement Zero Knowledge.

  1. Click Save.

Did this page help you?