A client of mine spun up a new Amazon Redshift Serverless workgroup, pointed their nightly ELT job at it, and moved on. Three weeks later the AWS bill landed and the Redshift line item was almost four times what they'd modeled. Nobody had touched a knob. The workgroup was still running the base capacity the console picked for them when they clicked "Create": 128 RPUs, on all day, whether anyone was querying or not.
That's the trap with Redshift Serverless. It removes the "how big should this cluster be" question at setup time, but it doesn't remove the need to answer it, it just moves that question to your first bill.
What an RPU actually buys you
A Redshift Processing Unit (RPU) is a bundle of compute and memory, 16 GB of memory per RPU. Base capacity is what a workgroup runs at when idle-but-warm, and Redshift Serverless scales up from there automatically under load.…