Features Pricing Build Docs Demos About Register or sign in
AWS

Cost by Tag

AWS spend grouped by a tag (Environment, Team, Application) — what each slice of the account costs.

Category Cost
Scope Global
Mock data. This preview shows how the pane renders when embedded in a page. Add an access key linked to your cloud account to see that account's data.

What this pane shows

Monthly spend split by the values of a tag key, so an Environment tag would yield Production / Staging / Development totals; a Team tag would yield per-team costs. Includes untagged resources called out separately so coverage gaps are visible. Driven by AWS Cost Explorer's group-by-tag query.

Key use cases

  • Show-back: bill departments or teams for their share of the cloud bill.
  • Find the cost of running staging or development environments.
  • Quantify how much spend is on untagged resources (typically what governance work needs to tackle).
  • Compare cost per environment month-over-month.

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.

ExplorerBuilderTeam
24 hours8 hours6 hours

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.

How to embed

Have an account? Use this pane in the console → — it fills in your access key, account handle and region, and builds the finished snippet for you.

Embedding within a web page

lp.js is the only script you add. It loads the LightPane runtime and, for each pane container on the page, fetches that pane's own code for you — so the first block never changes however many panes you add.

1

Once per page, in <head>

<script>window.lpEmbed = { accessKey: "lp_ak_YOUR_ACCESS_KEY" };</script>
<script src="https://lightpane.cloud/embed/lp.js"></script>
2

One container, where the pane should appear

<div class="lp-cost-by-tag-panel"
     data-lp-pane="aws/cost-by-tag"
     data-lp-account="YOUR_ACCOUNT_HANDLE"></div>

data-lp-pane is how lp.js knows what to load — without it the pane will not appear. The class is the mount point the pane's own code looks for, so keep both. This pane composes its own sections, so it takes no column options; data-lp-attributes applies to service inventory panes.

Embedding in an iframe

For somewhere you cannot add scripts — Confluence, Notion, a wiki, a SharePoint page — or anywhere a self-contained window suits better than a pane woven into the parent page.

<iframe src="https://lightpane.cloud/embed/v1/?p=cost-by-tag&provider=aws&account=YOUR_ACCOUNT_HANDLE#k=lp_ak_YOUR_ACCESS_KEY"
        title="Cost by Tag"
        style="width:100%;height:460px;border:0"></iframe>

The key sits after the #, so it stays in the browser and is never sent to our servers as part of the URL.

Same idea on another cloud