mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-05 12:46:18 +01:00
Typo fixes for main
This commit is contained in:
committed by
openshift-cherrypick-robot
parent
091f438767
commit
54cf709c80
@@ -68,7 +68,7 @@ image::rosa-continue-rh-6.png[]
|
||||
+
|
||||
image::rosa-login-rh-account-7.png[]
|
||||
+
|
||||
* You can also register for a new Red{nbsp}Hat account or reset your password on this page.
|
||||
* You can also register for a new Red{nbsp}Hat account or reset your password on this page.
|
||||
* Make sure to log in to the Red{nbsp}Hat account that you plan to associate with the AWS account where you have activated {hcp-title} in previous steps.
|
||||
* Only a single AWS account that will be used for service billing can be associated with a Red{nbsp}Hat account. Typically an organizational AWS account that has other AWS accounts, such as developer accounts, linked would be the one that is to be billed, rather than individual AWS end user accounts.
|
||||
* Red{nbsp}Hat accounts belonging to the same Red{nbsp}Hat organization will be linked with the same AWS account. Therefore, you can manage who has access to creating {hcp-title} clusters on the Red{nbsp}Hat organization account level.
|
||||
@@ -133,7 +133,7 @@ Do not share your unique token.
|
||||
|
||||
. The final prerequisite before your first cluster deployment is making sure the necessary account-wide roles and policies are created. The `rosa` CLI can help with that by using the command shown under step _2.2. To create the necessary account-wide roles and policies quickly…_ on the web console. The alternative to that is manual creation of these roles and policies.
|
||||
|
||||
. After logging in, creating the account roles, and verifying your identity using the `rosa whoami` command, your terminal will look similar to this:
|
||||
. After logging in, creating the account roles, and verifying your identity using the `rosa whoami` command, your terminal will look similar to this:
|
||||
+
|
||||
image::rosa-whoami-14.png[]
|
||||
|
||||
@@ -174,7 +174,7 @@ image::rosa-deploy-ui-19.png[]
|
||||
+
|
||||
image::rosa-deploy-ui-hcp-20.png[]
|
||||
|
||||
. The next step *Accounts and roles* allows you specifying the infrastructure AWS account, into which the the ROSA cluster will be deployed and where the resources will be consumed and managed:
|
||||
. The next step *Accounts and roles* allows you specifying the infrastructure AWS account, into which the ROSA cluster will be deployed and where the resources will be consumed and managed:
|
||||
+
|
||||
image::rosa-ui-account-21.png[]
|
||||
+
|
||||
@@ -191,12 +191,9 @@ image::rosa-ui-billing-22.png[]
|
||||
* You can see an indicator whether the ROSA contract is enabled for a given AWS billing account or not.
|
||||
* In case you would like to use an AWS account that does not have a contract enabled yet, you can either use the _Connect ROSA to a new AWS billing account_ to reach the ROSA AWS console page, where you can activate it after logging in using the respective AWS account by following steps described earlier in this tutorial, or ask the administrator of the AWS account to do that for you.
|
||||
|
||||
The following steps past the billing AWS account selection are beyond the scope of this tutorial.
|
||||
The following steps past the billing AWS account selection are beyond the scope of this tutorial.
|
||||
|
||||
.Additional resources
|
||||
|
||||
* For information on using the CLI to create a cluster, see xref:../rosa_hcp/rosa-hcp-sts-creating-a-cluster-quickly.adoc#rosa-hcp-sts-creating-a-cluster-cli_rosa-hcp-sts-creating-a-cluster-quickly[Creating a ROSA with HCP cluster using the CLI].
|
||||
* See link:https://cloud.redhat.com/learning/learn:getting-started-red-hat-openshift-service-aws-rosa/resource/resources:how-deploy-cluster-red-hat-openshift-service-aws-using-console-ui[this learning path] for more details on how to complete ROSA cluster deployment using the web console.
|
||||
|
||||
|
||||
|
||||
|
||||
Reference in New Issue
Block a user