[DOCS-15959] Private Endpoint example ports on GCP Created: 13/Mar/23  Updated: 23/Mar/23  Resolved: 23/Mar/23

Status: Closed
Project: Documentation
Component/s: Atlas
Affects Version/s: None
Fix Version/s: None

Type: Typo Priority: Major - P3
Reporter: Michael Talarico Assignee: Corry Root
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:
Days since reply: 46 weeks, 1 day ago
Story Points: 2

 Description   

Hey Team, GCP Private Endpoints note 

Atlas services are accessed through Private Service Connect endpoints on ports 27015 through 27017

However, in the standard connection string example it shows

mongodb://pl-0-eastus2.uzgh6.gcp.mongodb.net:1024,pl-0-eastus2.uzgh6.gcp.mongodb.net:1025,pl-0-eastus2.uzgh6.gcp.mongodb.net:1026/?ssl=truereplicaSet=atlas-18bndf-shard-0

which shows 1024, 1025, 1026 ports. It also appears this way in the procedure further down the page.

 

I think the 1024-range is only applicable to AWS and Azure; however, we should double check with the correct product teams to confirm which is correct as I do not have a GCP cluster + PE handy.



 Comments   
Comment by Corry Root [ 21/Mar/23 ]

natalie.tsvetkova@mongodb.com, I updated the GCP Private Endpoint connection string port numbers to align with the note, "Atlas services are accessed through Private Service Connect endpoints on ports 27015 through 27017".

Comment by Corry Root [ 21/Mar/23 ]

sarah.simpers@mongodb.com, I updated the GCP Private Endpoint connection string port numbers to align with the note, "Atlas services are accessed through Private Service Connect endpoints on ports 27015 through 27017".

Generated at Thu Feb 08 08:14:15 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.