Skip to content
shadcn.io

shadcn.io is not affiliated with official shadcn/ui

AWS Grid Integration Block for React

An integration grid section for a cloud cost tool reading from AWS: eight service tiles you tick, and one stacked bar and coverage figure that follow every tick, counted from last month's typed spend.

Framework
UI library

Preview

Preview width

Installation

Part of Pro
Pro unlocks the code and one-line install of every Pro button and text effect, plus the MCP for your AI editor.
Have Pro already? Sign in to open it.Opens here as soon as you're Pro.

Overview

An integration grid section for React with Base UI, written for Meterfern, a fictional cloud cost reporting tool, and its AWS connection. A compact header ("Choose what each report covers") has the mark pair at its end. Under a band rule, a coverage figure ("82% of last month's $48,200 is in your reports") sits beside one stacked bar that draws every service's share of the spend: ticked services are solid, left-out ones are hatched, and the services the tool never lists are a plain segment, with a three-key legend in words. Below it, eight tiles on shared hairlines (EC2, RDS, S3, EKS, Lambda, DynamoDB, CloudFront and CloudWatch) are whole-card checkboxes showing each service's spend. Ticking changes the figure, the bar and a polite status line; the tiles, bar and figure are all derived from the same typed spend. A visible note says the figures are examples and that ticking changes the page only: nothing is read from AWS. The block ends on the tile grid, so no rule closes it. The page's rails and top rule come from the Guides spine. It's built from Guides, Checkbox and Field, with your theme's tokens for every colour. AWS is named in text only: no AWS logo, colour or wordmark ships with the block.

FAQ

How do I change the services and the spend?

Edit SERVICES at the top of the file: an id, a name and last month's spend in dollars. OTHER is everything on the bill that the tool never lists, and START is the ids ticked on load. The total, every tile, the percentage covered, the service count and each bar segment's width are worked out from those numbers, so adding a service needs nothing else. All figures are example data.

Does ticking a service connect or read anything?

No. A tick changes this page's own state and nothing else: nothing is read from AWS and nothing is saved or sent. The note under the figure says so from the first paint, in a polite status region, and a second visually hidden status announces the new coverage after each change ("Covers 91% of $48,200 with 7 of 8 services"). Wire toggle to your own settings call.

Is every tile keyboard and screen reader friendly?

Each tile is one label around a real checkbox, so a click anywhere on the card toggles it, Space toggles it from the keyboard, and the checkbox is named by the service ("EC2"). The tile shows a visible focus ring and a ticked tint that does not depend on the primary colour. The bar is hidden from assistive technology because the figure, the count and the status line carry the same numbers in text.

Why is a left-out service hatched?

So the state never depends on tone alone: a covered service is a solid segment, a left-out one is diagonal hatching, and the legend names both in words. The grey segment is the spend the tool never lists, which no tick can change.

How does it fit on a phone, in right-to-left layouts and with reduced motion?

On a phone the figure sits above the bar and the tiles run two across. The bar and its legend always run left to right, as a drawing of proportions should, while the header, tiles and text follow the page direction; money amounts are kept in reading order. The header fades up once on load and the bar segments change tone with a short transition; reduced motion turns both off.

  • Pro

    AWS Detail Integration

    Scopes and steps

    An integration detail section for a cloud cost tool connecting to AWS: a header with the mark pair and Connect AWS, a three-cell trust chain on one wire, and the five read-only IAM actions its role allows.

  • Pro

    An integration list section for a cloud cost tool reading from AWS: six cost-allocation tags as rows with a coverage bar, a state word and an Activate switch, a segmented filter with counts, and a working Retry on the one row that timed out.

  • Pro

    An integration setup flow for a cloud cost tool connecting to AWS: a scope and 12-digit account ID, two aws iam commands built from that ID with a derived External ID, and a pasted role ARN that is parsed and checked against the account.

  • Pro

    AWS Stats Integration

    Bars and columns

    An integration stats section for a cloud cost tool reading from AWS: six region lanes on one 0 to 24 hour ruler showing how far each region's cost data runs behind, with a solid tick at the 6 hour agreement.

  • Pro

    Datadog Grid Integration

    Switch and tick grids

    An integration grid section for a post-incident review tool connecting to Datadog: six embeddable sources as drawn, whole-card checkboxes with a limit of four per review and a counter that follows the choices.

  • Pro

    A tabbed integration directory for an integration hub: twelve tiles with abstract monograms, each with a connect switch, three category tabs and a live count of what is connected.