Document per-source descriptions for network security policies

[shainaraskas]

Summary

• Add Add description option to IP filter source-adding step in the ECH/Serverless IP filtering page.
• Add Add description option to VPC filter / private endpoint steps in the AWS, Azure, and GCP private connectivity pages.
• Fix preexisting "AWS" → "GCP" typo in the GCP Private Service Connect page.

Closes https://github.com/elastic/docs-content-internal/issues/1648

Related: https://github.com/elastic/cloud-ui/issues/4018

Made with Cursor

[github-actions]

Elastic Docs AI PR menu

Check the box to run an AI review for this pull request.

• Review docs changes (docs-review). Status: not started.

Powered by GitHub Agentic Workflows and docs-actions. For more information, reach out to the docs team.

[github-actions]

🔍 Preview links for changed docs

• deploy-manage/security/ip-filtering-cloud.md
• deploy-manage/security/private-connectivity-aws.md
• deploy-manage/security/private-connectivity-azure.md
• deploy-manage/security/private-connectivity-gcp.md

[github-actions]

✅ Elastic Docs Style Checker (Vale)

No issues found on modified lines!

---

The Vale linter checks documentation changes against the Elastic Docs style guide. To use Vale locally or report issues, refer to Elastic style guide for Vale.

[wajihaparvez]

LGTM

[wajihaparvez]

Suggested change

	8. Add one or more allowed sources using IPv4, or a range of addresses with CIDR. For each source, you can select **Add description** to add an optional description that helps you identify the source later.
	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.

Not really needed if we're saying "optional"

[wajihaparvez]

Suggested change

	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, you can select **Add description** to add an optional description that helps you identify the filter later.
	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.

[wajihaparvez]

Suggested change

	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. You can select **Add description** to add an optional description that helps you identify the filter later.
	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.

[wajihaparvez]

Suggested change

	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, you can select **Add description** to add an optional description that helps you identify the filter later.
	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.