edit

Author: bmcelvee

modules/rosa-roles-and-policies.adoc

@@ -6,10 +6,10 @@
 [id="rosa-roles-and-policies_{context}"]
 = AWS managed policies and roles
 
-[id="aws-managed-policies"]
+ifdef::openshift-rosa-hcp[]
+[id="aws-managed-policies-hcp"]
 == AWS managed policies
 
-ifdef::openshift-rosa-hcp[]
 .AWS managed account policies
 [options="header",cols="2*"]
 |===
@@ -34,12 +34,6 @@ ifdef::openshift-rosa-hcp[]
 You must attach Operator policies to an Operator IAM role to allow a ROSA cluster to make calls to other AWS services.
 ====
 
-[id="account-wide-roles"]
-== Account-wide roles
-* `<prefix>-HCP-ROSA-Worker-Role`
-* `<prefix>-HCP-ROSA-Support-Role`
-* `<prefix>-HCP-ROSA-Installer-Role`
-
 .AWS managed Operator policies
 [options="header",cols="2*"]
 |===
@@ -72,7 +66,13 @@ You must attach Operator policies to an Operator IAM role to allow a ROSA cluste
 
 |===
 
-[id="operator-roles"]
+[id="account-wide-roles-hcp"]
+== Account-wide roles
+* `<prefix>-HCP-ROSA-Worker-Role`
+* `<prefix>-HCP-ROSA-Support-Role`
+* `<prefix>-HCP-ROSA-Installer-Role`
+
+[id="operator-roles-hcp"]
 == Operator roles
 
 Certain policies are used by the cluster Operator roles, listed below. The Operator roles are created in a second step because they are dependent on an existing cluster name and cannot be created at the same time as the account-wide roles.
@@ -94,6 +94,8 @@ For the full `JSON` information for the AWS managed policies, see the link:https
 endif::openshift-rosa-hcp[]
 
 ifdef::openshift-rosa[]
+[id="aws-managed-policies"]
+== AWS managed policies
 
 .AWS managed account policies
 [options="header",cols="2*"]