Planning estimates only. Not a formal quote, commercial offer, contractual commitment, or billing guarantee.
Inspired by Will Garcia’s ROSA Calculator. Thank you, Will, for the original work and for sharing it with the community.
Step 1 - Cluster sizing
Add one or more instance types and total instance counts to build a single-AZ sizing estimate.
| Type | Region | Count | Category | vCPUs | Memory | Actions |
|---|---|---|---|---|---|---|
| Totals | -- | -- | -- | |||
Changes apply automatically.
Model each ROSA HCP cluster and its machine pools. Use each cluster’s filters to choose an instance type, then Create pool(s). The HCP cluster fee is charged once per cluster.
Step 2 - Discounting (optional)
Approx EC2 Savings Plan discount (%)
Private Offer - Red Hat
Additional Programs ROSA is eligible for
AWS Marketplace Private Offers Discount
The AWS Marketplace seller private offer feature enables you to receive product pricing and EULA terms from a seller that aren't publicly available. You negotiate pricing and terms with the seller, and the seller creates a private offer for the AWS account that you designate. You accept the private offer and start receiving the negotiated price and terms of use.
Issued by Red Hat or AWS Partner eligible for Channel Partner Private Offers (CPPO)
AWS and Red Hat PoC Credits Discount
Partner Opportunity Acceleration (POA) funding for POC and Migrations: cash reimbursement, AWS promotional credits.
Discounts for existing Red Hat OpenShift and IBM customers
Customers migrating non-ROSA OpenShift workloads to ROSA are eligible for a 75% discount off the ROSA service fee 1-year contract rate over the remaining term of their non-ROSA OpenShift subscriptions.
AWS Migration Acceleration Program (MAP)
Migration Acceleration Program (MAP) funds support you with migrations or modernizations of any size or workload to AWS, at each phase of the customer’s migration journey. Receive cash or AWS promotional credits to originate opportunities, accelerate customer migration or modernizations workloads to AWS and grow your Migration practices on AWS.
AWS VMware Migration Accelerator
Until December 31, 2024, VMware Cloud on AWS customers can earn AWS promotional credits for migrating virtual machines (VMs) to Amazon EC2.
- Migrate 80+ VMs in a month, get up to $400 credit per migrated VM
- Migrate 40 to 79 VMs in a month, get up to $200 credit per migrated VM
To qualify, each migrated VM must run on AWS for at least 720 hours after migration. VMware Migration Accelerator incentives are not applicable to Amazon EC2 T2 and T3 instances.
AWS Windows Migration Accelerator
Save costs with AWS Promotional Credits when you accelerate migrations of Windows workloads to AWS. Until December 31, 2024, customers using Application Migration Service to migrate:
- At least 40 servers to AWS in one month, including a minimum of 15 Windows servers, may be eligible to receive a $200 AWS Promotional Credit per Windows server.
- If you migrate more than 80 servers, including at least 25 Windows servers, in a calendar month, we will increase the discount to $250 AWS Promotional Credit for each Windows server you migrate to AWS using AWS Application Migration Service.
Contact WMA-MGN@amazon.com
AWS Partner Network (APN) Innovation Sandbox Credits
Offset AWS usage costs incurred during solution development with AWS Promotional Credits as part of the Innovation Sandbox program. AWS Partners can integrate AWS services into offerings and launch solutions built on AWS, faster and more efficiently.
Program eligibility and terms change over time, confirm with AWS and Red Hat before relying on these incentives.
Step 3 - Results
Machine pool cost summary using min steady-state nodes. All costs are USD.
Excluded costs: EBS volumes, load balancers (NLB/ELB), data transfer, NAT gateways, and other AWS charges outside worker EC2 pricing.
EC2 costs are based on a pricing snapshot from the last collection date in this repository. For official ROSA service pricing details, see AWS ROSA pricing.
Supported regions and instance types follow the official Red Hat ROSA policies and service definition.
| Cluster | Pool | Region | Instance type | Count | vCPUs | Memory | EC2 cost | Node Fee | Total cost |
|---|---|---|---|---|---|---|---|---|---|
| HCP cluster fee | -- | ||||||||
| Total | |||||||||
Private Offer comparison
Private Offer affects the Worker Node Fee only. EC2 and HCP cluster fee stay the same across rows. The highlighted row matches your Step 2 selection.
| Private Offer | Node Fee | Scenario total | vs selected |
|---|
Step 4 - Platform Comparison and TCO
ROSA HCP and EKS Auto Mode are both AWS first-party services (jointly delivered with Red Hat for ROSA). They are not a Red Hat vs AWS contest. They optimize for different jobs: ROSA HCP is a turnkey application platform (OpenShift with built-in developer and ops capabilities), while EKS Auto Mode is a managed Kubernetes container scheduler where you assemble more of the surrounding platform yourself.
The tables below compare planning costs for the same Step 1 worker mix. The 1-year view is service and infrastructure oriented; the capabilities matrix and 3-year TCO show where the product focus differences show up in tooling and operations.
Assumptions: ROSA Worker Node Fee uses the standard 1-year Private Offer (33% off PAYGO). HCP cluster fee and EC2 stay at list (no standard published % off the cluster fee; EC2 discounts vary by AWS account). EKS Auto Mode management fee is about 12% of worker On-Demand EC2. EKS includes AWS Business Support at 10% of modeled EKS AWS spend (list-price proxy). ROSA Red Hat Premium Support is included (no dollar line). EKS extended Kubernetes support ($0.60/hr) is not in this table; it is an additional potential cost if you stay past the 14-month standard window (see lifecycle and 3-year TCO).
| Cost component | ROSA HCP (1-year) | EKS Auto Mode (1-year) |
|---|
Capabilities
✓ included/supported · ✗ not included · ? partial, add-on, or BYO. Narrative only; not modeled in the cost table.
| Capability | ROSA | EKS | Difference |
|---|
Version support lifecycle
Non-cost distinction: how long you can stay on a minor version before upgrades or higher fees. ROSA EUS Term 1 (Long-Life Additional Term 1) is included with Premium-class ROSA for even OpenShift minors.
| Topic | ROSA HCP | EKS Auto Mode |
|---|
3-year TCO
36-month total. ROSA Worker Node Fee uses the standard 3-year Private Offer (55% off PAYGO); HCP cluster fee and EC2 stay at list (Premium / EUS Term 1 included; Term 2/3 not modeled). EKS control plane is modeled as 14 months standard ($0.10/hr), 12 months extended ($0.60/hr), then 10 months standard after upgrade. Worker EC2, Auto Mode (~12%), and AWS Business Support (10%) run for all 36 months. Platform components and platform ops labor are included here only (not in the 1-year table); see note 2 and note 3.
| 3-year component | ROSA HCP (3-year) | EKS Auto Mode (3-year) |
|---|
2. Common platform components only: a conservative EKS planning proxy for monitoring, logging, and GitOps/CI-class services ($3,600/yr base + $600/yr per extra cluster, capped at $10,800/yr). ROSA shows Included for the OpenShift-provided equivalents. Registry storage is treated as a wash. This deliberately excludes heavier enterprise add-ons such as service mesh, Red Hat hardened images, and runtime support; if those are in scope on ROSA, similar commercially supported products would need to be added on EKS and would raise the EKS total further.
3. Platform ops FTEs are planning estimates stepped by Step 1 cluster count (1 → 1/2, 2–5 → 1.5/3, 6–15 → 2.5/5, 16–40 → 4/8, 41+ → 5/10 ROSA/EKS) at $225,000 fully loaded per FTE per year. Not editable, and not a customer-specific headcount or salary model. Staffing ranges are informed by Forrester TEI analyses of OpenShift operations (for example, The Total Economic Impact of Red Hat OpenShift Cloud Services), which models about two FTEs for ongoing OpenShift cloud-services administration on the composite organization and about 50% improvement in operational efficiency versus prior self-managed infrastructure toil.
This ROSA HCP calculator provides indicative, non-binding estimates to support planning and budgeting. Results are not a quote, offer, or contractual commitment from Red Hat or its affiliates. Actual charges may vary based on provider pricing changes, account configuration, discounts, taxes, region and availability zone specifics, and runtime usage patterns. Validate final pricing through official commercial channels before procurement or budgeting decisions.
How to use the ROSA HCP Cost Calculator
Build an HCP worker-node cost estimate in three steps. Hover any ? or action button for field-level tips. Amounts are planning estimates in USD, not a formal quote.
Step 1 - Cluster sizing
Add one or more instance types and node counts. Each row is a single-AZ worker pool for a region.
- Basic mode: Flat instance rows plus a cluster count. The HCP cluster fee scales with that count.
- Expert mode: Named clusters, each with machine pools (instance type, AZ, count). The HCP cluster fee is one fee per cluster. Basic and Expert keep separate sizing data.
- Remembered locally: This browser stores your last mode, Basic rows, Expert clusters, Step 2 discounts, and which steps are expanded or collapsed. Use Reset saved data to clear that and restore defaults. Share links still override on open.
- Region and filters (Basic): Choose region, architecture, category, and family to narrow the instance list, then Add a type.
- Count: Exact worker node count for that pool. Changes apply automatically.
Step 2 - Discounting (optional)
- Approx EC2 Savings Plan discount: Planning discount applied only to EC2 cost, not ROSA fees.
- Private Offer - Red Hat: PAYGO, 1-year (33% off), or 3-year (55% off) for the Worker Node Fee Per 4 vCPU.
- Additional programs: Reference list of AWS and Red Hat incentives. These do not change the math.
Step 3 - Results
The first time you expand Results or Platform Comparison and TCO, accept the non-binding estimate disclaimer (remembered in a cookie).
- Summary table: Per-pool EC2, Node Fee, and totals, plus HCP cluster fee.
- Private Offer comparison: PAYGO / 1-year / 3-year scenario totals with the selected tier highlighted and cost differences for the others.
- Summary price unit: Switch hourly, monthly (730 hours), or yearly.
- Export / Import CSV: Save or reload sizing, discounts, and a summary snapshot.
- Share: Copy a link or code so someone else can reload the same scenario.
- Open in Fleet Optimizer: Projects this scenario into fleet-level vCPU totals for broader optimization modeling.
Step 4 - Platform Comparison and TCO
Compare ROSA HCP and EKS Auto Mode as two AWS first-party options with different focus: turnkey OpenShift application platform vs managed Kubernetes container scheduler. Same Step 1 worker mix; Step 2 EC2 discounts are ignored in this view. Expanding this step uses the same non-binding estimate disclaimer as Results.
- 1-year base compare: Same workers, ROSA Worker Node Fee at 1-year Private Offer (33% off PAYGO), HCP cluster fee and EC2 at list, EKS $0.10/hr control plane, ~12% Auto Mode fee, and AWS Business Support at 10%. Locked to yearly amounts. Platform ops labor is reserved for the 3-year TCO.
- Capabilities: Compact ✓ / ✗ / ? matrix including GitOps, Observability, Service Mesh, Dev Spaces, Image builds, Production support, Hardened base images, Developer console, Cluster IdP / SSO, and Stateful apps / long batch.
- Version support: Separate lifecycle table. ROSA includes EUS Term 1 (~24 months on even OpenShift minors). EKS standard is 14 months at $0.10/hr; staying longer may add extended support at $0.60/hr (potential extra cost, not toggled in the base table).
- 3-year TCO: 36-month total with ROSA Worker Node Fee at 3-year Private Offer (55% off PAYGO). EKS control plane blends 14 months standard + 12 months extended + 10 months standard after upgrade. Includes a conservative EKS common platform-components line (monitoring/logging/GitOps) and platform ops labor stepped by cluster count.
What the fees mean
- EC2 cost: On-demand worker node pricing from the snapshot, after any EC2 discount.
- Node Fee: ROSA Worker Node Fee Per 4 vCPU (PAYGO $1,500/year per block, with Private Offer discounts).
- HCP cluster fee: $0.25/hour ($182.50/month) per cluster.
Before viewing results
These pricing results are non-binding estimates for planning only. They are not a quote, commercial offer, contractual commitment, or billing guarantee from Red Hat or its affiliates.
Actual charges may vary based on provider pricing changes, account configuration, discounts, taxes, region and availability zone specifics, and runtime usage patterns. Validate final pricing through official commercial channels before procurement or budgeting decisions.
