mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-05 12:46:18 +01:00
15 lines
1.3 KiB
Plaintext
15 lines
1.3 KiB
Plaintext
// Module included in the following assemblies:
|
||
//
|
||
// * osd_planning/aws-ccs.adoc
|
||
|
||
:_mod-docs-content-type: CONCEPT
|
||
[id="ccs-aws-understand_{context}"]
|
||
= Understanding Customer Cloud Subscriptions on AWS
|
||
|
||
[role="_abstract"]
|
||
To deploy {product-title} into your existing Amazon Web Services (AWS) account using the Customer Cloud Subscription (CCS) model, Red Hat requires several prerequisites be met.
|
||
|
||
Red Hat recommends the usage of an AWS Organization to manage multiple AWS accounts. The AWS Organization, managed by the customer, hosts multiple AWS accounts. There is a root account in the organization that all accounts will refer to in the account hierarchy.
|
||
|
||
It is recommended for the {product-title} cluster using a CCS model to be hosted in an AWS account within an AWS Organizational Unit. A service control policy (SCP) is created and applied to the AWS Organizational Unit that manages what services the AWS sub-accounts are permitted to access. The SCP applies only to available permissions within a single AWS account for all AWS sub-accounts within the Organizational Unit. It is also possible to apply a SCP to a single AWS account. All other accounts in the customer’s AWS Organization are managed in whatever manner the customer requires. Red Hat Site Reliability Engineers (SRE) will not have any control over SCPs within the AWS Organization.
|