Diagnose a failed AWS reader installation
If Proofline cannot assume the new role, inspect the installer’s result in the target account before changing the role’s trust policy.
Find the original failure and check again#
If installation fails, read the original CLI or deployment-tool error. For CloudFormation, select Return to AWS on the waiting screen and inspect the stack’s Events tab. If you used the CLI, open CloudFormation in the installation region and find the stack named in the script. A stack ID means AWS accepted the request, not that the role exists. Resolve an existing or rolled-back stack's reported error before retrying; the supplied script does not update or delete existing stacks.
An sts:AssumeRole refusal in Proofline does not identify the installer's failure. It can mean the role is missing or that its trust does not match. Check the role name, trusted principal, external ID, and permission policy against the supplied template. If Proofline stops checking, correct the setup and select Check again.