You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -53,7 +54,7 @@ Create a MongoDB cluster with a cluster read replica in another region by using
53
54
:::image type="content" source="media/quickstart-cross-region-replication/select-access-to-cross-region-replication-preview.png" alt-text="Screenshot of the access to global distribution preview.":::
54
55
55
56
> [!IMPORTANT]
56
-
> You should select **Access to global distribution (preview)** during provisioning to be able to create a preview replica cluster.
57
+
> You should select **Access to global distribution (preview)** during provisioning to be able to create a preview replica cluster.
57
58
58
59
1. On the **Create Azure Cosmos DB for MongoDB cluster** page, select the **Configure** option within the **Cluster tier** section.
59
60
@@ -87,7 +88,7 @@ Create a MongoDB cluster with a cluster read replica in another region by using
87
88
88
89
1. Select **Next: Global distribution (preview)**.
89
90
90
-
1.Select**Enable** for **Read replica in another region (preview)** to create a cluster read replica as a part of this new primary cluster provisioning.
91
+
1.On the **Global distribution (preview)** tab, select**Enable** for **Read replica in another region (preview)** to create a cluster read replica as a part of this new primary cluster provisioning.
91
92
92
93
1. In the **Read replica name** field, enter a name for the cluster read replica. It should be a globally unique cluster name.
93
94
@@ -109,26 +110,30 @@ You can also select add 0.0.0.0 - 255.255.255.255 firewall rule to allow not jus
109
110
110
111
1. Select **Review + create**.
111
112
112
-
1. Review the settings you provide, and then select **Create**. It takes a few minutes to create the cluster. Wait for the portal page to display **Your deployment is complete** before moving on.
113
+
1. Review the settings you provided, and then select **Create**. It takes a few minutes to create the cluster. Wait for the portal page to display **Your deployment is complete** before moving on.
113
114
114
115
1. Select **Go to resource** to go to the Azure Cosmos DB for MongoDB cluster page.
115
116
116
117
:::image type="content" source="media/quickstart-portal/deployment-complete.png" alt-text="Screenshot of the deployment page for a cluster.":::
117
118
118
-
## Get cluster credentials
119
+
## Connect to the cluster and ingest data
119
120
120
-
Get the connection string you need to connect to this cluster using your application code.
121
+
Get the connection string you need to connect to this primary cluster using your application code.
121
122
122
-
1. From the Azure Cosmos DB for MongoDB vCore cluster page, select the **Connection strings** navigation menu option.
123
+
1. From the Azure Cosmos DB for MongoDB vCore primary cluster page, select the **Connection strings** navigation menu option under **Settings**.
123
124
124
-
:::image type="content" source="media/quickstart-portal/select-connection-strings-option.png" alt-text="Screenshot of the connection strings option on the page for a cluster.":::
125
+
:::image type="content" source="media/quickstart-cross-region-replication/select-connection-strings-option.png" alt-text="Screenshot of the connection strings page in the cluster propteries.":::
125
126
126
127
1. Record the value from the **Connection string** field.
128
+
129
+
> [!IMPORTANT]
130
+
> The connection string in the portal does not include the username and password values. You must replace the `<user>` and `<password>` placeholders with the credentials you entered when you created the cluster.
127
131
128
-
:::image type="content" source="media/quickstart-portal/connection-string-value.png" alt-text="Screenshot of the connection string credential for a cluster.":::
132
+
1. In MongoDB shell, connect to the primary cluster using the connection string.
129
133
130
-
> [!IMPORTANT]
131
-
> The connection string in the portal does not include the username and password values. You must replace the `<user>` and `<password>` placeholders with the credentials you used when you originally created the cluster.
0 commit comments