azure

Author: shainaraskas

deploy-manage/security/_snippets/find-endpoint.md

@@ -10,8 +10,8 @@ If you have many deployments, you can instead go to the **Hosted deployments** (
 4. In the deployment overview, under **Applications**, find the application that you want to test.
 5. Click **Copy endpoint**. The value looks something like the following:
 
-```
-https://my-deployment-d53192.es.us-east-2.aws.elastic-cloud.com
+```subs=true
+https://my-deployment-d53192.es.{{example-default-dn}}
 ```
 
 In this endpoint, `my-deployment-d53192` is an alias, and `es` is the product you want to access within your deployment.

deploy-manage/security/_snippets/network-security-page.md

@@ -1,4 +1,3 @@
 1. Log in to the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body).
 2. From any deployment or project on the home page, select **Manage**.
-3. Under the **Features** tab, open the **Network security** page. 
-      % From the left navigation menu, select **Access and security** > **Network security**. 
+3. From the left navigation menu, select **Access and security** > **Network security**. 

deploy-manage/security/_snippets/private-url-struct.md

@@ -1,5 +1,4 @@
-* If you have a [custom endpoint alias](/deploy-manage/deploy/elastic-cloud/custom-endpoint-aliases.md) configured, you can use the custom endpoint URL to connect.
-* If you don't have a custom endpoint alias, then use the following URL structure. This URL is built from endpoint information retrieved from your Elastic deployment and the private hosted zone domain name that you registered.
+Use the following URL structure. This URL is built from endpoint information retrieved from your Elastic deployment and the private hosted zone domain name that you registered.
 
   ```
   https://{{alias}}.{{product}}.{{private_hosted_zone_domain_name}}
@@ -12,8 +11,8 @@
   ```
 
 
-::::{tip}
+:::{tip}
 You can use either 443 or 9243 as a port.
 
 You can also connect to the cluster using the {{es}} cluster ID, for example, https://6b111580caaa4a9e84b18ec7c600155e.{{example-phz-dn}}
-::::
+:::

deploy-manage/security/aws-privatelink-traffic-filters.md

@@ -12,6 +12,7 @@ sub:
   policy-type: "Private connection"
   service-name: "AWS PrivateLink"
   example-phz-dn: "vpce.us-east-1.aws.elastic-cloud.com"
+  example-default-dn: "us-east-1.aws.elastic-cloud.com"
 ---
 
 # AWS PrivateLink private connections
@@ -176,6 +177,7 @@ The mapping will be different for your region. Our production VPC Service for `u
 After you create your VPC endpoint and DNS entries, check that you are able to reach your cluster over PrivateLink.
 
 :::{include} _snippets/private-url-struct.md
+:::
 
 To test the connection:
 
@@ -184,7 +186,7 @@ To test the connection:
     :::{include} _snippets/find-endpoint.md
     :::
 
-2. Test the setup using the following cURL command. Make sure to replace the URL with your custom endpoint URL, or with your deployment's endpoint information and the private hosted zone domain name that you registered.
+2. Test the setup using the following cURL command. Make sure to replace the URL with your deployment's endpoint information and the private hosted zone domain name that you registered.
 
     **Request**
     ```sh
@@ -215,13 +217,13 @@ Creating a private connection policy and associating it with your deployments al
 * Record that you've established private connectivity between AWS and Elastic in the applicable region.
 * Filter traffic to your deployment using VCPE filters.
 
-Follow these high-level steps to add a private connection policy that can be associated with your deployment.
+Follow these high-level steps to add a private connection policy that can be associated with your deployments.
 
 1. Optional: [Find your VPC endpoint ID](#ec-find-your-endpoint).
 2. [Create rules using the VPC endpoint](#ec-create-traffic-filter-private-link-rule-set).
 3. [Associate the VPC endpoint with your deployment](#ec-associate-traffic-filter-private-link-rule-set).
 
-#### Optional: Find your VPC endpoint ID [ec-find-your-endpoint]
+### Optional: Find your VPC endpoint ID [ec-find-your-endpoint]
 
 The VPC endpoint ID is only required if you want to filter traffic to your deployment using VCPE filters.
 
@@ -232,7 +234,7 @@ You can find your VPC endpoint ID in the AWS console:
 :screenshot:
 :::
 
-#### Create a new private connection policy [ec-create-traffic-filter-private-link-rule-set]
+### Create a new private connection policy [ec-create-traffic-filter-private-link-rule-set]
 
 Create a new private connection policy.