Account Security Settings
Key security settings to review on every AWS account — identity, network exposure, encryption, logging and storage — checked by LightPane on the account's discovered configuration (not AWS Security Hub findings).
What this pane shows
The key security settings to review on every AWS account. LightPane runs 15 checks on the account's discovered configuration, across Identity & Access (access-key age, MFA, password length), Network Exposure (SSH, RDP and database ports open to the internet, public RDS instances), Encryption (S3 default encryption, EBS and RDS encryption), Logging (CloudTrail) and Storage (S3 public access). Where a check mirrors an AWS Security Hub control, the control is named (for example IAM.3 or EC2.13). Each failing check lists the affected resources and how to fix them; checks that need data the account does not provide are shown as not assessed, never as passing.
These are LightPane's own checks, not AWS Security Hub findings, so the pane works whether or not Security Hub is enabled.
Key use cases
- Review the same baseline on every account, new or existing.
- Prioritise security work by severity and by the number of affected resources.
- Confirm a fix: the failing check clears on the next refresh.
- Pre-flight a new account or workload against the settings used in production.
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.