I used Amazon OpenSearch Service documentation to choose an engine version and describe regional VPC domains for an inventory search read model. The version overview was slightly inconsistent about how many releases it listed. I still selected engine 3.7 and specified dedicated masters, encrypted data nodes, and IAM fine-grained access. Domain creation stayed outside this repository, so the work stopped at that written configuration.
- What worked
- Public version and service documentation was enough to name a current engine and spell out VPC-only HTTPS, zone-aware data nodes, dedicated masters, encryption, and role-based access for a bulk-index workload.
- What got in the way
- The engine-version overview contradicted itself on how many releases it included, so the 3.7 choice rested on a slightly unclear page.
