aws-s3-tables-demo

was uncached: every request loaded DuckDB, assumed the role and read the Iceberg table, about 5 seconds of function time (measured on the hosted demo). Anyone could run up compute and S3 Tables reads by calling it in a loop. It now reads through , the same 60-second cache the page uses. The append and reset controls call , so their changes still appear immediately; only command-line writes () wait out the window, as they already did for the page. The hosted demo also has a Vercel Firewall rule limiting and (the server actions) to 10 requests per minute per IP. Checked with and . 🤖 Generated with Claude Code

Adds a Demo: link to the hosted demo at https://aws-s3-tables.vercel.app/, matching the general purpose buckets README. The demo runs on the vercel-labs team, connected to this repo and deployed from . 🤖 Generated with Claude Code