Prepare an AWS identifier
01In brief #sec_ebe39e17
REVIEWIT collects an AWS organization through a dedicated IAM user, to whom you entrust the access key. This user reads the organization, IAM Identity Center, and IAM Access Analyzer; in each member account, it assumes a read-only role that you deploy via a StackSet. Everything is read-only: REVIEWIT never reads the value of a secret, a parameter, or the content of an object.
What you need to grant depends on the resources you want to collect. Two paths, the same result:
- the Prepare step of the login assistant renders the exact IAM policies for the resources you check, ready to paste into the IAM console;
- the CloudFormation templates below apply policies for the entire AWS catalog: one template for the user, one for the member role.
021. Choose the connection account #sec_c07a6242
REVIEWIT connects to an AWS organization: an isolated account is not supported. The IAM user resides in one of these two accounts:
- the delegated account (recommended) — your security or audit account. From the management account, delegate to it:
- AWS Organizations: Settings › Delegated Administrator for AWS Organizations, a delegation policy that authorizes it to read accounts, organizational units, policies, and their tags;
- IAM Identity Center: Settings › Delegated Administration;
- IAM Access Analyzer: Settings › Delegated Administrator, then create in this account an external access analyzer at the organization level; if you want unused access, an unused access analyzer; if you want the internal audience of your buckets, snapshots, and tables (Overshared policy), an internal access analyzer — the latter two are billed by AWS (section 5);
- the management account — simpler, without delegation, but access is usually limited there.
032. Create the IAM user #sec_2f19ce48
In the selected account, deploy a stack with the IAM user template for the connection (CloudFormation › Create stack, accepting the creation of IAM-named resources). It creates the REVIEWIT-Collector user and its policy: reading the organization, assuming the member role, and verifying its own permissions.
Then create its access key: IAM › Users › REVIEWIT-Collector › Security credentials › Create access key, use case "application running outside AWS". Note the Key ID (AKIA…) and the secret key, displayed only once.
The template does not create any key: an exposed key in the stack output would be readable in the CloudFormation console.
043. Deploy the member role #sec_4d4cee4f
From the management account (or a delegated StackSets administrator), create a StackSet with the member role template:
- service-managed permissions, auto-deployment enabled — an account joining the organization receives the role;
- targets: the root, or the organizational units that REVIEWIT governs; a single region is sufficient, the role is global;
- parameters: CollectorAccountId (the account from step 2), CollectorUserName (REVIEWIT-Collector), MemberRoleName (REVIEWIT-Read).
The role trusts only the IAM user of the connection. A service-managed StackSet does not deploy to the management account: if it must be governed, deploy the same template as a regular stack there.
054. Declare and verify #sec_f5476f51
Return to the assistant: step Identifier, enter the access key ID, the secret key, and the member role name; then Verify. There is no organization ID to enter: REVIEWIT discovers it.
REVIEWIT verifies that the key is valid, discovers the organization (o-…), reads the accounts, assumes the member role in a member account, then asks AWS, action by action, what the user and the role are allowed to do — policies, permission boundaries, and organization SCPs included. It displays the verdict for each resource; anything still missing returns you to the Prepare step.
The secret key is stored in REVIEWIT's vault, never in clear text. To renew it, create a new key in IAM, update the identifier in REVIEWIT, then deactivate the old one.
065. View the internal audience of your resources (Overshared policy) #sec_2f822289
For S3 buckets, RDS snapshots, and DynamoDB tables, REVIEWIT shows who, within your organization, can access the object: open access to the entire organization or to an organizational unit, and the roles, users, or internal accounts that have access, with their actions. This is the substance of the Overshared policy (audience too broad internally).
REVIEWIT does not infer anything from your policy text: it reads the internal access findings from IAM Access Analyzer. Therefore, you need an internal access analyzer:
- In the delegated Access Analyzer account (section 1), IAM Access Analyzer › Analyzers › Create analyzer, type Internal access analysis, trusted zone the organization;
- Choose the types of resources to analyze — at least S3 buckets, RDS snapshots, and DynamoDB tables — and, if you wish, the covered accounts or organizational units;
- Repeat in each region where these resources exist: an analyzer is regional.
This analyzer is billed by AWS per analyzed resource. Without an analyzer in a region, the two signals remain empty for objects in that region, and REVIEWIT shows them out of the policy scope: it never defaults to compliance. The necessary rights (access-analyzer:ListAnalyzers, ListFindingsV2, GetFindingV2) are already in the connection user's policy: nothing more to grant.
07What REVIEWIT never does #sec_08bd49b8
- It does not deploy anything or grant any rights: your administrator places the templates or policies.
- It does not read the value of a secret (secretsmanager:GetSecretValue), nor that of a parameter (ssm:GetParameter), nor the content of an object (s3:GetObject): none of these actions are requested.
- It does not require AWS Resource Explorer: if it is activated in your organization, REVIEWIT uses it to enumerate faster; otherwise, nothing changes.
08To go further #sec_2c34c00e
- Understand a collection connection
- Rights reference by resource
- Read a verdict