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: docs/source/networking.rst
+8-8
Original file line number
Diff line number
Diff line change
@@ -3,22 +3,22 @@
3
3
Network Configurations
4
4
======================
5
5
6
-
CfnCluster leverages Amazon Virtual Private Cloud(VPC) for networking. This provides a very flexiable and configurable networking platform to deploy clusters within. CfnCluster support the following high-level configurations:
6
+
CfnCluster leverages Amazon Virtual Private Cloud(VPC) for networking. This provides a very flexible and configurable networking platform to deploy clusters within. CfnCluster support the following high-level configurations:
7
7
8
8
* Single subnet, master and compute in the same subnet
9
9
* Two subnets, master in one subnet and compute new private subnet
10
-
* Two subnets, master in one subnet and compute in exisiting private subnet
10
+
* Two subnets, master in one subnet and compute in existing private subnet
11
11
12
-
All of these configurations can operate with or without public IP addressing. It can also be deployed to leverage an HTTP proxy for all AWS requests. The combinations of these configurations result in many different deployment scenario's, ranging from a single public subnet with all access over the Internet, to fully private via AWS Direct Connect and HTTP proxy for all traffic.
12
+
All of these configurations can operate with or without public IP addressing. It can also be deployed to leverage an HTTP proxy for all AWS requests. The combinations of these configurations result in many different deployment scenarios, ranging from a single public subnet with all access over the Internet, to fully private via AWS Direct Connect and HTTP proxy for all traffic.
13
13
14
-
Below are some architeture diagrams for some of those scenarios:
14
+
Below are some architecture diagrams for some of those scenarios:
15
15
16
16
.. figure:: images/networking_single_subnet.jpg
17
17
:alt:CfnCluster single subnet
18
18
19
19
CfnCluster in a single public subnet
20
20
21
-
The configuration for this architecture, requires the following settings:
21
+
The configuration for this architecture requires the following settings:
22
22
23
23
`note that all values are examples only`
24
24
@@ -31,9 +31,9 @@ The configuration for this architecture, requires the following settings:
31
31
.. figure:: images/networking_two_subnets.jpg
32
32
:alt:CfnCluster two subnets
33
33
34
-
CfnCluster using two subnets(new private)
34
+
CfnCluster using two subnets(new private)
35
35
36
-
The configuration for this architecture, requires the following settings:
36
+
The configuration for this architecture requires the following settings:
37
37
38
38
`note that all values are examples only`
39
39
@@ -49,7 +49,7 @@ The configuration for this architecture, requires the following settings:
49
49
50
50
CfnCluster in a private subnet connected using Direct Connect
51
51
52
-
The configuration for this architecture, requires the following settings:
52
+
The configuration for this architecture requires the following settings:
0 commit comments