Red Hat Training

A Red Hat training course is available for Red Hat Certified Cloud and Service Provider Certification

Chapter 1. Introduction to Red Hat Certified Cloud and Service Provider Certification policies

1.1. Audience

Use this guide to understand the technical and operational certification requirements as implemented for CCSP partners who want to offer Infrastructure-as-a-Service (IaaS), Platform-as-a-Service (PaaS), or a managed service based on Red Hat Enterprise Linux. The certification tools and methodologies cater to cloud application images built on Red Hat Enterprise Linux.

1.2. Create value for our joint customers

As a Certified Cloud and Service Provider (CCSP), you are required to certify images that you publish in a catalog. The certification process includes a series of tests that provide your Red Hat customers assurance that they will have a consistent experience across cloud providers, that the customer’s experience comes with the highest level of support, and that good security practices are available to the customers.

The cloud certification test suite (redhat-certification-cloud) includes three tests (supportable, configuration, security), each with a series of subtests and checks, which are explained below. Logs from a singular run with all three of the cloud tests and the test suite self check test (rhcert/selfcheck) must be submitted to Red Hat for new certifications and for recertifications.

Most of the cloud certification subtests provide an immediate return status (Pass/Fail); however, some subtests may require detailed review by Red Hat to confirm success. Such tests are marked with REVIEW status in the Red Hat Certification application.

Some tests may also identify a potential issue and return a WARN status. This status indicates that best practices have not been followed. Tests marked with the WARN status warrant attention or actions but do not prevent a certification from succeeding. Partners are recommended to review the output of such tests and perform appropriate actions based on the information contained within the warnings.

Additional resources

1.3. Test Suite versions

You must install the latest version of the certification tooling and use the latest workflow for the certification process. After a new version of the certification tooling is released, Red Hat supports the previous tooling and workflow for a period of 90 days post the release.

At the end of the 90 days period, test logs/results generated using the previous version(s) are automatically rejected and you are expected to regenerate the test logs/results using the latest tooling and workflow.

The latest version of the certification tooling and workflow is available (by default) via Red Hat Subscription Management and documented in the CCSP Certification Workflow Guide.

1.4. Supported RHEL version and architecture

The certifications are supported on the following RHEL version and architecture.

RHEL versionArchitecture


  • 64-bit AMD and Intel
  • 64-bit IBM Z
  • 64-bit ARM
  • Little endian IBM Power systems


  • 64-bit AMD and Intel
  • 64-bit IBM Z
  • 64-bit ARM
  • Little endian IBM Power systems


  • 64-bit AMD and Intel
  • Little endian IBM Power systems

For information about hypervisor support, see Certified Guest Operating Systems in Red Hat OpenStack Platform, Red Hat Virtualization and OpenShift Virtualization.

1.5. Understand Passthrough Certifications

A passthrough certification is used when the same image is provided as a copy of an existing certified cloud certification and is listed under a different image name.

You can create a passthrough regular or gold RHEL image from an originally certified regular or gold RHEL image.

The policy for submitting a passthrough image certification request requires you to:

  • Ensure that the image is a duplicate of the original certified image except for the name which might be different.
  • As with the original image certification, it is expected that a given running image does include a certain drift from the original static on-disk image file in the form of instance-type dependent configuration data.