Event Correlation
Alarms, deploys, security findings and CloudTrail events on one timeline for incident reviews.
What this pane shows
A unified timeline merging signals from CloudWatch alarms, recent deploys, Security Hub / GuardDuty findings and CloudTrail mutating events. Each row carries its source, time, severity and a short title; clicking a row jumps to the originating pane for the full context.
Key use cases
- Post-incident review: reconstruct exactly what happened and in what order.
- Mid-incident: find the change that preceded the failure.
- Train new on-call engineers on how signals correlate during real incidents.
- Produce a clean timeline for a post-mortem document.
How often it refreshes
Cached data is served within the window your plan guarantees. Faster refresh is one of the things a higher plan buys.
| Explorer | Builder | Team |
|---|---|---|
| 2 min | 1 min | 30 sec |
Linking to LightPane
Once you connect one or more cloud accounts in LightPane you can create
access keys, which are what allow panes to read those
accounts. A key is a text string: the prefix lp_ak_ followed
by 43 characters drawn from A–Z a–z 0–9 - _
(URL-safe base64 of 32 random bytes), so 49 characters in all.
Each cloud account you connect is also given an account
handle — a short name such as zesty-ridge, minted
by LightPane when you link the account and never changed afterwards. It
lets a pane reference the same account for good, without putting a cloud
account ID in your page. Use the handle, not the account's editable
alias: renaming an alias makes a pane match nothing, and that failure is
silent — the pane shows an ordinary empty state, not an error.
More on naming accounts.
When adding the code below into your web page, replace
lp_ak_YOUR_ACCESS_KEY and YOUR_ACCOUNT_HANDLE
with your own access key and account handle.
- No key? Paste this exactly as it is. With the placeholder still in, the pane renders clearly-marked mock data, so you can place and style it before you connect anything. (A key that is present but rejected shows an error instead — a live dashboard must never quietly fall back to sample numbers.)
- No handle? The pane falls back to the access key's default account. That works, but the default moves if the key's grants change — naming a handle is what guarantees the same account every time.