OSDOCS-14486: Pruning 'Prepare Your Environment' book

Author: EricPonvelle

_topic_maps/_topic_map_rosa.yml

@@ -233,21 +233,12 @@ Topics:
 - Name: Prerequisites checklist for deploying ROSA using STS
   File: rosa-cloud-expert-prereq-checklist
 - Name: Detailed requirements for deploying ROSA using STS
-  File: rosa-classic-aws-prereqs
-- Name: Detailed requirements for deploying ROSA with HCP
-  File: rosa-hcp-aws-prereqs
-# Hiding this entry until the HCP migration is completed
-# - Name: Detailed requirements for deploying ROSA using STS
-#   File: rosa-sts-aws-prereqs
+  File: rosa-sts-aws-prereqs
 - Name: ROSA Classic IAM role resources
   File: rosa-sts-ocm-role
-- Name: ROSA with HCP IAM roles and resources
-  File: rosa-hcp-prepare-iam-roles-resources
 ##### NOTE: THE BELOW IS REMOVED AS PART OF OSDOCS-13310
 # - Name: Limits and scalability
 #   File: rosa-limits-scalability
-#- Name: ROSA with HCP limits and scalability
-#  File: rosa-hcp-limits-scalability
 ##### NOTE: THE ABOVE IS REMOVED AS PART OF OSDOCS-13310F
 - Name: Planning your environment
   File: rosa-planning-environment

_topic_maps/_topic_map_rosa_hcp.yml

@@ -164,15 +164,10 @@ Topics:
 - Name: Prerequisites checklist for deploying ROSA with HCP
   File: rosa-cloud-expert-prereq-checklist
 - Name: Detailed requirements for deploying ROSA with HCP
-  File: rosa-hcp-aws-prereqs
-# Hiding this entry until the HCP migration is completed
-# - Name: Detailed requirements for deploying ROSA with HCP
-#   File: rosa-sts-aws-prereqs
+  File: rosa-sts-aws-prereqs
 - Name: Required IAM roles and resources
   File: rosa-hcp-prepare-iam-roles-resources
 ##### NOTE: THE BELOW IS REMOVED AS PART OF OSDOCS-13310
-# - Name: Limits and scalability
-#   File: rosa-limits-scalability
 #- Name: ROSA with HCP limits and scalability
 #  File: rosa-hcp-limits-scalability
 ##### NOTE: THE ABOVE IS REMOVED AS PART OF OSDOCS-13310
@@ -182,8 +177,6 @@ Topics:
   File: rosa-sts-setting-up-environment
 - Name: Planning resource usage in your cluster
   File: rosa-planning-environment
-# - Name: Preparing Terraform to install ROSA clusters
-#   File: rosa-understanding-terraform
 ---
 Name: Install ROSA with HCP clusters
 Dir: rosa_hcp

cloud_experts_tutorials/cloud-experts-getting-started/cloud-experts-getting-started-deploying/cloud-experts-getting-started-detailed-cli-guide.adoc

@@ -142,7 +142,7 @@ The default settings are as follows:
 ** 2 infrastructure nodes
 ** 2 worker nodes
 ** No autoscaling
-** See the documentation on xref:../../../rosa_planning/rosa-classic-aws-prereqs.adoc#rosa-ec2-instances_rosa-classic-aws-prereqs[ec2 instances] for more details. 
+** See the documentation on xref:../../../rosa_planning/rosa-sts-aws-prereqs.adoc#rosa-ec2-instances_rosa-sts-aws-prereqs[ec2 instances] for more details. 
 // This link needs to remain hidden until the HCP migration is published
 // ** See the documentation on xref:../../../rosa_planning/rosa-sts-aws-prereqs.adoc#rosa-ec2-instances_rosa-sts-aws-prereqs[ec2 instances] for more details.  
 * Region: As configured for the `aws` CLI

cloud_experts_tutorials/cloud-experts-getting-started/cloud-experts-getting-started-deploying/cloud-experts-getting-started-hcp.adoc

@@ -152,7 +152,7 @@ echo "export PRIVATE_SUBNET_ID=$PRIVATE_SUBNET_ID"
 +
 [role="_additional-resources"]
 .Additional resources
-* For more about VPC requirements, see the xref:../../../rosa_planning/rosa-classic-aws-prereqs.adoc#rosa-vpc_rosa-classic-aws-prereqs[VPC documentation].
+* For more about VPC requirements, see the xref:../../../rosa_planning/rosa-sts-aws-prereqs.adoc#rosa-vpc_rosa-sts-aws-prereqs[VPC documentation].
 // This link needs to remain hidden until the HCP migration is published
 // * For more about VPC requirements, see the xref:../../../rosa_planning/rosa-sts-aws-prereqs.adoc#rosa-vpc_rosa-sts-aws-prereqs[VPC documentation].
 

