Correcting Billing Account Information for HCP clusters

Updated

CONTEXT:

Deploying Red Hat OpenShift Service on AWS Hosted Control Planes (ROSA HCP) clusters requires to subscribe to the ROSA on the AWS console and link the AWS account to the 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 Red Hat OpenShift Service on AWS activation and account linking captures the full process along with the detailed steps involved.

COMMON ISSUE:

The customer's AWS account was linked to a different/personal Red Hat organization. This can lead to the following issues:

  • The AWS account is not seeing in the list of AWS billing accounts when deploying a ROSA HCP cluster.
  • An error is observed when trying to link the AWS account to the Red Hat organization.
  • A ROSA HCP cluster may accidentally be deployed by using a different AWS billing account for ROSA subscription fees and now unable to switch the AWS billing account for that 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:

Please create a support case in our support portal and provide:

  • The AWS account ID
  • The current Red Hat account number linked to the AWS account
  • The new Red Hat account number to be linked with this AWS account
Category
Article Type