Repair a deploy signal that cannot read CloudWatch

Read the setup action on the environment’s Deploy verification row when a CloudWatch signal is unread. It identifies whether the account connection or the installed read role needs a change.

If no connected AWS connection can read a signal's account, the check records No AWS connection can read CloudWatch, and the Inbox and the environment's Deploy verification row offer the step that repairs it. Check AWS connection opens a linked connection that is not connected. A signal reads only through the connection it was saved with, so when that connection was removed or no longer links the account, and another connected, linked connection covers the signal's account and region, the step is Edit signals. Open the signal, select Edit signal, choose its AWS account and region again from the entry that does not read connection unavailable, and save it with that connection. Open AWS accounts opens Setup → AWS accounts when no linked connection covers the signal's account and region. The step disappears once each signal is saved with a connected connection linked in its account and region; the next check that reads the signal shows the repair worked.

If AWS refuses a saved signal's metric read because the connection's role does not grant it, the check records the refusal, and the Inbox and the environment's Deploy verification row offer Update the AWS role, which opens the connection. When the connection leaves the metric read out of its read choices, the step is Choose what Proofline reads instead, and it opens those choices; choose the read, then update the installed role. Proofline grants nothing itself. The step stays until the next check reads the signal without a refusal: updating the role does not remove it.

Search help

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