Skip to content

Network sec file renames xlinks #2047

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
wants to merge 6 commits into
base: network-sec-core
Choose a base branch
from

Conversation

shainaraskas
Copy link
Collaborator

@shainaraskas shainaraskas commented Jul 4, 2025

This PR:

  • Renames traffic filter related terms to match new product terminology
    • umbrella feature is now "network security" (only reflected in ecloud UI, but still works as umbrella term in the docs)
    • traffic filters are now "network security" broadly, "IP filters" and "private connectivity" specifically
  • updates filenames and resulting broken xlinks, adds redirects
  • followup to core changes in Network sec: rebrand and new cloud UX, IP filters in serverless #1785

part of https://github.com/elastic/platform-docs-team/issues/682

Copy link

github-actions bot commented Jul 4, 2025

⚠️ Markdown file changes detected

The following 5 Markdown files were removed in this PR:

  • deploy-manage/security/aws-privatelink-traffic-filters.md
  • deploy-manage/security/azure-private-link-traffic-filters.md
  • deploy-manage/security/ec-traffic-filtering-through-the-api.md
  • deploy-manage/security/gcp-private-service-connect-traffic-filters.md
  • deploy-manage/security/ip-traffic-filtering.md

The following Markdown file was renamed in this PR:

  • deploy-manage/security/claim-traffic-filter-link-id-ownership-through-api.mddeploy-manage/security/claim-private-connection-api.md

Action Required

We currently do not have an easy way to implement redirects for removed or renamed files. If possible, please:

  • Keep files whenever possible and hide them from the TOC by using hidden
  • Add a notice at the top of the file indicating that the page has moved with a link to the new location
  • Ensure you've updated redirects.yml accordingly if files must be removed or renamed

Thank you!

Copy link

github-actions bot commented Jul 4, 2025

⚠️ Markdown file changes detected

The following 9 Markdown files were renamed in this PR:

  • deploy-manage/security/claim-traffic-filter-link-id-ownership-through-api.mddeploy-manage/security/claim-private-connection-api.md
  • deploy-manage/security/ip-traffic-filtering.mddeploy-manage/security/ip-filtering.md
  • deploy-manage/security/ec-traffic-filtering-through-the-api.mddeploy-manage/security/network-security-api.md
  • deploy-manage/security/traffic-filtering.mddeploy-manage/security/network-security.md
  • deploy-manage/security/aws-privatelink-traffic-filters.mddeploy-manage/security/private-connectivity-aws.md
  • deploy-manage/security/azure-private-link-traffic-filters.mddeploy-manage/security/private-connectivity-azure.md
  • deploy-manage/security/gcp-private-service-connect-traffic-filters.mddeploy-manage/security/private-connectivity-gcp.md
  • deploy-manage/security/private-link-traffic-filters.mddeploy-manage/security/private-connectivity.md
  • solutions/observability/synthetics/traffic-filters.mdsolutions/observability/synthetics/network-security.md

Action Required

We currently do not have an easy way to implement redirects for removed or renamed files. If possible, please:

  • Keep files whenever possible and hide them from the TOC by using hidden
  • Add a notice at the top of the file indicating that the page has moved with a link to the new location
  • Ensure you've updated redirects.yml accordingly if files must be removed or renamed

Thank you!

Copy link

github-actions bot commented Jul 4, 2025

⚠️ Markdown file changes detected

The following 8 Markdown files were renamed in this PR:

  • deploy-manage/security/claim-traffic-filter-link-id-ownership-through-api.mddeploy-manage/security/claim-private-connection-api.md
  • deploy-manage/security/ip-traffic-filtering.mddeploy-manage/security/ip-filtering.md
  • deploy-manage/security/ec-traffic-filtering-through-the-api.mddeploy-manage/security/network-security-api.md
  • deploy-manage/security/traffic-filtering.mddeploy-manage/security/network-security.md
  • deploy-manage/security/aws-privatelink-traffic-filters.mddeploy-manage/security/private-connectivity-aws.md
  • deploy-manage/security/azure-private-link-traffic-filters.mddeploy-manage/security/private-connectivity-azure.md
  • deploy-manage/security/gcp-private-service-connect-traffic-filters.mddeploy-manage/security/private-connectivity-gcp.md
  • deploy-manage/security/private-link-traffic-filters.mddeploy-manage/security/private-connectivity.md

Action Required

We currently do not have an easy way to implement redirects for removed or renamed files. If possible, please:

  • Keep files whenever possible and hide them from the TOC by using hidden
  • Add a notice at the top of the file indicating that the page has moved with a link to the new location
  • Ensure you've updated redirects.yml accordingly if files must be removed or renamed

Thank you!

Copy link

github-actions bot commented Jul 4, 2025

⚠️ Markdown file changes detected

