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
Copy file name to clipboardExpand all lines: README.md
+23-1Lines changed: 23 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -297,7 +297,7 @@ The monitoring script sets up email alerts and a monitoring endpoint for your Mo
297
297
298
298
## Managing Replica Sets
299
299
300
-
If you're setting up a replica set with multiple nodes, you'll need to add secondary nodes to the replica set.
300
+
This deployment uses x509 certificate authentication for replica set members, providing enhanced security compared to the traditional keyFile authentication method.
301
301
302
302
1.**Set up secondary nodes**:
303
303
@@ -311,17 +311,39 @@ If you're setting up a replica set with multiple nodes, you'll need to add secon
The `provision_ssl.sh` script will automatically get the domain name from your config.json file and use it to configure the replica set.
328
+
329
+
**Note about x509 Authentication**: This deployment uses x509 certificate authentication for replica set members instead of the traditional keyFile method. The x509 certificates provide stronger security and are more flexible for certificate rotation.
330
+
331
+
The replica certificate should be placed at `/etc/ssl/mongodb/replicas.pem` on each node. This file must contain both the certificate and its private key in PEM format, similar to the server certificate. The certificate should be signed by the same CA as the server certificate.
0 commit comments