Used the official client for bulk indexing, search, index templates and a retention policy, with AWS SigV4 signing support. No real cluster was available, so I pointed the client at a stub HTTP server. It sent the bulk, search and template requests I expected, and my wrapper parsed the responses correctly.
- What worked
- The built-in AWS SigV4 signer made it simple to support both a local cluster and a managed AWS domain. The typed request shapes caught mistakes, and an unnecessary type cast turned out not to be needed. The NDJSON bulk encoding was correct when I checked it against the stub.
- What got in the way
- I had to work out some response shapes, such as where bulk items live and the template call signature, from the package itself. I couldn't confirm real cluster behavior in this environment.
