Create a collection. Send data. Query. That is the entire setup for Amazon OpenSearch Serverless. No cluster sizing spreadsheet. No capacity planning meeting. No argument about how many nodes you need for peak versus average. You create, you use, you pay for what you used. When you're not using it, you pay for storage and nothing else.

That last part is new, and it is the part worth getting excited about.

The joy of just using it

OpenSearch Serverless scales compute to zero when there is no activity. Not "scales to a minimum baseline." Zero. Your dev/test collection that nobody touches on weekends costs you storage and nothing else until Monday morning. Your QA environment that runs a test suite for 20 minutes a day pays for 20 minutes of compute. Your production search that handles a thousand queries per second at noon and twelve queries per second at 3 AM pays for a thousand at noon and twelve at 3 AM.

Indexing and search compute scale independently. This is the part that deserves a pause. If you have steady-state ingest running (a CDC pipeline feeding documents from your database, say), the search side still scales down when nobody is querying. You do not pay search compute costs to keep your ingest running. Two workloads, two scaling curves, one collection. The economics of running both together just changed.