The following 8 Markdown files were renamed in this PR:

  • deploy-manage/security/claim-traffic-filter-link-id-ownership-through-api.mddeploy-manage/security/claim-private-connection-api.md
  • deploy-manage/security/ip-traffic-filtering.mddeploy-manage/security/ip-filtering.md
  • deploy-manage/security/ec-traffic-filtering-through-the-api.mddeploy-manage/security/network-security-api.md
  • deploy-manage/security/traffic-filtering.mddeploy-manage/security/network-security.md
  • deploy-manage/security/aws-privatelink-traffic-filters.mddeploy-manage/security/private-connectivity-aws.md
  • deploy-manage/security/azure-private-link-traffic-filters.mddeploy-manage/security/private-connectivity-azure.md
  • deploy-manage/security/gcp-private-service-connect-traffic-filters.mddeploy-manage/security/private-connectivity-gcp.md
  • deploy-manage/security/private-link-traffic-filters.mddeploy-manage/security/private-connectivity.md

Action Required

We currently do not have an easy way to implement redirects for removed or renamed files. If possible, please:

  • Keep files whenever possible and hide them from the TOC by using hidden
  • Add a notice at the top of the file indicating that the page has moved with a link to the new location
  • Ensure you've updated redirects.yml accordingly if files must be removed or renamed

Thank you!

Copy link

github-actions bot commented Jul 4, 2025

⚠️ Markdown file changes detected

The following 8 Markdown files were renamed in this PR:

  • deploy-manage/security/claim-traffic-filter-link-id-ownership-through-api.mddeploy-manage/security/claim-private-connection-api.md
  • deploy-manage/security/ip-traffic-filtering.mddeploy-manage/security/ip-filtering.md
  • deploy-manage/security/ec-traffic-filtering-through-the-api.mddeploy-manage/security/network-security-api.md
  • deploy-manage/security/traffic-filtering.mddeploy-manage/security/network-security.md
  • deploy-manage/security/aws-privatelink-traffic-filters.mddeploy-manage/security/private-connectivity-aws.md
  • deploy-manage/security/azure-private-link-traffic-filters.mddeploy-manage/security/private-connectivity-azure.md
  • deploy-manage/security/gcp-private-service-connect-traffic-filters.mddeploy-manage/security/private-connectivity-gcp.md
  • deploy-manage/security/private-link-traffic-filters.mddeploy-manage/security/private-connectivity.md

Action Required

We currently do not have an easy way to implement redirects for removed or renamed files. If possible, please:

  • Keep files whenever possible and hide them from the TOC by using hidden
  • Add a notice at the top of the file indicating that the page has moved with a link to the new location
  • Ensure you've updated redirects.yml accordingly if files must be removed or renamed

Thank you!

Copy link

github-actions bot commented Jul 4, 2025

⚠️ Markdown file changes detected

The following 8 Markdown files were renamed in this PR:

  • deploy-manage/security/claim-traffic-filter-link-id-ownership-through-api.mddeploy-manage/security/claim-private-connection-api.md
  • deploy-manage/security/ip-traffic-filtering.mddeploy-manage/security/ip-filtering.md
  • deploy-manage/security/ec-traffic-filtering-through-the-api.mddeploy-manage/security/network-security-api.md
  • deploy-manage/security/traffic-filtering.mddeploy-manage/security/network-security.md
  • deploy-manage/security/aws-privatelink-traffic-filters.mddeploy-manage/security/private-connectivity-aws.md
  • deploy-manage/security/azure-private-link-traffic-filters.mddeploy-manage/security/private-connectivity-azure.md
  • deploy-manage/security/gcp-private-service-connect-traffic-filters.mddeploy-manage/security/private-connectivity-gcp.md
  • deploy-manage/security/private-link-traffic-filters.mddeploy-manage/security/private-connectivity.md

Action Required

We currently do not have an easy way to implement redirects for removed or renamed files. If possible, please:

  • Keep files whenever possible and hide them from the TOC by using hidden
  • Add a notice at the top of the file indicating that the page has moved with a link to the new location
  • Ensure you've updated redirects.yml accordingly if files must be removed or renamed

Thank you!

Copy link

github-actions bot commented Jul 4, 2025

🔍 Preview links for changed docs

More links …

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this was resolved. found this changelog entry and corresponding PR

Comment on lines -55 to +56
:::

Once the traffic filter has been created, it needs to be assigned to the deployment from which you’re managing monitors from (the deployment containing the {{es}} cluster where your results need to go).
* `1.2.3.4/32`
* `34.89.99.187/32`

In ECH, ECE, and {{serverless-short}}, after the IP filter has been created, it needs to be associated with the deployment from which you’re managing monitors from (the deployment containing the {{es}} cluster where your results need to go).
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nb: replaced the screenshot with more generic instructions so this page wouldn't only work in the context of elastic cloud

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant