Skip to content

Commit ac81e00

Browse files
authored
Merge pull request #44998 from mjpytlak/osdocs-3437
OSDOCS-3437: Installing to the AWS SC2S region
2 parents f8beadf + 4ee3cc8 commit ac81e00

7 files changed

+30
-27
lines changed

_topic_maps/_topic_map.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -157,7 +157,7 @@ Topics:
157157
File: installing-aws-private
158158
- Name: Installing a cluster on AWS into a government region
159159
File: installing-aws-government-region
160-
- Name: Installing a cluster on AWS into a Top Secret Region
160+
- Name: Installing a cluster on AWS into a Secret or Top Secret Region
161161
File: installing-aws-secret-region
162162
- Name: Installing a cluster on AWS into a China region
163163
File: installing-aws-china

installing/installing_aws/installing-aws-secret-region.adoc

Lines changed: 9 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1,12 +1,17 @@
11
:_content-type: ASSEMBLY
22
[id="installing-aws-secret-region"]
3-
= Installing a cluster on AWS into a Top Secret Region
3+
= Installing a cluster on AWS into a Secret or Top Secret Region
44
include::_attributes/common-attributes.adoc[]
55
:context: installing-aws-secret-region
66

77
toc::[]
88

9-
In {product-title} version {product-version}, you can install a cluster on Amazon Web Services (AWS) into a Commercial Cloud Services (C2S) Top Secret Region. To configure the region, modify parameters in the `install config.yaml` file before you install the cluster.
9+
In {product-title} version {product-version}, you can install a cluster on Amazon Web Services (AWS) into the following secret regions:
10+
11+
* Secret Commercial Cloud Services (SC2S)
12+
* Commercial Cloud Services (C2S)
13+
14+
To configure a cluster in either region, you change parameters in the `install config.yaml` file before you install the cluster.
1015

1116
[id="prerequisites_installing-aws-secret-region"]
1217
== Prerequisites
@@ -56,20 +61,17 @@ include::modules/logging-in-by-using-the-web-console.adoc[leveloffset=+1]
5661
[role="_additional-resources"]
5762
[id="additional-resources_installing-aws-secret-region_console"]
5863
.Additional resources
59-
60-
* See xref:../../web_console/web-console.adoc#web-console[Accessing the web console] for more details about accessing and understanding the {product-title} web console.
64+
* xref:../../web_console/web-console.adoc#web-console[Accessing the web console]
6165

6266
include::modules/cluster-telemetry.adoc[leveloffset=+1]
6367

6468
[role="_additional-resources"]
6569
[id="additional-resources_installing-aws-secret-region_telemetry"]
6670
.Additional resources
67-
68-
* See xref:../../support/remote_health_monitoring/about-remote-health-monitoring.adoc#about-remote-health-monitoring[About remote health monitoring] for more information about the Telemetry service.
71+
* xref:../../support/remote_health_monitoring/about-remote-health-monitoring.adoc#about-remote-health-monitoring[About remote health monitoring]
6972

7073
[id="next-steps_installing-aws-secret-region"]
7174
== Next steps
72-
7375
* xref:../../installing/validating-an-installation.adoc#validating-an-installation[Validating an installation].
7476
* xref:../../post_installation_configuration/cluster-tasks.adoc#available_cluster_customizations[Customize your cluster].
7577
* If necessary, you can xref:../../support/remote_health_monitoring/opting-out-of-remote-health-reporting.adoc#opting-out-remote-health-reporting_opting-out-remote-health-reporting[opt out of remote health reporting].

modules/installation-aws-about-government-region.adoc

Lines changed: 5 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -15,22 +15,13 @@ ifdef::aws-gov[]
1515
= AWS government regions
1616
endif::aws-gov[]
1717
ifdef::aws-secret[]
18-
= AWS Top Secret Region
18+
= AWS secret regions
1919
endif::aws-secret[]
2020

2121
ifdef::aws-gov[]
2222
{product-title} supports deploying a cluster to an link:https://aws.amazon.com/govcloud-us[AWS GovCloud (US)] region.
2323
endif::aws-gov[]
2424

25-
ifdef::aws-secret[]
26-
{product-title} supports deploying a cluster to an link:https://aws.amazon.com/federal/us-intelligence-community/[AWS Commercial Cloud Services (C2S) Top Secret Region].
27-
endif::aws-secret[]
28-
29-
ifdef::aws-secret[]
30-
The C2S Top Secret Region does not have a published {op-system-first} Amazon Machine Images (AMI) to select, so you
31-
must upload a custom AMI that belongs to that region.
32-
endif::aws-secret[]
33-
3425
ifdef::aws-gov[]
3526
The following AWS GovCloud partitions are supported:
3627

