# ROSA Day 1 Experience > Console automation for ROSA prerequisite validation, paired with AWS-native getting started documentation. Both shipped with the Q4 2022 console launch. Rendered version: https://codyanthony.dev/case-studies/console-ux/rosa-prerequisites-automation/ Author: Cody Anthony (https://codyanthony.dev/about/) --- Enabling ROSA used to mean verifying AWS account prerequisites by hand across multiple AWS service consoles, without AWS-native documentation that guided users through the setup process. For the Q4 2022 ROSA console launch, I created the UI text and help panels for an automated prerequisite-validation experience and wrote the getting-started documentation. Together, the console and docs established a Day 1 pattern for ROSA: automate what the console could verify, explain each prerequisite in context, and connect the experience to matching documentation. *(image: ROSA Get Started Page)* _ROSA Get Started page with automated prerequisite validation checking account readiness before cluster deployment_ ## The challenge Before creating a cluster, customers had to confirm their AWS account met prerequisites across service quotas, IAM permissions, and load balancer integration. The check was entirely manual: customers had to discover the requirements in documentation, then verify them across multiple AWS consoles, with no proactive signal of readiness. As a result, setup issues surfaced late, after customers had already invested time. The documentation path also needed to meet customers where they were starting. For the AWS console launch, customers needed AWS-native getting-started guidance that matched the console experience and explained the same prerequisites in the same terms. The goal was to give customers a coherent Day 1 path from the AWS console to the AWS service guide. *(image: Service Quotas Help Panel)* _Service Quotas help panel explaining why EC2 and EBS quota limits matter for ROSA cluster creation_ ## Automating prerequisite validation I wrote the UI text and help panels for the prerequisite-validation page, turning what had been a manual setup check into a guided readiness experience. The content explained what the console was checking, showed readiness in real time, and helped customers understand what to fix before creating a cluster. The interaction model included introductory text that set expectations, success and error states, quota-specific remediation messages, contextual callouts explaining why each prerequisite mattered, and a final checkpoint before customers proceeded. Instead of discovering setup issues late in the workflow, customers could see account readiness up front and move into cluster creation with clearer guidance. *(image: Help Panel Screenshot)* _Help panel providing contextual guidance on ROSA enablement prerequisites and the automated validation process_ ## Creating an AWS-native Day 1 path Alongside the console work, I wrote the getting-started documentation for the AWS ROSA User Guide: a landing page routing customers to the right workflow, a setup page gathering prerequisites in one place, and step-by-step deployment procedures. The prerequisites in the docs matched the in-console checks, so customers got one consistent story whether they started in the console or the documentation. I worked with the partner documentation team so both sites used consistent AWS service terminology and customers did not encounter conflicting guidance across platforms. ## What this demonstrates - Designing an automated console experience and its documentation as one Day 1 path - Connecting UI text, help panels, and documentation into a coherent customer journey - Aligning in-console validation with documentation so customers received consistent guidance - Creating AWS-native setup guidance for customers starting from the AWS console - Cross-company collaboration on terminology and customer guidance ## Outcomes The coordinated console and documentation experience shipped with the Q4 2022 ROSA console launch, giving customers a complete AWS-native enablement path. Customers could validate account readiness in the console, understand why each prerequisite mattered, and follow matching documentation when they needed deeper setup guidance. The work established a pattern for later ROSA console experiences: automate what the console can verify, explain the requirement in context, and connect the workflow to matching documentation. That pattern carried into later ROSA console work, including the [ROSA with Hosted Control Planes Launch](/case-studies/console-ux/rosa-hcp-console-integration/) and the [ROSA with HCP Getting Started Guide](/case-studies/architecture-guides/rosa-getting-started/). ## Live documentation - [Getting Started with ROSA](https://docs.aws.amazon.com/rosa/latest/userguide/getting-started.html) — landing page orienting customers to ROSA deployment workflows (CLI-based, PrivateLink) ([archived snapshot](https://web.archive.org/web/20260508131622/https://docs.aws.amazon.com/rosa/latest/userguide/getting-started.html)) - [Set Up Prerequisites](https://docs.aws.amazon.com/rosa/latest/userguide/set-up.html) — prerequisite requirements and configuration steps customers validate in the console ([archived snapshot](https://web.archive.org/web/20260210200653/https://docs.aws.amazon.com/rosa/latest/userguide/set-up.html)) - [Create a ROSA Cluster Using the CLI](https://docs.aws.amazon.com/rosa/latest/userguide/getting-started-classic-cli.html) — step-by-step CLI-based cluster creation workflow with STS authentication ([archived snapshot](https://web.archive.org/web/20260412124606/https://docs.aws.amazon.com/rosa/latest/userguide/getting-started-classic-cli.html)) - [Create a ROSA Cluster Using AWS PrivateLink](https://docs.aws.amazon.com/rosa/latest/userguide/getting-started-classic-private-link.html) — PrivateLink deployment workflow for private cluster connectivity ([archived snapshot](https://web.archive.org/web/20260413121002/https://docs.aws.amazon.com/rosa/latest/userguide/getting-started-classic-private-link.html))