cloud_experts_tutorials/cloud-experts-getting-started/cloud-experts-getting-started-what-is-rosa.adoc

@@ -134,7 +134,7 @@ etcd encryption is configured the same as in OpenShift Container Platform. The a
 Currently, the ROSA CLI does not accept multi-region KMS keys for EBS encryption. This feature is in our backlog for product updates. The ROSA CLI accepts single region KMS keys for EBS encryption if it is defined at cluster creation.
 
 == Infrastructure
-ROSA uses several different cloud services such as virtual machines, storage, and load balancers. You can see a defined list in the xref:../../rosa_planning/rosa-classic-aws-prereqs.adoc#rosa-aws-policy-provisioned_rosa-classic-aws-prereqs[AWS prerequisites].
+ROSA uses several different cloud services such as virtual machines, storage, and load balancers. You can see a defined list in the xref:../../rosa_planning/rosa-sts-aws-prereqs.adoc#rosa-aws-policy-provisioned_rosa-sts-aws-prereqs[AWS prerequisites].
 // This section needs to remain hidden until the HCP migration is published
 // ROSA uses several different cloud services such as virtual machines, storage, and load balancers. You can see a defined list in the xref:../../rosa_planning/rosa-sts-aws-prereqs.adoc#rosa-aws-policy-provisioned_rosa-sts-aws-prereqs[AWS prerequisites].
 

cloud_experts_tutorials/cloud-experts-getting-started/cloud-experts-rosa-sts-explained.adoc

@@ -64,7 +64,7 @@ STS roles and policies must be created for each ROSA cluster. To make this easie
 
 [id="components-specific-to-rosa-with-sts"]
 == Components specific to ROSA with STS
-* *AWS infrastructure* - This provides the infrastructure required for the cluster. It contains the actual EC2 instances, storage, and networking components. See xref:../../rosa_architecture/rosa_policy_service_definition/rosa-service-definition.adoc#rosa-sdpolicy-aws-compute-types_rosa-service-definition[AWS compute types] to see supported instance types for compute nodes and xref:../../rosa_planning/rosa-classic-aws-prereqs.adoc#rosa-ec2-instances_rosa-classic-aws-prereqs[provisioned AWS infrastructure] for control plane and infrastructure node configuration.
+* *AWS infrastructure* - This provides the infrastructure required for the cluster. It contains the actual EC2 instances, storage, and networking components. See xref:../../rosa_architecture/rosa_policy_service_definition/rosa-service-definition.adoc#rosa-sdpolicy-aws-compute-types_rosa-service-definition[AWS compute types] to see supported instance types for compute nodes and xref:../../rosa_planning/rosa-sts-aws-prereqs.adoc#rosa-ec2-instances_rosa-sts-aws-prereqs[provisioned AWS infrastructure] for control plane and infrastructure node configuration.
 // This section needs to remain hidden until the HCP migration is done
 // * *AWS infrastructure* - This provides the infrastructure required for the cluster. It contains the actual EC2 instances, storage, and networking components. See xref:../../rosa_architecture/rosa_policy_service_definition/rosa-service-definition.adoc#rosa-sdpolicy-aws-compute-types_rosa-service-definition[AWS compute types] to see supported instance types for compute nodes and xref:../../rosa_planning/rosa-sts-aws-prereqs.adoc#rosa-ec2-instances_rosa-sts-aws-prereqs[provisioned AWS infrastructure] for control plane and infrastructure node configuration.
 * *AWS STS* - See the credential method section above.

modules/mos-network-prereqs-min-bandwidth.adoc

@@ -7,13 +7,6 @@
 [id="mos-network-prereqs-min-bandwidth_{context}"]
 = Minimum bandwidth
 
-During cluster deployment, 
-ifdef::openshift-rosa[]
-{rosa-classic-short} 
-endif::openshift-rosa[]
-ifdef::openshift-rosa-hcp[]
-{rosa-short} 
-endif::openshift-rosa-hcp[]
-requires a minimum bandwidth of 120{nbsp}Mbps between cluster infrastructure and the public internet or private network locations that provide deployment artifacts and resources. When network connectivity is slower than 120{nbsp}Mbps (for example, when connecting through a proxy) the cluster installation process times out and deployment fails.
+During cluster deployment, {product-title} requires a minimum bandwidth of 120{nbsp}Mbps between cluster infrastructure and the public internet or private network locations that provide deployment artifacts and resources. When network connectivity is slower than 120{nbsp}Mbps (for example, when connecting through a proxy) the cluster installation process times out and deployment fails.
 
 After cluster deployment, network requirements are determined by your workload. However, a minimum bandwidth of 120{nbsp}Mbps helps to ensure timely cluster and operator upgrades.