@@ -39,13 +30,14 @@ The following AWS GovCloud partitions are supported:
3930
endif::aws-gov[]
4031
4132
ifdef::aws-secret[]
42-
The following AWS Top Secret Region partition is supported:
33+
The following AWS secret partitions are supported:
4334

44-
* `us-iso-east-1`
35+
* `us-isob-east-1` (SC2S)
36+
* `us-iso-east-1` (C2S)
4537
4638
[NOTE]
4739
====
48-
The maximum supported MTU in an AWS Top Secret Region is not the same as
40+
The maximum supported MTU in an AWS SC2S and C2S Regions is not the same as
4941
AWS commercial. For more information about configuring MTU during installation,
5042
see the _Cluster Network Operator configuration object_ section in _Installing
5143
a cluster on AWS with network customizations_

modules/installation-aws-config-yaml.adoc

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -373,10 +373,10 @@ endif::openshift-origin[]
373373
endif::private[]
374374
ifdef::secret[]
375375
ifndef::openshift-origin[]
376-
<15> The custom CA certificate. This is required when deploying to the AWS C2S Top Secret Region because the AWS API requires a custom CA trust bundle.
376+
<15> The custom CA certificate. This is required when deploying to the SC2S or C2S Regions because the AWS API requires a custom CA trust bundle.
377377
endif::openshift-origin[]
378378
ifdef::openshift-origin[]
379-
<14> The custom CA certificate. This is required when deploying to the AWS C2S Top Secret Region because the AWS API requires a custom CA trust bundle.
379+
<14> The custom CA certificate. This is required when deploying to the SC2S or C2S Regions because the AWS API requires a custom CA trust bundle.
380380
endif::openshift-origin[]
381381
endif::secret[]
382382
ifdef::restricted[]

modules/installation-aws-regions-with-no-ami.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -43,7 +43,7 @@ endif::aws-china,aws-secret[]
4343

4444
ifdef::aws-china,aws-secret[]
4545
ifdef::aws-china[Red Hat does not publish a {op-system-first} Amazon Machine Image (AMI) for the AWS China regions.]
46-
ifdef::aws-secret[Red Hat does not publish a {op-system-first} Amzaon Machine Image for the AWS Top Secret Region.]
46+
ifdef::aws-secret[Red Hat does not publish a {op-system-first} Amzaon Machine Image for the AWS Secret and Top Secret Regions.]
4747

4848
Before you can install the cluster, you must:
4949

modules/installation-aws-regions.adoc

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -48,9 +48,12 @@ The following AWS GovCloud regions are supported:
4848
* `us-gov-east-1`
4949

5050
[id="installation-aws-c2s_{context}"]
51-
== AWS C2S Secret region
51+
== AWS SC2S and C2S secret regions
5252

53-
The `us-iso-east-1` region is supported.
53+
The following AWS secret regions are supported:
54+
55+
* `us-isob-east-1` Secret Commercial Cloud Services (SC2S)
56+
* `us-iso-east-1` Commercial Cloud Services (C2S)
5457

5558
[id="installation-aws-china_{context}"]
5659
== AWS China regions

modules/installation-custom-aws-vpc.adoc

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -82,7 +82,13 @@ If you are working in a disconnected environment, you are unable to reach the pu
8282
endif::aws-china[]
8383

8484
ifdef::aws-secret[]
85-
* A cluster in a Top Secret Region is unable to reach the public IP addresses for the EC2 and ELB endpoints. You must create a VPC endpoint and attach it to the subnet that the clusters are using. Name the endpoints as follows:
85+
* A cluster in an SC2S or C2S Region is unable to reach the public IP addresses for the EC2 and ELB endpoints. You must create a VPC endpoint and attach it to the subnet that the clusters are using. Name the endpoints as follows:
86+
+
87+
SC2S::
88+
** `elasticloadbalancing.<region>.sc2s.sgov.gov`
89+
** `ec2.<region>.sc2s.sgov.gov`
90+
** `s3.<region>.sc2s.sgov.gov`
91+
C2S::
8692
** `elasticloadbalancing.<region>.c2s.ic.gov`
8793
** `ec2.<region>.c2s.ic.gov`
8894
** `s3.<region>.c2s.ic.gov`

0 commit comments

Comments
 (0)