diff --git a/docs/Advanced Functionality/account-settings/encryption-key-policy.md b/docs/Advanced Functionality/account-settings/encryption-key-policy.md index 4870ea649..91a4995cd 100644 --- a/docs/Advanced Functionality/account-settings/encryption-key-policy.md +++ b/docs/Advanced Functionality/account-settings/encryption-key-policy.md @@ -47,7 +47,7 @@ Where: ## Set an Encryption Key Policy with the Console -1. Log in to the Akeyless Console, and go to **Account Settings** > **Key Management**. +1. Log in to the Akeyless Console, and go to **Account Settings**, then **Key Management**. 2. In the **Key Management Policies** section, press **Add**. 3. Define the remaining parameters as follows: * **Object Type**: Choose either **Item** or **Target**. diff --git a/docs/Advanced Functionality/aws-best-practices/crossaccount-configuration-using-terraform.md b/docs/Advanced Functionality/aws-best-practices/crossaccount-configuration-using-terraform.md index 9f2240c9d..ff89f10ac 100644 --- a/docs/Advanced Functionality/aws-best-practices/crossaccount-configuration-using-terraform.md +++ b/docs/Advanced Functionality/aws-best-practices/crossaccount-configuration-using-terraform.md @@ -220,7 +220,7 @@ Once finish, you will have a new role in the source Account that trusts itself a To work with this role from Akeyless, an [AWS Target](https://docs.akeyless.io/docs/aws-targets) is required: -1. Navigate to **Targets** > **New** > **AWS**. Press **Next**. +1. Navigate to **Targets**, then **New**, then **AWS**. Press **Next**. 2. Give the Target a **Name** and optionally, a **Location**. Press **Next**. 3. Choose **Use Gateway's Cloud Identity** and click **Finish** @@ -228,7 +228,7 @@ To work with this role from Akeyless, an [AWS Target](https://docs.akeyless.io/d To have a centralized Gateway that will be able to manage resources in multiple AWS Accounts, A target in Akeyless with an [External ID](https://aws.amazon.com/blogs/apn/securely-using-external-id-for-accessing-aws-accounts-owned-by-others/) is required. -1. Navigate to **Targets** > **New** > **AWS**. Press **Next**. +1. Navigate to **Targets**, then **New**, then **AWS**. Press **Next**. 2. Give the Target a **Name** and optionally, a **Location**. Press **Next**. 3. Choose **Use Gateway's Cloud Identity** and check the **External ID** option. @@ -485,7 +485,7 @@ Then, enter the GW console - `https://public-ip>:8000/console` This example will use **IAM\_USER** mode, this will create a new temporary user in the destination account in AWS. -In Akeyless, Navigate to **Items** > **New** > **Dynamic Secret** > **AWS**. +In Akeyless, Navigate to **Items**, then **New**, then **Dynamic Secret**, then **AWS**. 1. Give the Dynamic Secret a name and select **Next**. 2. Choose the **Target** that was created with the **External ID**. @@ -500,7 +500,7 @@ You will get the credentials of the new temporary user that was created in the d Now, we will use an AWS [Rotated Secret](https://docs.akeyless.io/docs/create-an-aws-rotated-secret). -In Akeyless, Navigate to **Items** > **New** > **Rotated Secret** > **AWS**. +In Akeyless, Navigate to **Items**, then **New**, then **Rotated Secret**, then **AWS**. 1. Give the Dynamic Secret a name and select **Next**. 2. Choose the **Target** that was created with the **External ID**. diff --git a/docs/Advanced Functionality/aws-best-practices/deploy-a-gateway-using-cloudformation.md b/docs/Advanced Functionality/aws-best-practices/deploy-a-gateway-using-cloudformation.md index 9301b1054..8cfdab828 100644 --- a/docs/Advanced Functionality/aws-best-practices/deploy-a-gateway-using-cloudformation.md +++ b/docs/Advanced Functionality/aws-best-practices/deploy-a-gateway-using-cloudformation.md @@ -28,13 +28,13 @@ In this case, for simplicity, we used [API Key](https://docs.akeyless.io/docs/au In the Akeyless Console, navigate to **Users & Auth Methods**. -1. Click **New** > **AWS IAM**. +1. Click **New**, then **AWS IAM**. 2. Provide a name AWS Account and click **Finish**. More details about the AWS IAM authentication method can be found [here](https://docs.akeyless.io/docs/auth-with-aws) In addition, to create an authentication methods that support user login, for simplicity, we will use [API Key](https://docs.akeyless.io/docs/auth-with-api-key) -1. Click **New** > **API Key** +1. Click **New**, then **API Key** 2. Provide a name and click **Finish** > ℹ️ **Note (API Key Credentials):** @@ -65,7 +65,7 @@ The following steps will be used to set up the Gateway and create the required * To deploy the Akeyless Gateway using [AWS CloudFormation](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/Welcome.html): -1. Open the **AWS Console**, navigate to **CloudFormation** > **Create Stack** > **With new resources (standard)** +1. Open the **AWS Console**, navigate to **CloudFormation**, then **Create Stack**, then **With new resources (standard)** 2. Select **Upload a template file**, then upload the `yaml` file containing the CloudFormation template. @@ -587,7 +587,7 @@ The following steps will create the required resources in Akeyless to generate a ### Create a Rotated Secret -1. Go to **Items** > **New** > **Rotated Secret**, then select **AWS**. +1. Go to **Items**, then **New**, then **Rotated Secret**, then select **AWS**. 2. Provide a name and location. @@ -605,7 +605,7 @@ Click the **eye** icon to view the current credentials, or select **Rotate Secre ### Create a Universal Secret Connector (USC) -1. Go to **Items** > **New** > **Universal Secret Connector**, and choose **AWS**. +1. Go to **Items**, then **New**, then **Universal Secret Connector**, and choose **AWS**. 2. Provide a name and location. diff --git a/docs/Akeyless Gateway/configure-gateway/gateway-caching/index.md b/docs/Akeyless Gateway/configure-gateway/gateway-caching/index.md index d83f51816..1c8308902 100644 --- a/docs/Akeyless Gateway/configure-gateway/gateway-caching/index.md +++ b/docs/Akeyless Gateway/configure-gateway/gateway-caching/index.md @@ -41,7 +41,7 @@ For Kubernetes proactive cache sizing guidance, see [Gateway Best Practices: Res To manage cache runtime settings from Gateway Configuration Manager: 1. Open `https://:8000/console`. -2. Go to **Gateways** > **Your Gateway** > **Manage Gateway** > **Caching Configuration**. +2. Go to **Gateways**, then **Your Gateway**, then **Manage Gateway**, then **Caching Configuration**. 3. Configure cache and proactive cache options. 4. Save changes. diff --git a/docs/Akeyless Gateway/configure-gateway/gateway-caching/proactive-caching.md b/docs/Akeyless Gateway/configure-gateway/gateway-caching/proactive-caching.md index 2055210cf..c75cace2c 100644 --- a/docs/Akeyless Gateway/configure-gateway/gateway-caching/proactive-caching.md +++ b/docs/Akeyless Gateway/configure-gateway/gateway-caching/proactive-caching.md @@ -72,7 +72,7 @@ Do not use proactive caching when: | Deployment option | How to configure | | --- | --- | -| Gateway Console | In the Gateway UI, go to **Manage Gateway** > **Caching** and turn on the **Enable Proactive Caching** toggle. (Requires **Enable Caching** to be on first.) | +| Gateway Console | In the Gateway UI, go to **Manage Gateway**, then **Caching** and turn on the **Enable Proactive Caching** toggle. (Requires **Enable Caching** to be on first.) | | [Kubernetes (Helm)](https://docs.akeyless.io/docs/gateway-deploy-kubernetes-helm) | Set environment variables under `globalConfig.env` in `values.yaml` and [apply a Helm upgrade](https://helm.sh/docs/helm/helm_upgrade/). | | [Standalone Docker](https://docs.akeyless.io/docs/gateway-deploy-standalone-docker) | Set proactive cache environment variables in container runtime configuration. | | [Docker Compose](https://docs.akeyless.io/docs/gateway-deploy-docker-compose) | Set the same environment variables in the compose service definition and redeploy. | diff --git a/docs/Akeyless Gateway/configure-gateway/gateway-caching/runtime-caching.md b/docs/Akeyless Gateway/configure-gateway/gateway-caching/runtime-caching.md index 2d76c770b..4b0ca0a77 100644 --- a/docs/Akeyless Gateway/configure-gateway/gateway-caching/runtime-caching.md +++ b/docs/Akeyless Gateway/configure-gateway/gateway-caching/runtime-caching.md @@ -67,7 +67,7 @@ Use the following deployment-specific options to configure runtime caching: | Deployment option | How to configure | | --- | --- | -| Gateway Console | In the Gateway UI, go to **Manage Gateway** > **Caching** and turn on the **Enable Caching** toggle. | +| Gateway Console | In the Gateway UI, go to **Manage Gateway**, then **Caching** and turn on the **Enable Caching** toggle. | | [Kubernetes (Helm)](https://docs.akeyless.io/docs/gateway-deploy-kubernetes-helm) | Set runtime behavior keys under `globalConfig.env` in `values.yaml` (for example `CACHE_ENABLE`, `PREFER_CLUSTER_CACHE_FIRST`) and [apply a Helm upgrade](https://helm.sh/docs/helm/helm_upgrade/). Set `IGNORE_REDIS_HEALTH` separately when you want to change health-check behavior. | | [Standalone Docker](https://docs.akeyless.io/docs/gateway-deploy-standalone-docker) | Set cache-related environment variables (for example `CACHE_ENABLE`, `PREFER_CLUSTER_CACHE_FIRST`) in container runtime configuration. | | [Docker Compose](https://docs.akeyless.io/docs/gateway-deploy-docker-compose) | Set the same cache-related environment variables in the compose service definition and redeploy. | diff --git a/docs/Akeyless Gateway/configure-gateway/gateway-certificate-store.md b/docs/Akeyless Gateway/configure-gateway/gateway-certificate-store.md index f4aa07b66..31a06fd32 100644 --- a/docs/Akeyless Gateway/configure-gateway/gateway-certificate-store.md +++ b/docs/Akeyless Gateway/configure-gateway/gateway-certificate-store.md @@ -78,4 +78,4 @@ To remove certificates from your gateway using the UI, follow these steps: 2. Go to **Certificate Store**. -3. Choose the certificate you wish to remove and select the **Action Menu** > **Delete**. +3. Choose the certificate you wish to remove and select the **Action Menu**, then **Delete**. diff --git a/docs/Akeyless Gateway/deploy-gateway/gateway-cloud-serverless-deployments/gateway-deploy-serverless-aws.md b/docs/Akeyless Gateway/deploy-gateway/gateway-cloud-serverless-deployments/gateway-deploy-serverless-aws.md index 33bcfed63..2c367ffce 100644 --- a/docs/Akeyless Gateway/deploy-gateway/gateway-cloud-serverless-deployments/gateway-deploy-serverless-aws.md +++ b/docs/Akeyless Gateway/deploy-gateway/gateway-cloud-serverless-deployments/gateway-deploy-serverless-aws.md @@ -187,7 +187,7 @@ Find more information about the available Terraform [configuration files](https: The **Serverless Gateway** version can be updated to different versions based on your preferences, follow these steps to update the Gateway: * Enter the [Serverless Gateway](https://github.com/akeyless-community/akeyless-serverless-gateway) repo in **GitHub** -* Go to **Lambda Docker Image Configuration** > **Selecting a Different Version** +* Go to **Lambda Docker Image Configuration**, then **Selecting a Different Version** * [View available versions](https://gallery.ecr.aws/akeyless/serverless-gateway) * In `variables.tf` file, change the field `image-tag` to the version you desire * Run `terraform apply` diff --git a/docs/Certificate Lifecycle Management/certificate-discovery.md b/docs/Certificate Lifecycle Management/certificate-discovery.md index 79cfa30c3..feca70a74 100644 --- a/docs/Certificate Lifecycle Management/certificate-discovery.md +++ b/docs/Certificate Lifecycle Management/certificate-discovery.md @@ -47,7 +47,7 @@ Use the following mapping when translating Console fields to CLI flags: ## Setting a Certificate Discovery in the Akeyless Console -1. Log in to the Akeyless Console, and go to **Discovery & Migration** > **New** > **Certificate Discovery**. +1. Log in to the Akeyless Console, and go to **Discovery & Migration**, then **New**, then **Certificate Discovery**. 2. Define a Name for the certificate discovery, and specify the **Target Location** as a path to the virtual folder where you want the scanned certificates to be saved in. If the folder does not exist, it will be created together with the scanned certificates. 3. Add the **Sources** of the scan, such as: **IPs**, **CIDR ranges**, or **DNS names** 4. Add the relevant ports, the default value is `443`. @@ -55,4 +55,4 @@ Use the following mapping when translating Console fields to CLI flags: ## Run the Certificate Discovery -To run the discovery, select the discovery item and choose **Action Menu** > **Start Scan**. If the scan completes successfully, a new folder will appear under **Items** containing all the certificates that were found. +To run the discovery, select the discovery item and choose **Action Menu**, then **Start Scan**. If the scan completes successfully, a new folder will appear under **Items** containing all the certificates that were found. diff --git a/docs/Certificate Lifecycle Management/certificate-storage.md b/docs/Certificate Lifecycle Management/certificate-storage.md index 712e37824..1276a2ae1 100644 --- a/docs/Certificate Lifecycle Management/certificate-storage.md +++ b/docs/Certificate Lifecycle Management/certificate-storage.md @@ -75,7 +75,7 @@ All of the parameters from the creation command will also apply here. ## Managing a Certificate in the Console -1. Select **Items** > **New** > **Certificate**. +1. Select **Items**, then **New**, then **Certificate**. 2. Basic Configuration (fill in the following parameters): diff --git a/docs/Contributing Guides/technical-documentation-style-guide/index.md b/docs/Contributing Guides/technical-documentation-style-guide/index.md index ce8251d70..0ee69fa8d 100644 --- a/docs/Contributing Guides/technical-documentation-style-guide/index.md +++ b/docs/Contributing Guides/technical-documentation-style-guide/index.md @@ -163,6 +163,15 @@ With context: * `Monospace`: For commands, code, filenames, configuration keys. * Avoid underlines (can be confused with hyperlinks). +### UI Navigation Paths + +Write out navigation steps using words. Use bold for UI element names and "then" between steps. Do not use `>` as a navigation separator. + +* **Correct**: go to **Account Settings**, then **Key Management** +* **Incorrect**: go to **Account Settings** > **Key Management** + +This applies to all UIs, including third-party consoles such as the AWS Console, Azure Portal, and GitHub. + ## Terminology * Capitalize proper nouns and feature names (For example, Akeyless MCP Server). diff --git a/docs/Encryption & KMS/classic-keys/create-a-classic-key.md b/docs/Encryption & KMS/classic-keys/create-a-classic-key.md index b1d40b356..b2d3a5906 100644 --- a/docs/Encryption & KMS/classic-keys/create-a-classic-key.md +++ b/docs/Encryption & KMS/classic-keys/create-a-classic-key.md @@ -59,7 +59,7 @@ The full list of options for this command is: You can create a classic key using the Akeyless Gateway. If you’d prefer, see how to do this from the [Akeyless CLI](https://docs.akeyless.io/docs/create-a-classic-key#create-a-classic-key-from-the-cli) instead. -1. In the Akeyless Gateway UI, select **Classic Keys** > **New**. +1. In the Akeyless Gateway UI, select **Classic Keys**, then **New**. 2. Define the following: * **Name:** The name of the classic key. diff --git a/docs/Encryption & KMS/classic-keys/index.md b/docs/Encryption & KMS/classic-keys/index.md index 2255c0b3e..6ef578b62 100644 --- a/docs/Encryption & KMS/classic-keys/index.md +++ b/docs/Encryption & KMS/classic-keys/index.md @@ -86,7 +86,7 @@ Additional parameters can be found in the [CLI Reference](https://docs.akeyless. ### Creating a Classic Key -1. In the Akeyless Console, select **Items** > **New** > **Encryption Key** > **Classic**. +1. In the Akeyless Console, select **Items**, then **New**, then **Encryption Key**, then **Classic**. 2. Define the following: diff --git a/docs/Encryption & KMS/encryption-keys/index.md b/docs/Encryption & KMS/encryption-keys/index.md index 494d624c0..c9f221bb4 100644 --- a/docs/Encryption & KMS/encryption-keys/index.md +++ b/docs/Encryption & KMS/encryption-keys/index.md @@ -163,7 +163,7 @@ Select a hash function between `sha-256` and `sha-512`. The full parameters for ### Creating an Encryption Key -1. Log in to the Akeyless Console, and go to **Items** > **New** > **Encryption Key** > **DFC™**. +1. Log in to the Akeyless Console, and go to **Items**, then **New**, then **Encryption Key**, then **DFC™**. 2. Define a **Name** for the key. diff --git a/docs/Encryption & KMS/gpg-keys.md b/docs/Encryption & KMS/gpg-keys.md index 263a8ba3c..70be40069 100644 --- a/docs/Encryption & KMS/gpg-keys.md +++ b/docs/Encryption & KMS/gpg-keys.md @@ -94,7 +94,7 @@ While the console can create GPG-type keys, their full usage functionalities are ### Key Creation -1. In the Akeyless Console, select **New**>**Encryption Key** > **Classic**. +1. In the Akeyless Console, select **New**, then **Encryption Key**, then **Classic**. 2. Define the following: diff --git a/docs/Integrations & Plugins/plugins-overview/circleci-plugin.md b/docs/Integrations & Plugins/plugins-overview/circleci-plugin.md index c45be3058..0aa80ee9f 100644 --- a/docs/Integrations & Plugins/plugins-overview/circleci-plugin.md +++ b/docs/Integrations & Plugins/plugins-overview/circleci-plugin.md @@ -75,7 +75,7 @@ akeyless set-role-rule --role-name /Dev/CI/CircleCIRole \ Instead of checking your Auth Method `access Id`, or your [Gateway](https://docs.akeyless.io/docs/gateway-overview) `URL` into version control, we can store them securely in CircleCI environment variables. -Go to **Project Settings** > **Environment variables** > **Add Environment Variable** +Go to **Project Settings**, then **Environment variables**, then **Add Environment Variable** Create an environment variable in CircleCI called `ACCESS_ID` and store your Auth Method's `access-id` in it. @@ -87,7 +87,7 @@ While working with [Zero Knowledge](https://docs.akeyless.io/docs/gateway-zero-k In jobs using a context, CircleCI provides OpenID Connect ID (OIDC) tokens in environment variables. A job can use these tokens to access Akeyless without storing long-lived credentials in CircleCI. -Go to **Organization Settings** > **Contexts** > **Add a context** +Go to **Organization Settings**, then **Contexts**, then **Add a context** Name it `akeyless`, we will later add this context to a job by adding the context key to the workflows section of your `circleci/config.yml` file. ## Usage diff --git a/docs/Integrations & Plugins/plugins-overview/hashicorp-vault-proxy/github-actions-hvp.md b/docs/Integrations & Plugins/plugins-overview/hashicorp-vault-proxy/github-actions-hvp.md index 8483b98ae..6af05a569 100644 --- a/docs/Integrations & Plugins/plugins-overview/hashicorp-vault-proxy/github-actions-hvp.md +++ b/docs/Integrations & Plugins/plugins-overview/hashicorp-vault-proxy/github-actions-hvp.md @@ -54,7 +54,7 @@ To work with the GitHub Actions plugin: ## Set Up Akeyless Authentication Credentials for the Repository -1. On GitHub, navigate to the main page of the repository, and select **Settings** > **Secrets** > **New repository secret**. +1. On GitHub, navigate to the main page of the repository, and select **Settings**, then **Secrets**, then **New repository secret**. 2. Name the secret **VAULT\_TOKEN**. @@ -72,7 +72,7 @@ The GitHub repository is now configured with an access token for Akeyless. The GitHub [self-hosted runner](https://docs.github.com/en/actions/hosting-your-own-runners/about-self-hosted-runners) enables you to start a runner instance on an instance that you manage. Your workstation can be used if it is supported. -1. On GitHub, navigate to the main page of the repository, and select **Settings** > **Actions** > **Runners** > **Add runner**. +1. On GitHub, navigate to the main page of the repository, and select **Settings**, then **Actions**, then **Runners**, then **Add runner**. 2. Select the operating system and architecture of your self-hosted runner machine. diff --git a/docs/Secrets Management/how-to-create-dynamic-secret/create-an-azure-ad-app-service-account.md b/docs/Secrets Management/how-to-create-dynamic-secret/create-an-azure-ad-app-service-account.md index 9fa70c6dd..3b7e8217b 100644 --- a/docs/Secrets Management/how-to-create-dynamic-secret/create-an-azure-ad-app-service-account.md +++ b/docs/Secrets Management/how-to-create-dynamic-secret/create-an-azure-ad-app-service-account.md @@ -12,7 +12,7 @@ next: --- ## Application Registration in Active Directory -1. In the Azure Portal, go to **Azure Active Directory** > **App registration**: +1. In the Azure Portal, go to **Azure Active Directory**, then **App registration**: ![On Azure Portal -> Azure Active Directory -> App Registration](https://files.readme.io/407e4bf-image-20210204-103119.png) diff --git a/docs/Secrets Management/how-to-create-dynamic-secret/google-workspace-secret.md b/docs/Secrets Management/how-to-create-dynamic-secret/google-workspace-secret.md index 59eb9e0c8..fdede72d1 100644 --- a/docs/Secrets Management/how-to-create-dynamic-secret/google-workspace-secret.md +++ b/docs/Secrets Management/how-to-create-dynamic-secret/google-workspace-secret.md @@ -39,7 +39,7 @@ Follow these steps to create a **Service Account** in **Google Cloud Platform**: 3. **Generate and download JSON key**: Click the **Service Account** that was created, go to **Keys**, and click **Add Key > Create new key > JSON**. The key will be downloaded automatically to your computer. -4. **Delegate Domain-Wide Authority**: In the **Google Workspace Admin Console**, go to **Security** > **Access and data control > API controls**, click **Manage Domain Wide Delegation** > **Add new**, and enter the client **ID** from the **JSON** file downloaded earlier. +4. **Delegate Domain-Wide Authority**: In the **Google Workspace Admin Console**, go to **Security**, then **Access and data control > API controls**, click **Manage Domain Wide Delegation**, then **Add new**, and enter the client **ID** from the **JSON** file downloaded earlier. * In the same location, add the following scopes: ```json diff --git a/docs/Secrets Management/how-to-create-dynamic-secret/openai-dynamic-secrets.md b/docs/Secrets Management/how-to-create-dynamic-secret/openai-dynamic-secrets.md index c6414bd0c..da2f27912 100644 --- a/docs/Secrets Management/how-to-create-dynamic-secret/openai-dynamic-secrets.md +++ b/docs/Secrets Management/how-to-create-dynamic-secret/openai-dynamic-secrets.md @@ -61,7 +61,7 @@ Where: > ✅ **Tip:** To start working with Dynamic Secrets from the Akeyless Console, you need to configure the Gateway URL thus enabling communication between the Akeyless SaaS and the Akeyless Gateway. -1. Log in to the Akeyless Console, and go to **Items** > **New** > **Dynamic Secret**. +1. Log in to the Akeyless Console, and go to **Items**, then **New**, then **Dynamic Secret**. 2. Select the **OpenAI** secret type and click **Next**. diff --git a/docs/Secrets Management/targets/cloudflare-target.md b/docs/Secrets Management/targets/cloudflare-target.md index a408355da..9836cd501 100644 --- a/docs/Secrets Management/targets/cloudflare-target.md +++ b/docs/Secrets Management/targets/cloudflare-target.md @@ -53,7 +53,7 @@ Where: ## Create a Cloudflare Target in the Console -1. Log in to the Akeyless Console, and go to **Targets** > **New** > **Cloudflare**. +1. Log in to the Akeyless Console, and go to **Targets**, then **New**, then **Cloudflare**. 2. Define the **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. diff --git a/docs/Secrets Management/targets/digicert-target.md b/docs/Secrets Management/targets/digicert-target.md index ebc367644..72f1843d1 100644 --- a/docs/Secrets Management/targets/digicert-target.md +++ b/docs/Secrets Management/targets/digicert-target.md @@ -96,7 +96,7 @@ Where: ## Create a Digicert Target in the Console -1. Log in to the Akeyless Console, and go to **Targets** > **New** > **Certificate Automation (Digicert)**. +1. Log in to the Akeyless Console, and go to **Targets**, then **New**, then **Certificate Automation (Digicert)**. 2. Define the 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. @@ -112,11 +112,11 @@ Where: * **Target**: Select a target that contains the DNS provider credentials (relevant only if **Challenge Type** is **DNS**). -* **Hosted Zone**: [Amazon Route 53](https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/hosted-zones-working-with.html) hosted zone identifier. (Relevant only if **Challenge Type** is **DNS** and **DNS Provider** is **AWS**). + * **Hosted Zone**: [Amazon Route 53](https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/hosted-zones-working-with.html) hosted zone identifier. (Relevant only if **Challenge Type** is **DNS** and **DNS Provider** is **AWS**). -* **Resource Group**: Azure resource group name. (Relevant only if **Challenge Type** is **DNS** and **DNS Provider** is **Azure**). + * **Resource Group**: Azure resource group name. (Relevant only if **Challenge Type** is **DNS** and **DNS Provider** is **Azure**). -* **GCP Project**: GCP Cloud DNS project ID. Optional when **DNS Provider** is **GCP**. + * **GCP Project**: GCP Cloud DNS project ID. Optional when **DNS Provider** is **GCP**. * **DNS Zone**: Cloudflare DNS zone name. Relevant only when **DNS Provider** is **Cloudflare**. diff --git a/docs/Secrets Management/targets/google-ca-target.md b/docs/Secrets Management/targets/google-ca-target.md index 50e626d26..17ab72329 100644 --- a/docs/Secrets Management/targets/google-ca-target.md +++ b/docs/Secrets Management/targets/google-ca-target.md @@ -96,7 +96,7 @@ Where: ## Create a Google CA Target in the Console -1. Log in to the Akeyless Console, and go to **Targets** > **New** > **Certificate Automation (Google CA)**. +1. Log in to the Akeyless Console, and go to **Targets**, then **New**, then **Certificate Automation (Google CA)**. 2. Define the 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. @@ -116,11 +116,11 @@ Where: * **Target**: Select a target that contains the DNS provider credentials (relevant only if **Challenge Type** is **DNS**). -* **Hosted Zone**: [Amazon Route 53](https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/hosted-zones-working-with.html) hosted zone identifier. (Relevant only if **Challenge Type** is **DNS** and **DNS Provider** is **AWS**). + * **Hosted Zone**: [Amazon Route 53](https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/hosted-zones-working-with.html) hosted zone identifier. (Relevant only if **Challenge Type** is **DNS** and **DNS Provider** is **AWS**). -* **Resource Group**: Azure resource group name. (Relevant only if **Challenge Type** is **DNS** and **DNS Provider** is **Azure**). + * **Resource Group**: Azure resource group name. (Relevant only if **Challenge Type** is **DNS** and **DNS Provider** is **Azure**). -* **GCP Project**: GCP Cloud DNS project ID. Optional when **DNS Provider** is **GCP**. + * **GCP Project**: GCP Cloud DNS project ID. Optional when **DNS Provider** is **GCP**. * **DNS Zone**: Cloudflare DNS zone name. Relevant only when **DNS Provider** is **Cloudflare**. diff --git a/docs/Secrets Management/targets/index.md b/docs/Secrets Management/targets/index.md index 993000311..95b888d6e 100644 --- a/docs/Secrets Management/targets/index.md +++ b/docs/Secrets Management/targets/index.md @@ -22,74 +22,14 @@ Using targets has three primary advantages: * Don't break the credential chain: Targets can also be used to sync encryption keys with an external KMS, or to define a Target to be used with our [Rotated Secrets](https://docs.akeyless.io/docs/rotated-secrets) to manage and automate your privilege account credentials rotation. This allows every item referencing the target to be up to date on the necessary information and to stay usable even after rotations are done. -## Target Types +## Common Target Families -### Database +If you are looking for a specific target type, start with the family that matches your endpoint: -* [Cassandra](https://docs.akeyless.io/docs/database-targets#cassandra) -* [Microsoft SQL Server (MSSQL)](https://docs.akeyless.io/docs/database-targets#microsoft-sql-server-mssql) -* [MongoDB](https://docs.akeyless.io/docs/database-targets#mongodb) -* [MySQL](https://docs.akeyless.io/docs/database-targets#mysql-and-mariadb) -* [Oracle](https://docs.akeyless.io/docs/database-targets#oracle) -* [PostgreSQL](https://docs.akeyless.io/docs/database-targets#postgresql) -* [Redis](https://docs.akeyless.io/docs/database-targets#redis) -* [Redshift](https://docs.akeyless.io/docs/database-targets#amazon-redshift) -* [SAP HANA database](https://docs.akeyless.io/docs/database-targets#sap-hana-database) -* [Snowflake](https://docs.akeyless.io/docs/database-targets#snowflake) - -### Cloud - -* [AWS](https://docs.akeyless.io/docs/aws-targets) -* [Azure AD](https://docs.akeyless.io/docs/azure-targets) -* [Cloudflare](https://docs.akeyless.io/docs/cloudflare-target) -* [GCP](https://docs.akeyless.io/docs/gcp-targets) -* [Salesforce](https://docs.akeyless.io/docs/salesforce-target) - -### AI - -* [Gemini](https://docs.akeyless.io/docs/gemini-target) -* [OpenAI](https://docs.akeyless.io/docs/openai-target) - -### Kubernetes - -* [EKS](https://docs.akeyless.io/docs/kubernetes-targets) -* [GKE](https://docs.akeyless.io/docs/kubernetes-targets) -* [Generic](https://docs.akeyless.io/docs/kubernetes-targets) - -### Operating System - -* [SSH](https://docs.akeyless.io/docs/ssh-target) -* [Windows](https://docs.akeyless.io/docs/windows-target) - -### Certificate Automation - -* [DigiCert](https://docs.akeyless.io/docs/digicert-target) -* [GlobalSign](https://docs.akeyless.io/docs/globalsign-target) -* [GlobalSign Atlas](https://docs.akeyless.io/docs/globalsign-atlas) -* [GoDaddy](https://docs.akeyless.io/docs/godaddy-target) -* [Google CA](https://docs.akeyless.io/docs/google-ca-target) -* [Let's Encrypt](https://docs.akeyless.io/docs/lets-encrypt) -* [Sectigo](https://docs.akeyless.io/docs/sectigo-target) -* [Venafi](https://docs.akeyless.io/docs/venafi-target) -* [ZeroSSL](https://docs.akeyless.io/docs/zerossl-target) - -### Infrastructure - -* [Artifactory](https://docs.akeyless.io/docs/artifactory-targets) -* [Chef Infra](https://docs.akeyless.io/docs/chef-infra-targets) -* [Docker Hub](https://docs.akeyless.io/docs/docker-hub-target) -* [GitHub](https://docs.akeyless.io/docs/github-target) -* [GitLab](https://docs.akeyless.io/docs/gitlab-target) -* [Splunk](https://docs.akeyless.io/docs/splunk-target) - -### Other - -* [Custom](https://docs.akeyless.io/docs/web-targets) -* [HashiCorp Vault](https://docs.akeyless.io/docs/hashicorp-vault-target) -* [LDAP](https://docs.akeyless.io/docs/ldap-target) -* [Linked](https://docs.akeyless.io/docs/linked-target) -* [Ping](https://docs.akeyless.io/docs/ping-target) -* [RabbitMQ](https://docs.akeyless.io/docs/rabbitmq-targets) +* [Database Targets](https://docs.akeyless.io/docs/database-targets) for database credentials that applications and teams reuse across secrets. +* Cloud provider targets: [AWS Targets](https://docs.akeyless.io/docs/aws-targets), [Azure Targets](https://docs.akeyless.io/docs/azure-targets), and [GCP Targets](https://docs.akeyless.io/docs/gcp-targets) for cloud platform credentials and cloud-specific integrations. +* Certificate automation targets: [Let's Encrypt Target](https://docs.akeyless.io/docs/lets-encrypt), [DigiCert Target](https://docs.akeyless.io/docs/digicert-target), [Google CA Target](https://docs.akeyless.io/docs/google-ca-target), and [Cloudflare Target](https://docs.akeyless.io/docs/cloudflare-target) for DNS-01 validation with public Certificate Authority (CA) targets. +* [SSH Targets](https://docs.akeyless.io/docs/ssh-target) and [Web Targets](https://docs.akeyless.io/docs/web-targets) for server access and web-facing endpoints. ## Delete protection for targets diff --git a/docs/Secrets Management/targets/lets-encrypt.md b/docs/Secrets Management/targets/lets-encrypt.md index 73a9d9072..a3e5b4ae8 100644 --- a/docs/Secrets Management/targets/lets-encrypt.md +++ b/docs/Secrets Management/targets/lets-encrypt.md @@ -98,7 +98,7 @@ Where: ## Create a Let's Encrypt Target in the Console -1. Log in to the Akeyless Console, and go to **Targets** > **New** > **Certificate Automation (Let's Encrypt)**. +1. Log in to the Akeyless Console, and go to **Targets**, then **New**, then **Certificate Automation (Let's Encrypt)**. 2. Define the 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. diff --git a/docs/Universal Secret Connector/universal-secrets-connector/index.md b/docs/Universal Secret Connector/universal-secrets-connector/index.md index 6cff8ccfc..f872f2bb2 100644 --- a/docs/Universal Secret Connector/universal-secrets-connector/index.md +++ b/docs/Universal Secret Connector/universal-secrets-connector/index.md @@ -36,7 +36,7 @@ Akeyless currently supports creating Universal Secrets Connectors for the follow * [HashiCorp Vault Universal Secret Connector](https://docs.akeyless.io/docs/hc-vault-universal-secrets-connector) -To view all your Universal Secret Connectors, log in to the **Console** then navigate to **Items** > **Universal Secrets Connector**. +To view all your Universal Secret Connectors, log in to the **Console** then navigate to **Items**, then **Universal Secrets Connector**. ## Tutorial