{
  "id": "red-hat-openshift-service-on-aws-vs-amazon-eks",
  "ids": [
    "red-hat-openshift-service-on-aws",
    "amazon-eks"
  ],
  "title": "Red Hat OpenShift Service on AWS vs Amazon EKS: Kubernetes integration and operating responsibilities",
  "heading": "Red Hat OpenShift Service on AWS vs Amazon EKS",
  "kicker": "Software architecture comparison",
  "deck": "ROSA is a managed OpenShift platform on AWS; EKS is a managed Kubernetes service. Choose based on whether the team needs OpenShift's platform and operating model, rather than treating both names as identical Kubernetes hosting packages.",
  "description": "Compare Red Hat OpenShift Service on AWS vs Amazon EKS for Kubernetes integration and operating responsibilities.",
  "answerHeading": "Which option fits the requirement?",
  "answer": "ROSA is a managed OpenShift platform on AWS; EKS is a managed Kubernetes service. Choose based on whether the team needs OpenShift's platform and operating model, rather than treating both names as identical Kubernetes hosting packages.",
  "checkedAt": "2026-10-25",
  "researchTag": "Deployment, compatibility and cost scope",
  "researchLimit": "Official product material reviewed. Acceptance checks are proposed exercises, not completed product trials, performance measurements or reliability guarantees.",
  "datasetDescription": "Seven technical differences and four proposed acceptance checks for Red Hat OpenShift Service on AWS vs Amazon EKS.",
  "type": "workflow-buying",
  "sharedBuyingNeed": "Evaluate alternative approaches to Kubernetes integration and operating responsibilities.",
  "rows": [
    [
      "Cloud provider",
      "AWS and Red Hat",
      "AWS"
    ],
    [
      "Platform",
      "Managed OpenShift",
      "Managed Kubernetes"
    ],
    [
      "Deployment object",
      "ROSA OpenShift clusters",
      "EKS clusters and chosen compute arrangement"
    ],
    [
      "Image ecosystem",
      "OpenShift image workflows and registries",
      "Amazon ECR integration"
    ],
    [
      "Identity context",
      "OpenShift and AWS identity configuration",
      "AWS IAM integration"
    ],
    [
      "Network context",
      "OpenShift networking in AWS",
      "EKS and AWS VPC networking"
    ],
    [
      "Cost components",
      "Selected OpenShift subscription and cloud resource scope",
      "Cluster configuration, compute, storage and networking"
    ]
  ],
  "scenarios": [
    {
      "name": "Application manifests",
      "question": "Can the team deploy the representative application and its dependencies?",
      "left": "With Red Hat OpenShift Service on AWS, deploy the representative application and its dependencies.",
      "right": "With Amazon EKS, deploy the representative application and its dependencies.",
      "note": "The workload becomes ready and all mandatory integrations work."
    },
    {
      "name": "Persistent data",
      "question": "Can the team restart a stateful test workload using its volume configuration?",
      "left": "With Red Hat OpenShift Service on AWS, restart a stateful test workload using its volume configuration.",
      "right": "With Amazon EKS, restart a stateful test workload using its volume configuration.",
      "note": "The workload recovers the expected data."
    },
    {
      "name": "Workload identity",
      "question": "Can the team access one cloud service through the intended workload identity?",
      "left": "With Red Hat OpenShift Service on AWS, access one cloud service through the intended workload identity.",
      "right": "With Amazon EKS, access one cloud service through the intended workload identity.",
      "note": "Only the required permissions are granted."
    },
    {
      "name": "Upgrade exercise",
      "question": "Can the team rehearse a supported non-production upgrade?",
      "left": "With Red Hat OpenShift Service on AWS, rehearse a supported non-production upgrade.",
      "right": "With Amazon EKS, rehearse a supported non-production upgrade.",
      "note": "Downtime, rollback and remaining operating tasks are documented."
    }
  ],
  "exampleTable": {
    "caption": "Proposed checks using authorised non-production resources. Record the actual account, region, version, configuration and observed outcome.",
    "headers": [
      "Requirement",
      "Proposed exercise",
      "Accept when"
    ],
    "rows": [
      [
        "Application manifests",
        "Deploy the representative application and its dependencies.",
        "The workload becomes ready and all mandatory integrations work."
      ],
      [
        "Persistent data",
        "Restart a stateful test workload using its volume configuration.",
        "The workload recovers the expected data."
      ],
      [
        "Workload identity",
        "Access one cloud service through the intended workload identity.",
        "Only the required permissions are granted."
      ],
      [
        "Upgrade exercise",
        "Rehearse a supported non-production upgrade.",
        "Downtime, rollback and remaining operating tasks are documented."
      ]
    ]
  },
  "sections": [
    {
      "id": "scope-and-architecture",
      "title": "Scope and architecture",
      "paragraphs": [
        "ROSA is a managed OpenShift platform on AWS; EKS is a managed Kubernetes service. Choose based on whether the team needs OpenShift's platform and operating model, rather than treating both names as identical Kubernetes hosting packages.",
        "A common Kubernetes API does not make cloud storage, ingress, workload identity and network policy configuration automatically portable. OpenShift also adds its own platform conventions and administration model."
      ],
      "links": [
        {
          "url": "https://docs.aws.amazon.com/rosa/",
          "label": "Red Hat OpenShift Service on AWS product information"
        },
        {
          "url": "https://aws.amazon.com/eks/",
          "label": "Amazon EKS product information"
        }
      ],
      "navLabel": "Architecture"
    },
    {
      "id": "cost-and-migration",
      "title": "Cost and migration planning",
      "paragraphs": [
        "For Red Hat OpenShift Service on AWS, include selected OpenShift subscription and cloud resource scope. For Amazon EKS, include cluster configuration, compute, storage and networking. Use the same workload and resilience assumptions, then confirm current vendor terms for the selected configuration.",
        "Deploy the actual manifests, images, secrets, ingress and persistent volumes in a non-production environment. Document remaining node, upgrade, security-policy and capacity responsibilities for the exact selected operating mode."
      ],
      "navLabel": "Costs & migration"
    }
  ],
  "faqs": [
    {
      "question": "How should we choose between Red Hat OpenShift Service on AWS and Amazon EKS?",
      "answer": "ROSA is a managed OpenShift platform on AWS; EKS is a managed Kubernetes service. Choose based on whether the team needs OpenShift's platform and operating model, rather than treating both names as identical Kubernetes hosting packages."
    },
    {
      "question": "Which costs belong in the comparison?",
      "answer": "For Red Hat OpenShift Service on AWS, include selected OpenShift subscription and cloud resource scope. For Amazon EKS, include cluster configuration, compute, storage and networking. Use the same workload and resilience assumptions, then confirm current vendor terms for the selected configuration."
    },
    {
      "question": "What should we validate before a production move?",
      "answer": "Deploy the actual manifests, images, secrets, ingress and persistent volumes in a non-production environment. Document remaining node, upgrade, security-policy and capacity responsibilities for the exact selected operating mode."
    }
  ],
  "sources": [
    {
      "url": "https://docs.aws.amazon.com/rosa/",
      "facts": "Official product scope, deployment and integration context used for Kubernetes integration and operating responsibilities."
    },
    {
      "url": "https://aws.amazon.com/eks/",
      "facts": "Official product scope, deployment and integration context used for Kubernetes integration and operating responsibilities."
    }
  ],
  "relatedLinks": [
    {
      "path": "/categories/container-management/",
      "title": "Container Management software"
    },
    {
      "path": "/categories/cloud-devops/",
      "title": "Cloud Devops software"
    },
    {
      "path": "/guides/cloud-cost-checklist/",
      "title": "Cloud workload and cost checklist"
    }
  ]
}