shadcn.io is not affiliated with official shadcn/ui
S3 Bucket Usage Monitoring Block for Ark UI
Eight key prefixes ranked by requests a second for GET, PUT or LIST against a per-prefix ceiling, with throttled counts and minutes over in words, plus bucket facts, storage by class and a lifecycle preview.
Installation
Overview
See which key prefixes of an object-store bucket are being throttled, with this bucket panel for React with Ark UI. It is Bucketry, a storage monitor (made up) for an S3-style object store. A hairline frame with a plus mark on each corner holds eight key prefixes as rows, ordered by requests a second for the operation chosen in a native select (GET, PUT or LIST). Each row is a bar with a tick at the per-prefix ceiling, the count of throttled requests and how long it was over, in words. The header names how many prefixes were throttled and suggests spreading the worst one by a hash. A side cell holds the bucket facts (storage, objects, average size, data out), storage split by class, and a lifecycle preview: choose an age and read how much a move to Infrequent would shift. Guides draw the frame; the entrance is CSS only. For platform teams that run busy buckets.
FAQ
How do I use my own prefixes?
Edit PREFIXES at the top of the file: each prefix has requests a second:minutes over for GET, PUT and LIST. OPERATIONS holds the ceilings, FACTS the bucket facts, and CLASSES and RULES the class sizes and the lifecycle table. Throttled counts are derived as the excess over the ceiling times the minutes over times 60.
Where do the ceilings come from?
They are this demo's own numbers (4,000 GET, 1,500 PUT and 800 LIST a second per prefix) and say nothing about any real service's limits. Set ceiling in OPERATIONS to the limit you care about.
What does the lifecycle preview do?
It reads a typed table of how many gigabytes of Standard storage are older than 30, 60 or 90 days, and says how much would move to Infrequent and what would remain. It is a preview only: nothing is moved, and the table is an example, not a scan of a bucket.
What is real here and what stays local?
All the figures are typed and the product is made up; nothing calls a storage service. Changing the operation or the lifecycle age only changes what the panel shows, and the status line says what it now reads.