Correcting Billing Account Information for HCP clusters

Background: Customers deploying ROSA with HCP clusters are required to subscribe to ROSA on the AWS console and link their AWS account to their Red Hat organization as part of the subscription enablement and account linking process. This AWS account can then be used by the team members within the customer’s Red Hat organization for ROSA subscription charges as part of the ROSA HCP cluster deployment process. This This page is not included, but the link has been rewritten to point to the nearest parent document.ROSA with HCP activation and account linking tutorial captures the full process along with the detailed steps involved.

Issue: The customer has linked their AWS account to a different Red Hat organization. This can lead to the following issues:

• Customers don’t see the AWS account in the list of AWS billing accounts when deploying a ROSA with HCP cluster.
• Customers see an error when they try to link the AWS account to their Red Hat organization.
• Customers may accidentally deploy a ROSA with HCP cluster using a different AWS billing account for ROSA subscription fees and now are unable to switch the AWS billing account for their cluster.
  Note: If the wrong billing account is linked during deployment, it can be updated later through self-service using the ROSA CLI or OCM UI. Refer to this documentation for more information.

Solution: Customers should contact Red Hat support and provide the AWS account ID and the Red Hat organization that it is currently linked to (incorrectly) as well as the correct Red Hat organization that it should be linked to.