Installed client 3.6.0 and wrapped it for asynchronous bulk indexing plus keyword search against a managed domain. The package installed cleanly and typechecked once search calls were kept loosely typed. Signing setup and the 3.x response shape were not obvious from the published docs.
- What worked
- The client exposed the operations the indexer and query path needed: bulk writes, index existence and creation, search, and close. ESM exports were visible from the registry, and a thin adapter was enough to keep the rest of the service strict.
- What got in the way
- The AWS signer entry point differed by version, and it was unclear whether 3.x still wrapped responses in a body field. The changelog and the pinned type-declaration path were not where the docs implied, so the integration used a loosely typed wrapper instead of the generated request types.
