diff --git a/modules/installation-configuration-parameters.adoc b/modules/installation-configuration-parameters.adoc index 2c50e3bf27a7..1ce1824a9986 100644 --- a/modules/installation-configuration-parameters.adoc +++ b/modules/installation-configuration-parameters.adoc @@ -805,21 +805,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. @@ -841,10 +826,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. @@ -861,6 +842,20 @@ can be specified for EC2, S3, IAM, Elastic Load Balancing, Tagging, Route 53, and STS AWS services. |Valid link:https://docs.aws.amazon.com/general/latest/gr/rande.html[AWS service endpoint] name. +|`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.url` |The AWS service endpoint URL. The URL must use the `https` protocol and the host must trust the certificate.