Skip to content

Commit fc35096

Browse files
authored
(DOCSP-44659) addressing feedback from stakeholders (#102)
* (DOCSP-44659) addressing feedback from stakeholders * (DOCSP-44659) errors from build log * (DOCSP-44659) copy fix
1 parent e4622c8 commit fc35096

File tree

1 file changed

+21
-11
lines changed

1 file changed

+21
-11
lines changed

source/network-security.txt

Lines changed: 21 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -40,8 +40,11 @@ configuration of your {+clusters+}.
4040
{+service+} enforces |tls-ssl| encryption for all connections to your
4141
databases.
4242

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+
4548
{+service+} deploys all dedicated clusters inside this |vpc| or {+vnet+}.
4649

4750
By default, all access to your {+clusters+} is blocked. You must explicitly allow
@@ -61,17 +64,15 @@ Features
6164
```````````
6265

6366
{+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
6768
:guilabel:`Set Minimum TLS Protocol Version` section of
6869
:ref:`Configure Additional Settings
6970
<create-cluster-additional-settings>`.
7071

7172
{+ip-access-list+}s
7273
```````````````````````````````
7374

74-
As a |service| administrator, you can:
75+
As an |service| administrator, you can:
7576

7677
You can configure {+ip-access-list+}s to limit which IP addresses can
7778
attempt authentication to your database.
@@ -85,8 +86,6 @@ You can configure :atlas:`temporary access list entries
8586
</security/ip-access-list/#add-ip-access-list-entries>`
8687
that expire automatically after a user-defined period.
8788

88-
You can create one access list per project.
89-
9089
Firewall Configuration
9190
``````````````````````
9291

@@ -103,7 +102,17 @@ cases of {+cluster+} changes such as :ref:`vertical scaling
103102
certain topology changes, such as a :ref:`conversion from replica set
104103
to sharded cluster <scale-cluster-sharding>`, the
105104
: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.
107116

108117
VPC/{+vnet+} Peering
109118
`````````````````````````````
@@ -117,7 +126,8 @@ application environment, minimizing the need for {+service+} to make
117126
outbound access requests to peer |vpc|\s. However, if you configure {+service+}
118127
to use |ldap| authentication, you must enable {+service+} to
119128
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.
121131

122132
You can choose your {+service+} |cidr| block with the |vpc| peering wizard
123133
before you deploy your first {+cluster+}. The {+service+} |vpc| |cidr|
@@ -144,7 +154,7 @@ private endpoints are available:
144154
- {+azure+} :azure:`Private Link </private-link/private-link-overview>`,
145155
for connections from {+azure+} {+vnet+}s
146156
- :gcp:`Private Service Connect </vpc/docs/private-service-connect>`, for
147-
connections from {+gcp+}
157+
connections from {+gcp+} |vpc|s
148158

149159
.. figure:: /includes/images/private-link.svg
150160
:alt: "An image representing how MongoDB Atlas private endpoints work."

0 commit comments

Comments
 (0)