Skip to content

Conversation

shainaraskas
Copy link
Collaborator

No description provided.

* Connection #0 to host my-deployment-d53192.es.vpce.us-east-1.aws.elastic-cloud.com left intact
```
The connection is established, and a valid certificate is presented to the client. The `403 Forbidden` is expected, because you haven’t allowed the traffic over this PrivateLink connection yet.
Copy link
Collaborator Author

Choose a reason for hiding this comment

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

fix me

Copy link

⚠️ Markdown file changes detected

The following Markdown file was removed in this PR:

  • deploy-manage/security/_snippets/create-filter.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

⚠️ Markdown file changes detected

The following Markdown file was removed in this PR:

  • deploy-manage/security/_snippets/create-filter.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

⚠️ Markdown file changes detected

The following Markdown file was removed in this PR:

  • deploy-manage/security/_snippets/create-filter.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

⚠️ Markdown file changes detected

The following Markdown file was removed in this PR:

  • deploy-manage/security/_snippets/create-filter.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

⚠️ Markdown file changes detected

The following Markdown file was removed in this PR:

  • deploy-manage/security/_snippets/create-filter.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

⚠️ Markdown file changes detected

The following Markdown file was removed in this PR:

  • deploy-manage/security/_snippets/create-filter.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

⚠️ Markdown file changes detected

The following Markdown file was removed in this PR:

  • deploy-manage/security/_snippets/associate-filter.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!

Follow these high-level steps to add Private Link rules to your deployments.
After you create your private endpoint and DNS entries, you can create a private connection policy in {{ecloud}}.

1. [Find your private endpoint resource name](/deploy-manage/security/azure-private-link-traffic-filters.md#ec-find-your-resource-name).
Copy link
Collaborator Author

Choose a reason for hiding this comment

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

there is no place in the ui for the resource name - is it still needed?

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