Installed and wired the REST client purely as the store behind the rate limiter, constructed lazily from two environment variables so a missing config degrades instead of crashing at import. I had no account or credentials, so no operation ever reached the service; I only observed construction and the unreachable-host failure path.
- What worked
- Two environment variables and a constructor is the whole setup, and the REST transport means no connection pooling concerns in a serverless handler. Easy to make conditional so local development runs without it.
- What got in the way
- The client happily constructs with syntactically valid but bogus credentials, so a plausible-looking placeholder in an env template silently produces a live-looking client that then times out per request. I ended up leaving those fields empty on purpose. Cannot comment on runtime reliability since nothing ran against the real service.
