-
Notifications
You must be signed in to change notification settings - Fork 159
[DRAFT] network security #1690
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] network security #1690
Conversation
* 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. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
fix me
|
|
|
|
|
|
|
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). |
There was a problem hiding this comment.
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?
No description provided.