# ROSA with Hosted Control Planes Launch > Console UX and documentation designed for the ROSA hosted control planes launch, standardizing terminology across AWS and Red Hat for a new Marketplace billing model. Rendered version: https://codyanthony.dev/case-studies/console-ux/rosa-hcp-console-integration/ Author: Cody Anthony (https://codyanthony.dev/about/) --- ROSA launched a new deployment model, ROSA with hosted control planes (HCP), that creates clusters in about 10 minutes instead of the 40-plus that ROSA Classic takes. For the Q2 2023 launch, I designed the console UI text and the user documentation in parallel and aligned terminology across AWS and Red Hat for a new Marketplace billing model. This is the console and documentation view; for the broader ROSA information-architecture work, see [ROSA Jobs-to-be-Done Content Redesign](/case-studies/systems-strategy/rosa-jtbd-redesign/). The cluster provisioning guide for HCP is covered in [ROSA with HCP Getting Started Guide](/case-studies/architecture-guides/rosa-getting-started/). *(image: ROSA Console Get Started Page)* _ROSA console Get Started page guiding customers through the enablement workflow_ ## The challenge ROSA with hosted control planes introduced a second deployment and billing model alongside ROSA Classic. Classic and HCP required different AWS Marketplace contract paths, so the console could not rely on one generic enablement flow. Customers needed to understand which model they were choosing, why the billing setup differed, and what to do next. The experience also spanned company boundaries. Customers moved from AWS Marketplace enablement to the AWS console, AWS documentation, and then the Red Hat console for cluster creation. The launch needed clear differentiation between Classic and HCP, a smooth AWS-to-Red Hat transition, and consistent terminology across both companies' surfaces. *(image: ROSA Contracts Page)* _Contracts page showing the ROSA with hosted control planes option with consistent terminology_ ## Aligning terminology first Before design work began, I organized sessions with AWS and Red Hat product leadership to standardize the naming. We aligned on **ROSA with hosted control planes**, because “with hosted control planes” was already standard across Red Hat products and helped customers connect the ROSA launch to the broader OpenShift portfolio. Settling terminology up front kept the AWS console, AWS documentation, and Red Hat materials consistent, and prevented downstream rework as the launch moved through design, documentation, and product review. ## Designing the console and documentation together Over weekly design workshops with the product manager, UX designer, and console developer, I drafted the console microcopy, help-panel content, and user documentation together, then revised them against UX, PM, and engineering feedback. I wrote the UI text for the six states of the ROSA Enablement card on the console homepage, from not-yet-enabled through setup, enabled, and the error states. Each state gave customers a clear status and next step. I also wrote the pricing-card text that explained the relationship between HCP and Classic. I created the help-panel content from scratch for the new experience, including guidance on why AWS Marketplace integration was required and how HCP billing differed from Classic. The goal was to answer billing and enablement questions at the point of need, before customers left the console flow. The documentation was built as part of the same product surface. I gathered inputs from product, UX, engineering, solution architects, and Red Hat partners, then validated the workflows through hands-on testing, which surfaced gaps the specs alone did not. I also reviewed Red Hat's parallel HCP Quickstart and STS cluster-creation guides for AWS terminology accuracy and prerequisite alignment, so the cross-company journey stayed consistent. *(image: ROSA Help Panel)* _Help panel providing contextual guidance on ROSA enablement requirements_ *(image: Contract Purchase Wizard)* _Contract purchase workflow with UI text guiding customers through billing setup_ ## What this demonstrates - Designing console UI text, help panels, and documentation as one launch experience - Establishing terminology governance before design and documentation work scaled - Explaining two billing models without overcomplicating the customer path - Validating product workflows through hands-on testing, not specs alone - Coordinating cross-company guidance across AWS and Red Hat surfaces ## Outcomes The console and documentation shipped on schedule for the Q2 2023 HCP launch, enabling a strategically important ROSA offering. Customers got a clearer path for choosing between Classic and HCP, understanding the billing difference, and moving from AWS Marketplace setup into cluster creation. The terminology alignment kept AWS and Red Hat materials consistent, while the integrated console-and-docs process moved through UX approval with minimal rework. The work established a pattern for later ROSA experiences: align terminology first, design the console and documentation together, and validate the end-to-end workflow before launch. ## Live documentation - [Getting Started with ROSA](https://docs.aws.amazon.com/rosa/latest/userguide/getting-started.html) — landing page orienting customers to deployment options and choosing between HCP and Classic ([archived snapshot](https://web.archive.org/web/20260508131622/https://docs.aws.amazon.com/rosa/latest/userguide/getting-started.html)) - [Getting Started with HCP](https://docs.aws.amazon.com/rosa/latest/userguide/getting-started-hcp.html) — step-by-step HCP cluster creation workflow, validated through hands-on testing ([archived snapshot](https://web.archive.org/web/20260412124606/https://docs.aws.amazon.com/rosa/latest/userguide/getting-started-hcp.html)) - [Set Up Prerequisites](https://docs.aws.amazon.com/rosa/latest/userguide/set-up.html) — AWS account configuration, IAM permissions, and service enablement steps ([archived snapshot](https://web.archive.org/web/20260210200653/https://docs.aws.amazon.com/rosa/latest/userguide/set-up.html)) - [Troubleshooting ROSA](https://docs.aws.amazon.com/rosa/latest/userguide/troubleshooting-rosa.html) — common HCP enablement and Marketplace integration issues ([archived snapshot](https://web.archive.org/web/20260103122703/https://docs.aws.amazon.com/rosa/latest/userguide/troubleshooting-rosa.html))