Skip to content

Commit 021671b

Browse files
authored
Merge pull request #58047 from jneczypor/OSDOCS-3796
OSDOCS-3796: Private/Public Subnet
2 parents bda393e + 4c95f89 commit 021671b

File tree

3 files changed

+21
-2
lines changed

3 files changed

+21
-2
lines changed

modules/ccs-aws-provisioned.adoc

Lines changed: 6 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -64,7 +64,12 @@ Two buckets are required with a typical size of 2 TB each.
6464
Customers should expect to see one VPC per cluster. Additionally, the VPC needs the following configurations:
6565

6666
* *Subnets*: Two subnets for a cluster with a single availability zone, or six subnets for a cluster with multiple availability zones.
67-
67+
+
68+
[NOTE]
69+
====
70+
A *public subnet* connects directly to the internet through an internet gateway. A *private subnet* connects to the internet through a network address translation (NAT) gateway.
71+
====
72+
+
6873
* *Route tables*: One route table per private subnet, and one additional table per cluster.
6974

7075
* *Internet gateways*: One Internet Gateway per cluster.

modules/osd-aws-privatelink-architecture.adoc

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,7 @@
1+
// Module included in the following assemblies:
2+
//
3+
// * rosa_architecture/rosa_architecture_sub/rosa-architecture-models.adoc
4+
15
[id="osd-aws-privatelink-architecture.adoc_{context}"]
26
= AWS PrivateLink architecture
37

@@ -19,6 +23,11 @@ image::156_OpenShift_ROSA_Arch_0621_privatelink.svg[Multi-AZ AWS PrivateLink clu
1923

2024
AWS provides multiple reference architectures that can be useful to customers when planning how to set up a configuration that uses AWS PrivateLink. Here are three examples:
2125

26+
[NOTE]
27+
====
28+
A *public subnet* connects directly to the internet through an internet gateway. A *private subnet* connects to the internet through a network address translation (NAT) gateway.
29+
====
30+
2231
* VPC with a private subnet and AWS Site-to-Site VPN access.
2332
+
2433
This configuration enables you to extend your network into the cloud without exposing your network to the internet.

modules/rosa-aws-provisioned.adoc

Lines changed: 6 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -67,7 +67,12 @@ Two buckets are required with a typical size of 2TB each.
6767
Customers should expect to see one VPC per cluster. Additionally, the VPC will need the following configurations:
6868

6969
* *Subnets*: Two subnets for a cluster with a single availability zone, or six subnets for a cluster with multiple availability zones.
70-
70+
+
71+
[NOTE]
72+
====
73+
A *public subnet* connects directly to the internet through an internet gateway. A *private subnet* connects to the internet through a network address translation (NAT) gateway.
74+
====
75+
+
7176
* *Route tables*: One route table per private subnet, and one additional table per cluster.
7277

7378
* *Internet gateways*: One Internet Gateway per cluster.

0 commit comments

Comments
 (0)