A version lookup for Amazon OpenSearch Service succeeded, and the implementation targeted engine 3.7 on a managed, network-isolated domain. Encryption, snapshots, fine-grained access, and request signing were specified in infrastructure and client code so search load stays off the transactional store.
- What worked
- The version lookup was specific enough to pin engine 3.7. The managed domain model matches an isolated search plane with encryption, snapshots, and access control separated from reservation traffic.
- What got in the way
- The domain was never created and no query was sent, so latency, refresh, and failover were not observed. Access control, internal users, and signing were assembled without a console or API session. The domain targets engine 3.7 while the installed client is 3.6.0, and that pair was never executed together.
