Document per-source descriptions for network security policies

deploy-manage/security/ip-filtering-cloud.md

@@ -78,7 +78,7 @@ To create an IP filter:
 5. Select the cloud provider and region for the IP filter. 
 6. Add a meaningful name and description for the IP filter.
 7. Under **Access control**, select whether the IP filter should be applied to ingress or egress traffic. Currently, only ingress traffic filters are supported.
-8. Add one or more allowed sources using IPv4, or a range of addresses with CIDR.
+8. Add one or more allowed sources using IPv4, or a range of addresses with CIDR. For each source, select **Add description** to add an optional description that helps you identify the source later.
 9.  Optional: Under **Apply to resources**, associate the new filter with one or more deployments or projects. After you associate the  IP filter with a deployment or project, it starts filtering traffic.
 10.  To automatically attach this IP filter to new deployments or projects, select **Apply to future resources by default**.
 11.  Click **Create**.

deploy-manage/security/private-connectivity-aws.md

@@ -375,7 +375,7 @@ Create a new private connection policy.
     Private connection policies are bound to a single resource type and region, and can be assigned only to resources with the same resource type and in the same region. If you want to associate a policy with multiple resource types or resources in multiple regions, then you have to recreate the policy for all applicable resource types and regions.
     :::
 6.  Under **Connectivity**, select **PrivateLink**.
-7.  Optional: Under **VPC filter**, enter your VPC endpoint ID. You should only specify a VPC filter if you want to filter traffic to your deployment or project.
+7.  Optional: Under **VPC filter**, enter your VPC endpoint ID. You should only specify a VPC filter if you want to filter traffic to your deployment or project. For each VPC filter, select **Add description** to add an optional description that helps you identify the filter later.
 
     If you don't specify a VPC filter, then the private connection policy acts only as a record that you've established private connectivity between AWS and Elastic in the applicable region.
 

deploy-manage/security/private-connectivity-azure.md

@@ -232,7 +232,7 @@ The Private Link connection will be approved automatically after the private con
     Private connection policies are bound to a single resource type and region, and can be assigned only to resources with the same resource type and in the same region. If you want to associate a policy with multiple resource types or resources in multiple regions, then you have to recreate the policy for all applicable resource types and regions.
     :::
 6.  Under **Connectivity**, select **PrivateLink**.
-7.  Enter your private endpoint **Resource name** and **Resource ID**. When applied to a deployment or project, this information will be used to filter traffic.
+7.  Enter your private endpoint **Resource name** and **Resource ID**. When applied to a deployment or project, this information will be used to filter traffic. Select **Add description** to add an optional description that helps you identify the filter later.
 
     :::{tip}
     You can apply multiple policies to a single deployment or project. The policies can be of different types. In case of multiple policies, traffic can match any associated policy to be forwarded to the resource. If none of the policies match, the request is rejected with `403 Forbidden`.

deploy-manage/security/private-connectivity-gcp.md

@@ -202,9 +202,9 @@ Create a new private connection policy.
     Private connection policies are bound to a single region, and can be assigned only to deployments in the same region. If you want to associate a policy with resources in multiple regions, then you have to create the same policy in all the regions you want to apply it to.
     :::
 6. Under **Connectivity**, select **PrivateLink**.
-7. Optional: Under **VPC filter**, enter your Private Service Connect endpoint connection ID. You should only specify a Private Service Connect endpoint connection ID if you want to filter traffic to your deployment. 
+7. Optional: Under **VPC filter**, enter your Private Service Connect endpoint connection ID. You should only specify a Private Service Connect endpoint connection ID if you want to filter traffic to your deployment. For each VPC filter, select **Add description** to add an optional description that helps you identify the filter later.
 
-    If you don't specify a VPC filter, then the private connection policy acts only as a record that you've established private connectivity between AWS and Elastic in the applicable region.
+    If you don't specify a VPC filter, then the private connection policy acts only as a record that you've established private connectivity between GCP and Elastic in the applicable region.
 
     :::{tip}
     You can apply multiple policies to a single deployment. The policies can be of different types. In case of multiple policies, traffic can match any associated policy to be forwarded to the resource. If none of the policies match, the request is rejected with `403 Forbidden`.