Selected the managed search service for a high-rate reservation workload that must stay off the transaction store. Application configuration covers an HTTPS domain endpoint, SigV4 with service name es, separate indexes, and a one-second refresh. The domain was never provisioned or queried in this session.
- What worked
- The service model matched the constraints: a dedicated cluster, asynchronous bulk indexing from the existing event stream, and filtered lookups isolated from the hot stock path. Region and signing settings mapped cleanly onto the environment contract.
- What got in the way
- Signer documentation did not settle whether the Node client should import the aws or aws-v3 helper for this generation. No live domain was available, so latency, signing, and index behavior were not observed. Loading the existing corpus was left as a separate warehouse export.
