Merge pull request #97802 from bscott-rh/OCPBUGS-54405-4.13

[enterprise-4.13] OCPBUGS#54405 removing invalid parameters from AWS

Author: bscott-rh

modules/installation-configuration-parameters.adoc

@@ -964,21 +964,6 @@ such as `io1`.
 |A list of valid AWS availability zones, such as `us-east-1c`, in a
 link:https://yaml.org/spec/1.2/spec.html#sequence//[YAML sequence].
 
-|`compute.aws.region`
-|The AWS region that the installation program creates compute resources in.
-|Any valid link:https://docs.aws.amazon.com/general/latest/gr/rande.html[AWS region], such as `us-east-1`. You can use the AWS CLI to access the regions available based on your selected instance type. For example:
-[source,terminal]
-----
-aws ec2 describe-instance-type-offerings --filters Name=instance-type,Values=c7g.xlarge
-----
-ifndef::openshift-origin[]
-[IMPORTANT]
-====
-When running on ARM based AWS instances, ensure that you enter a region where AWS Graviton processors are available. See link:https://aws.amazon.com/ec2/graviton/#Global_availability[Global availability] map in the AWS documentation. Currently, AWS Graviton3 processors are only available in some regions.
-====
-endif::openshift-origin[]
-
-
 |`controlPlane.platform.aws.amiID`
 |The AWS AMI used to boot control plane machines for the cluster. This is required for regions that require a custom {op-system} AMI.
 |Any published or custom {op-system} AMI that belongs to the set AWS region. See _{op-system} AMIs for AWS infrastructure_ for available AMI IDs.
@@ -1000,10 +985,6 @@ endif::openshift-origin[]
 control plane machine pool.
 |A list of valid AWS availability zones, such as `us-east-1c`, in a link:https://yaml.org/spec/1.2/spec.html#sequence//[YAML sequence].
 
-|`controlPlane.aws.region`
-|The AWS region that the installation program creates control plane resources in.
-|Valid link:https://docs.aws.amazon.com/general/latest/gr/rande.html[AWS region], such as `us-east-1`.
-
 |`platform.aws.amiID`
 |The AWS AMI used to boot all machines for the cluster. If set, the AMI must
 belong to the same region as the cluster. This is required for regions that require a custom {op-system} AMI.
@@ -1013,6 +994,20 @@ belong to the same region as the cluster. This is required for regions that requ
 |An existing Route 53 private hosted zone for the cluster. You can only use a pre-existing hosted zone when also supplying your own VPC. The hosted zone must already be associated with the user-provided VPC before installation. Also, the domain of the hosted zone must be the cluster domain or a parent of the cluster domain. If undefined, the installation program creates a new hosted zone.
 |String, for example `Z3URY6TWQ91KVV`.
 
+|`platform.aws.region`
+|The AWS region that the installation program creates all cluster resources in.
+|Any valid link:https://docs.aws.amazon.com/general/latest/gr/rande.html[AWS region], such as `us-east-1`. You can use the AWS CLI to access the regions available based on your selected instance type by running the following command:
+[source,terminal]
+----
+$ aws ec2 describe-instance-type-offerings --filters Name=instance-type,Values=c7g.xlarge
+----
+ifndef::openshift-origin[]
+[IMPORTANT]
+====
+When running on ARM based AWS instances, ensure that you enter a region where AWS Graviton processors are available. See link:https://aws.amazon.com/ec2/graviton/#Global_availability[Global availability] map in the AWS documentation. Currently, AWS Graviton3 processors are only available in some regions.
+====
+endif::openshift-origin[]
+
 |`platform.aws.serviceEndpoints.name`
 |The AWS service endpoint name. Custom endpoints are only required for cases
 where alternative AWS endpoints must be used. Custom API endpoints