Public Exposure Audit
Every publicly-reachable resource — buckets, databases, EC2, ALBs — split into critical vs expected.
What this pane shows
A cross-service roll-up of every resource the internet can reach: publicly-accessible RDS, public S3 buckets, EC2 instances with public IPs, internet-facing ALBs and NLBs, CloudFront distributions, public Lambda function URLs and public API Gateways. Critical exposures (e.g. a public database) are surfaced first; expected exposures (web servers, public CDN) are grouped separately.
Key use cases
- Find a database, queue or storage resource that's accidentally public.
- Confirm intentional public-facing infrastructure has the expected configuration (WAF, OAC, etc.).
- Audit external attack surface during a security review.
- Catch a new service spinning up with the public-access default still on.
How often it refreshes
This pane refreshes every 30 min on every plan. Panes that draw on billing or recommendation APIs refresh on a per-plan schedule — see pricing.
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.