@@ -40,8 +40,11 @@ configuration of your {+clusters+}.
40
40
{+service+} enforces |tls-ssl| encryption for all connections to your
41
41
databases.
42
42
43
- We recommend using M10+ dedicated {+clusters+} because all {+service+} projects with one or more M10+ dedicated {+clusters+} receive
44
- their own dedicated |vpc| on {+aws+} or {+gcp+} (or {+vnet+} if you use |azure|).
43
+ We recommend using M10+ dedicated {+clusters+} because all {+service+} projects with
44
+ one or more M10+ dedicated {+clusters+} receive their own dedicated:
45
+ - |vpc| on {+aws+} or {+gcp+}.
46
+ - {+vnet+} on |azure|.
47
+
45
48
{+service+} deploys all dedicated clusters inside this |vpc| or {+vnet+}.
46
49
47
50
By default, all access to your {+clusters+} is blocked. You must explicitly allow
@@ -61,17 +64,15 @@ Features
61
64
```````````
62
65
63
66
{+service+} enforces mandatory |tls| encryption of connections to your
64
- databases. |tls| 1.2 is the default protocol; you can select |tls| 1.1
65
- or |tls| 1.0 if necessary, but we do not recommend protocols lower than
66
- the default. To learn more, see the
67
+ databases. |tls| 1.2 is the default protocol. To learn more, see the
67
68
:guilabel:`Set Minimum TLS Protocol Version` section of
68
69
:ref:`Configure Additional Settings
69
70
<create-cluster-additional-settings>`.
70
71
71
72
{+ip-access-list+}s
72
73
```````````````````````````````
73
74
74
- As a |service| administrator, you can:
75
+ As an |service| administrator, you can:
75
76
76
77
You can configure {+ip-access-list+}s to limit which IP addresses can
77
78
attempt authentication to your database.
@@ -85,8 +86,6 @@ You can configure :atlas:`temporary access list entries
85
86
</security/ip-access-list/#add-ip-access-list-entries>`
86
87
that expire automatically after a user-defined period.
87
88
88
- You can create one access list per project.
89
-
90
89
Firewall Configuration
91
90
``````````````````````
92
91
@@ -103,7 +102,17 @@ cases of {+cluster+} changes such as :ref:`vertical scaling
103
102
certain topology changes, such as a :ref:`conversion from replica set
104
103
to sharded cluster <scale-cluster-sharding>`, the
105
104
:ref:`addition of shards <scale-cluster-shardNum>`, or a :ref:`region
106
- change <scale-cluster-region>` require that you use new IP addresses.
105
+ change <scale-cluster-region>` require that you use new IP addresses.
106
+
107
+ In the case of converting from a replica set to a sharded cluster, the
108
+ failure to reconnect the application clients might cause your application
109
+ to suffer from data outages. If you use a |dns| seed list
110
+ connection string, your application automatically connects to the |mongos|
111
+ for your sharded cluster. If you use a standard connection string,
112
+ you must update your connection string to reflect your new cluster topology.
113
+
114
+ In the case of adding new shards, the failure to reconnect the application
115
+ clients may cause your application to suffer from a data outage.
107
116
108
117
VPC/{+vnet+} Peering
109
118
`````````````````````````````
@@ -117,7 +126,8 @@ application environment, minimizing the need for {+service+} to make
117
126
outbound access requests to peer |vpc|\s. However, if you configure {+service+}
118
127
to use |ldap| authentication, you must enable {+service+} to
119
128
connect outbound to the authentication endpoint of your peer |vpc| over the |ldap|
120
- protocol.
129
+ protocol. Note that |ldap| authentication is deprecated on {+service+} with 8.0.
130
+ We recommend that you use {+wif+} and |workload| instead.
121
131
122
132
You can choose your {+service+} |cidr| block with the |vpc| peering wizard
123
133
before you deploy your first {+cluster+}. The {+service+} |vpc| |cidr|
@@ -144,7 +154,7 @@ private endpoints are available:
144
154
- {+azure+} :azure:`Private Link </private-link/private-link-overview>`,
145
155
for connections from {+azure+} {+vnet+}s
146
156
- :gcp:`Private Service Connect </vpc/docs/private-service-connect>`, for
147
- connections from {+gcp+}
157
+ connections from {+gcp+} |vpc|s
148
158
149
159
.. figure:: /includes/images/private-link.svg
150
160
:alt: "An image representing how MongoDB Atlas private endpoints work."
0 commit comments