Skip to content

Commit 7ac39ff

Browse files
Update README.md
Fix typo
1 parent 0672ca4 commit 7ac39ff

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

terraform/README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
# MongoDB-Atlas-Mirroring-Terraform
22
MongoDB Atlas integration with Microsoft Fabric Mirrored Database.
33

4-
This Terraform code automates the deployment of [MongoBD Fabric Integration](https://github.com/mongodb-partners/MongoDB_Fabric_Mirroring) solution developed by MongoDB Partners team. The resulting environment will have all resources required to synchronise a MongoDB database and collections with Microsoft Fabric Mirrored Database, allowing customers to use the features provided by Microsoft's service with the data stored on MongoDB Atlas.
4+
This Terraform code automates the deployment of [MongoDB Fabric Integration](https://github.com/mongodb-partners/MongoDB_Fabric_Mirroring) solution developed by MongoDB Partners team. The resulting environment will have all resources required to synchronise a MongoDB database and collections with Microsoft Fabric Mirrored Database, allowing customers to use the features provided by Microsoft's service with the data stored on MongoDB Atlas.
55

66
There are two options to deploy the solution; with a private connection between Azure and MongoDB Atlas, and with public internet communication between the services. The former option will incur in additional costs due to the Azure SKU required for isolated environment, and the latter can be deployed using Free tier SKU.
77

@@ -153,4 +153,4 @@ Do you really want to destroy all resources?
153153
3. Run the `curl checkip.amazonaws.com` command to get the IP address being used by the VM to reach the internet
154154
4. Add the IP address obtained on the MongoDB Atlas Network Access list
155155
5. Back to the Azure App Service resource, go to "Overview" on the left-side menu, then click on "Restart" on the top-level menu to restart the VM.
156-
6. Back on the SSH session, check the synch status using the `tail -f mirroring.log` and checking the activities registered in the log file.
156+
6. Back on the SSH session, check the synch status using the `tail -f mirroring.log` and checking the activities registered in the log file.

0 commit comments

Comments
 (0)