From 62e1e607234321a9efa2315c7f129477dba61498 Mon Sep 17 00:00:00 2001 From: dorota <114921900+wojcik-dorota@users.noreply.github.com> Date: Thu, 1 Aug 2024 09:48:51 +0200 Subject: [PATCH] update(platform): azure private link early availability (#356) --- docs/platform/howto/use-azure-privatelink.md | 32 ++++++++++---------- 1 file changed, 16 insertions(+), 16 deletions(-) diff --git a/docs/platform/howto/use-azure-privatelink.md b/docs/platform/howto/use-azure-privatelink.md index d43a6e891..775d47999 100644 --- a/docs/platform/howto/use-azure-privatelink.md +++ b/docs/platform/howto/use-azure-privatelink.md @@ -1,6 +1,6 @@ --- title: Use Azure Private Link with Aiven services -limited: true +early: true --- import ConsoleLabel from "@site/src/components/ConsoleIcons" @@ -23,7 +23,7 @@ Azure Private Link is supported for the following services: ## Prerequisites -- This feature is in [limited availability](/docs/platform/concepts/beta_services). +- This feature is in [early availability](/docs/platform/concepts/beta_services#early-availability-). [Contact the sales team](mailto:sales@aiven.io) to enable it. - [Aiven CLI](/docs/tools/cli) is @@ -130,7 +130,7 @@ your Azure subscription and virtual network. The output will look similar to this: - ```shell + ```text PRIVATELINK_CONNECTION_ID PRIVATE_ENDPOINT_ID STATE USER_IP_ADDRESS ========================= ========================================================================================================================================================== ===================== =============== plc35843e8051. /subscriptions/8eefec94-5d63-40c9-983c-03ab083b411d/resourceGroups/test-privatelink/providers/Microsoft.Network/privateEndpoints/my-endpoint pending-user-approval null @@ -218,7 +218,6 @@ implementation. - ## Acquire connection information ### One Azure Private Link connection @@ -226,7 +225,8 @@ implementation. If you have one private endpoint connected to your Aiven service, you can preview the connection information (URI, hostname, or port required to access the service through the private endpoint) in [Aiven -Console](https://console.aiven.io/) > the service's **Overview** page > the **Connection information** section, where you'll also find the +Console](https://console.aiven.io/) > the service's **Overview** page > +the **Connection information** section, where you'll also find the switch for the `privatelink` access route. `privatelink`-access-route values for `host` and `port` differ from those for the `dynamic` access route used by default to connect to the service. @@ -238,7 +238,8 @@ PrivateLink connection. Each endpoint (connection) has PRIVATELINK_CONNECTION_ID, which you can check using the -[avn service privatelink azure connection list SERVICE_NAME](/docs/tools/cli/service/privatelink) command. +[avn service privatelink azure connection list SERVICE_NAME](/docs/tools/cli/service/privatelink) +command. To acquire connection information for your service component using Azure Private Link, run the @@ -251,11 +252,11 @@ Private Link, run the avn service connection-info UTILITY_NAME SERVICE_NAME -p PRIVATELINK_CONNECTION_ID ``` -Where: + Where: -- UTILITY_NAME is `kcat`, for example -- SERVICE_NAME is `kafka-12a3b4c5`, for example -- PRIVATELINK_CONNECTION_ID is `plc39413abcdef`, for example + - UTILITY_NAME is `kcat`, for example + - SERVICE_NAME is `kafka-12a3b4c5`, for example + - PRIVATELINK_CONNECTION_ID is `plc39413abcdef`, for example - For SASL connection information for Aiven for Apache Kafka® service components using Azure Private Link, run the following command: @@ -264,15 +265,14 @@ Where: avn service connection-info UTILITY_NAME SERVICE_NAME -p PRIVATELINK_CONNECTION_ID -a sasl ``` -Where: + Where: -- UTILITY_NAME is `kcat`, for example -- SERVICE_NAME is `kafka-12a3b4c5`, for example -- PRIVATELINK_CONNECTION_ID is `plc39413abcdef`, for example + - UTILITY_NAME is `kcat`, for example + - SERVICE_NAME is `kafka-12a3b4c5`, for example + - PRIVATELINK_CONNECTION_ID is `plc39413abcdef`, for example :::note -SSL certificates and SASL credentials are the same for all the -connections. +SSL certificates and SASL credentials are the same for all the connections. ::: ## Update subscription list