此内容没有您所选择的语言版本。

Chapter 1. Getting started with Red Hat OpenShift Service on AWS in AWS GovCloud


This service is for use by federal and government agencies, or by commercial organizations and Federal Information Security Modernization Act (FISMA) research and development 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 in AWS GovCloud carries the following requirements:

  • Red Hat OpenShift Service on AWS in AWS GovCloud 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 in AWS GovCloud only supports the use of the AWS STS credentials method.
  • Red Hat OpenShift Service on AWS in AWS GovCloud only uses Federal Information Processing Standards (FIPS) validated modules in process cryptographic libraries.
  • Red Hat OpenShift Service on AWS 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 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

To access Red Hat OpenShift Service on AWS in AWS GovCloud, you must sign up for a Red Hat FedRAMP account.

Procedure

  1. Navigate to the ROSA GovCloud access request form.
  2. Complete the access request form.
  3. Click Submit to sign up. You receive a Submission confirmation.

    Red Hat’s confirmed stateside support team contacts you through email for the following information:

    • Admin details to include your organization name, administrator first and surname 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 multifactor authentication (MFA) with an approved device.

        Note

        Only 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.
Red Hat logoGithubredditYoutubeTwitter

学习

尝试、购买和销售

社区

关于红帽文档

通过我们的产品和服务,以及可以信赖的内容,帮助红帽用户创新并实现他们的目标。 了解我们当前的更新.

让开源更具包容性

红帽致力于替换我们的代码、文档和 Web 属性中存在问题的语言。欲了解更多详情,请参阅红帽博客.

關於紅帽

我们提供强化的解决方案,使企业能够更轻松地跨平台和环境(从核心数据中心到网络边缘)工作。

Theme

© 2026 Red Hat
返回顶部