Access Analyzer
IAM Access Analyzer findings — resources accessible from outside the account's trust boundary.
What this pane shows
Every resource AWS IAM Access Analyzer has flagged as accessible from outside the trust boundary: public S3 buckets, cross-account IAM roles, KMS keys shared externally, Secrets Manager secrets, Lambda functions and others. Each finding shows the principal that has access, the actions allowed and the policy excerpt that grants it.
Key use cases
- Triage external-access findings during an account review.
- Validate that an intentional cross-account share has the expected scope.
- Catch an accidentally-public S3 bucket the moment Access Analyzer flags it.
- Audit which external accounts have access to which resources.
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 |
|---|---|---|
| 30 min | 15 min | 5 min |
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.