modules/osd-aws-privatelink-firewall-prerequisites.adoc

@@ -7,7 +7,7 @@
 :_mod-docs-content-type: PROCEDURE
 ifdef::openshift-rosa[]
 [id="rosa-classic-firewall-prerequisites_{context}"]
-= Firewall prerequisites for {rosa-classic-short} clusters using STS
+= Firewall prerequisites for {product-title} clusters using STS
 endif::openshift-rosa[]
 ifdef::openshift-dedicated[]
 [id="osd-aws-privatelink-firewall-prerequisites_{context}"]
@@ -108,7 +108,7 @@ endif::[]
 
 |`oidc.op1.openshiftapps.com`
 |443
-|Used by ROSA for STS implementation with managed OIDC configuration.
+|Used by {product-title}  for STS implementation with managed OIDC configuration.
 |===
 +
 . Allowlist the following telemetry URLs:

modules/rosa-aws-provisioned.adoc

@@ -6,14 +6,7 @@
 [id="rosa-aws-policy-provisioned_{context}"]
 = Provisioned AWS Infrastructure
 
-This is an overview of the provisioned {AWS} components on a deployed 
-ifdef::openshift-rosa[]
-{rosa-classic-short} 
-endif::openshift-rosa[]
-ifdef::openshift-rosa-hcp[]
-{rosa-short} 
-endif::openshift-rosa-hcp[]
-cluster.
+This is an overview of the provisioned {AWS} components on a deployed {product-title} cluster.
 
 [id="rosa-ec2-instances_{context}"]
 == EC2 instances
@@ -22,13 +15,7 @@ AWS EC2 instances are required to deploy
 ifndef::openshift-rosa-hcp[]
 the control plane and data plane functions for
 endif::openshift-rosa-hcp[]
-ifdef::openshift-rosa[]
-{rosa-classic-short}.
-endif::openshift-rosa[]
-ifdef::openshift-rosa-hcp[]
-{rosa-short}.
-endif::openshift-rosa-hcp[]
-
+{product-title}.
 ifndef::openshift-rosa-hcp[]
 Instance types can vary for control plane and infrastructure nodes, depending on the worker node count.
 
@@ -213,11 +200,4 @@ can add additional custom security groups during cluster creation. Custom securi
 
 * You must create the custom security groups in AWS before you create the cluster. For more information, see link:https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-security-groups.html[Amazon EC2 security groups for Linux instances].
 * You must associate the custom security groups with the VPC that the cluster will be installed into. Your custom security groups cannot be associated with another VPC.
-* You might need to request additional quota for your VPC if you are adding additional custom security groups. For information on AWS quota requirements for 
-ifdef::openshift-rosa[]
-{rosa-classic-short}, 
-endif::openshift-rosa[]
-ifdef::openshift-rosa-hcp[]
-{rosa-short}, 
-endif::openshift-rosa-hcp[]
-see _Required AWS service quotas_ in _Prepare your environment_. For information on requesting an AWS quota increase, see link:https://docs.aws.amazon.com/servicequotas/latest/userguide/request-quota-increase.html[Requesting a quota increase].
+* You might need to request additional quota for your VPC if you are adding additional custom security groups. For information on AWS quota requirements for {product-title} see _Required AWS service quotas_ in _Prepare your environment_. For information on requesting an AWS quota increase, see link:https://docs.aws.amazon.com/servicequotas/latest/userguide/request-quota-increase.html[Requesting a quota increase].

modules/rosa-getting-started-install-configure-cli-tools.adoc

@@ -44,7 +44,7 @@ $ aws sts get-caller-identity  --output text
 +
 . Install and configure the latest ROSA CLI (`rosa`).
 .. Navigate to link:https://console.redhat.com/openshift/downloads[*Downloads*].
-.. Find *Red Hat OpenShift Service on AWS command line interface (`rosa)* in the list of tools and click *Download*.
+.. Find *Red Hat OpenShift Service on AWS command line interface (`rosa`)* in the list of tools and click *Download*.
 +
 The `rosa-linux.tar.gz` file is downloaded to your default download location.
 .. Extract the `rosa` binary file from the downloaded archive. The following example extracts the binary from a Linux tar archive: