Confirm AWS inventory is current before enabling checks

Verify the AWS account connection, then check the Inventory section of the environment. A working reader role and a recent inventory collection answer different questions.

Inspect the collection behind the connection#

  1. If you did not check access beneath the files, return to the AWS connection and select Check connection, or I applied it while Proofline is checking.
  2. Confirm that the connection's Status tab shows connected access. Use Diagnostics for the last check and any error.
  3. Open the environment's Setup → AWS accounts page and select Add.
  4. Select the connected account, choose its region and resource scope, then select Link account.
  5. Open Overview and find the account under Inventory. Its line shows how many resource types were read, when it was last collected, and any collection gaps. Expand Collection details to see refreshes after a change and how many changes the change events caught.

Before continuing, confirm that inventory collection is current. An absent Inventory section, Waiting for the first collection, Collection is off, or an overdue collection means you cannot yet rely on the inventory. Use the repair action beside a collection gap and resolve the reported setup or collection problem. When AWS refused inventory reads that the environment uses, the gap's repair action, Open access request, opens the connection's Access request. It lists what the grant adds for each feature in use, with a policy and a command that keep every inventory read the role already answers and add the missing ones, and leaves out refused reads that nothing you use needs. Run the command, or for a role installed with CloudFormation or Terraform, select Open installation files beneath it, check Inventory regions and apply the files to the stack or Terraform root that created the role. For a role installed through a connection set's StackSet or Terraform file, run the command. Then select Check access again at the end of the Access request. Proofline does not ask AWS again for a read it refused in the last 24 hours until you do, so without the check the gap stays for up to a day. After the check, the gap leaves at the next collection. A gap that says the account's role leaves a read out by choice has no repair action: those resource types stay a gap, and scans and investigations run without them. That choice is made when the role is installed (Connect Amazon Web Services). A connected role alone does not establish usable inventory or complete infrastructure evidence.

Search help

Tab to a result. Enter to open. Escape to close.