Getting started with ROSA GovCloud
Setting up clusters and accounts with GovCloud
Abstract
Chapter 1. Getting started with Red Hat OpenShift Service on AWS classic architecture in AWS GovCloud Copy linkLink copied to clipboard!
This service is for use by federal and government agencies, or by commercial organizations and Federal Information Security Modernization Act (FISMA) R&D Universities supporting a government contract or in the process of bidding on a government contract such as a request for proposal (RFP) or request for information (RFI) pre-bid stage.
Red Hat OpenShift Service on AWS classic architecture in AWS GovCloud, carries the following requirements:
- Red Hat OpenShift Service on AWS classic architecture FedRAMP can only be deployed into an existing VPC. See Create Amazon VPC architecture for the AWS PrivateLink use case for instructions on setting up a VPC.
- Red Hat OpenShift Service on AWS classic architecture in AWS GovCloud only supports the use of the AWS STS credentials method.
- Red Hat OpenShift Service on AWS classic architecture in AWS GovCloud only uses Federal Information Processing Standards (FIPS) validated modules in process cryptographic libraries.
Red Hat OpenShift Service on AWS classic architecture in AWS GovCloud requires a separate Red Hat account for use with FedRAMP, even if you already have an existing Red Hat account for Red Hat OpenShift Service on AWS classic architecture clusters in commercial regions.
- Each person who needs to be able to create, modify, or delete clusters must have their own Red Hat FedRAMP account.
- Access to an existing cluster, to use that cluster, does not require a Red Hat FedRAMP account.
- You can use your Red Hat FedRAMP account to deploy to multiple AWS GovCloud accounts.
1.1. Signing up for a Red Hat FedRAMP account Copy linkLink copied to clipboard!
To access Red Hat OpenShift Service on AWS classic architecture in AWS GovCloud, you must sign up for a Red Hat FedRAMP account.
Procedure
- Navigate to https://console.redhat.com/openshift/create/rosa/govcloud.
- Complete the access request form.
Click Submit to sign up.
You will receive a Submission confirmation.
Red Hat’s confirmed stateside support team will contact you through email for the following information:
- Admin details to include your organization name, administrator first and last name and administrator email.
User authentication option to the FedRAMP Hybrid Cloud Console from one of the following two options:
Local group in a Red Hat managed Keycloak instance, where users will be required to setup multi-factor authentication (MFA) with an approved device.
NoteOnly device YubiKEY 5C NFC FIPS currently accepted.
Customer managed Identity Provider (IdP), integrated via OpenID Connect (OIDC), where you will need to provide the following:
- Discovery Endpoint: The IdP’s OIDC discovery URL (typically ending in /.well-known/openid-configuration). This allows Keycloak to automatically fetch most of the IdP’s settings.
- Client ID and secret: Credentials that allow Keycloak to authenticate with the customer’s IdP.
- Email domain(s): A list of approved email domains. Only users with an email address from one of these domains will be allowed to log in.
Essential claim: A specific key-value pair (e.g., "rh-approved": "true") that must be present in a user’s token from the IdP to grant them access.
In this configuration, the customer takes on the responsibility for implementing FIPS 140-2 validated MFA.
Chapter 2. Managing your Red Hat OpenShift Service on AWS classic architecture AWS GovCloud account Copy linkLink copied to clipboard!
Once you have access to the FedRAMP accounts, you can manage the credentials as needed.
2.1. Changing your Red Hat FedRAMP account password Copy linkLink copied to clipboard!
To change your FedRAMP account password, you must have access to your Red Hat FedRAMP account.
Procedure
- Navigate to https://sso.openshiftusgov.com/realms/redhat-external/account.
- Sign in with your current username and password.
- Under the middle box called Account Security, click Signing In.
- Under Basic Authentication select Password.
Click Update and choose a password that meets the following requirements:
- minimum of fifteen (15) characters
- at least one (1) upper-case letter
- at least one (1) lower-case letter
- at least one (1) number
- at least one (1) special character (e.g. ~ ! @ # $ % ^ & * ( ) _ + = - ‘ [ ] / ? > <)
- Confirm your password.
- Click Submit.
2.2. Opening a support ticket Copy linkLink copied to clipboard!
To get access to open a support ticket please complete the following.
Procedure
- If you need to create an account, please contact fedramp-css@openshiftusgov.com.
- Once access is granted, navigate to https://redhatgov.servicenowservices.com/css.
- Click Create Case and complete the required information.
- Click Submit.
Chapter 3. Installing a Red Hat OpenShift Service on AWS classic architecture cluster in AWS GovCloud Copy linkLink copied to clipboard!
To install a Red Hat OpenShift Service on AWS classic architecture cluster in AWS GovCloud you must:
- Meet the requirements to access AWS GovCloud.
Complete the steps in Getting started with Red Hat OpenShift Service on AWS classic architecture in AWS GovCloud:
- Preparing to access Red Hat OpenShift Service on AWS classic architecture in AWS GovCloud.
- Signing up for a Red Hat FedRAMP account following.
3.1. Preparing to deploy a Red Hat OpenShift Service on AWS classic architecture cluster in AWS GovCloud Copy linkLink copied to clipboard!
To deploy a Red Hat OpenShift Service on AWS classic architecture cluster in AWS GovCloud, you must be logged in to your Red Hat FedRAMP account.
Prerequisites
- You have configured your AWS CLI to use GovCloud.
- You are logged into your government region.
Procedure
- Navigate to https://console.openshiftusgov.com/openshift/token.
- Sign in with your Red Hat FedRAMP account credentials where you will see a screen with your token.
- Copy your token for the next step.
In your terminal:
Run
rosa loginand paste your copied token in order to log into the service.rosa login --govcloud --token=<TOKEN>
$ rosa login --govcloud --token=<TOKEN>Copy to Clipboard Copied! Toggle word wrap Toggle overflow NoteDepending on your AWS CLI configuration, you may need to add a government region to the end of the command string like
--region us-gov-west-1.Run
rosa whoamito confirm all information is correct ensuring that you are using the AWS Gov region and the OCM API is “https://api.openshiftusgov.com”..rosa whoami
$ rosa whoamiCopy to Clipboard Copied! Toggle word wrap Toggle overflow Example output
Copy to Clipboard Copied! Toggle word wrap Toggle overflow
- You must create a VPC where Red Hat OpenShift Service on AWS classic architecture will be deployed. For instructions on setting up a VPC, see Amazon VPC architecture for the AWS PrivateLink use case.
3.2. Creating an AWS PrivateLink cluster Copy linkLink copied to clipboard!
You can create an AWS PrivateLink cluster using the ROSA command-line interface (CLI) (rosa).
AWS PrivateLink is supported on existing VPCs only.
Prerequisites
- You have available AWS service quotas.
- You have enabled the Red Hat OpenShift Service on AWS classic architecture service in the AWS Console.
- You have installed and configured the latest ROSA CLI, on your installation host.
- For GovCloud, you have enabled the Red Hat OpenShift Service on AWS classic architecture service in the AWS Console on the linked commercial account because it is inside the commercial account that you enable Red Hat OpenShift Service on AWS classic architecture for GovCloud. For more information, see Enable ROSA and configure AWS prerequisites.
- For Private Marketplace, you have enabled the Red Hat OpenShift Service on AWS classic architecture service in the AWS Console. For more information, see AWS Marketplace listings for ROSA.
Procedure
Creating a cluster can take up to 40 minutes.
With AWS PrivateLink, you can create a cluster with a single availability zone (Single-AZ) or multiple availability zones (Multi-AZ). In either case, your machine’s classless inter-domain routing (CIDR) must match your virtual private cloud’s CIDR. See Requirements for using your own VPC and VPC validation for more information.
ImportantIf you use a firewall, you must configure it so that Red Hat OpenShift Service on AWS classic architecture can access the sites that it requires to function.
For more information, see the AWS PrivateLink firewall prerequisites section.
NoteIf your cluster name is longer than 15 characters, it will contain an autogenerated domain prefix as a sub-domain for your provisioned cluster on
*.openshiftapps.com.To customize the subdomain, use the
--domain-prefixflag. The domain prefix cannot be longer than 15 characters, must be unique, and cannot be changed after cluster creation.To create a Single-AZ cluster:
rosa create cluster --private-link --cluster-name=<cluster-name> [--machine-cidr=<VPC CIDR>/16] --subnet-ids=<private-subnet-id>
$ rosa create cluster --private-link --cluster-name=<cluster-name> [--machine-cidr=<VPC CIDR>/16] --subnet-ids=<private-subnet-id>Copy to Clipboard Copied! Toggle word wrap Toggle overflow To create a Multi-AZ cluster:
rosa create cluster --private-link --multi-az --cluster-name=<cluster-name> [--machine-cidr=<VPC CIDR>/16] --subnet-ids=<private-subnet-id1>,<private-subnet-id2>,<private-subnet-id3>
$ rosa create cluster --private-link --multi-az --cluster-name=<cluster-name> [--machine-cidr=<VPC CIDR>/16] --subnet-ids=<private-subnet-id1>,<private-subnet-id2>,<private-subnet-id3>Copy to Clipboard Copied! Toggle word wrap Toggle overflow
Enter the following command to check the status of your cluster. During cluster creation, the
Statefield from the output will transition frompendingtoinstalling, and finally toready.rosa describe cluster --cluster=<cluster_name>
$ rosa describe cluster --cluster=<cluster_name>Copy to Clipboard Copied! Toggle word wrap Toggle overflow NoteIf installation fails or the
Statefield does not change toreadyafter 40 minutes, check the installation troubleshooting documentation for more details.Enter the following command to follow the OpenShift installer logs to track the progress of your cluster:
rosa logs install --cluster=<cluster_name> --watch
$ rosa logs install --cluster=<cluster_name> --watchCopy to Clipboard Copied! Toggle word wrap Toggle overflow
Legal Notice
Copy linkLink copied to clipboard!
Copyright © 2025 Red Hat
OpenShift documentation is licensed under the Apache License 2.0 (https://www.apache.org/licenses/LICENSE-2.0).
Modified versions must remove all Red Hat trademarks.
Portions adapted from https://github.com/kubernetes-incubator/service-catalog/ with modifications by Red Hat.
Red Hat, Red Hat Enterprise Linux, the Red Hat logo, the Shadowman logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries.
Linux® is the registered trademark of Linus Torvalds in the United States and other countries.
Java® is a registered trademark of Oracle and/or its affiliates.
XFS® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries.
MySQL® is a registered trademark of MySQL AB in the United States, the European Union and other countries.
Node.js® is an official trademark of Joyent. Red Hat Software Collections is not formally related to or endorsed by the official Joyent Node.js open source or commercial project.
The OpenStack® Word Mark and OpenStack logo are either registered trademarks/service marks or trademarks/service marks of the OpenStack Foundation, in the United States and other countries and are used with the OpenStack Foundation’s permission. We are not affiliated with, endorsed or sponsored by the OpenStack Foundation, or the OpenStack community.
All other trademarks are the property of their respective owners.