-
Notifications
You must be signed in to change notification settings - Fork 471
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
RC: Enabling private service connection causes issues with the public endpoint #3195
Conversation
@@ -132,6 +132,10 @@ Once your Private Service Connect endpoint is active, you can connect your appli | |||
|
|||
1. Copy the endpoint and use it in your application to connect to your database. | |||
|
|||
{{< note >}} | |||
Once your Private Service Connect endpoint is active, you must connect to the database from the Private Service Connect endpoint. If you previously used the public or private endpoint to connect to your database, you must migrate any connections to the Private Service Connect endpoint. |
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.
@cmilesb do you think we should also mention that customers moving away from PSC should change their endpoint to the public or private endpoint or do you think the above implies it?
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.
Other than that looks good :) Thanks!
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.
Just added something under deactivate in eb06970
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.
LGTM
Ticket: DOC-3526
Staging link: https://docs.redis.com/staging/DOC-3526/rc/security/private-service-connect/