AWS opensearch-service documentation change
Summary
Clarified instance type selection for coordinator nodes
Security assessment
The change provides general documentation improvements without security implications.
Diff
diff --git a/opensearch-service/latest/developerguide/Dedicated-coordinator-nodes.md b/opensearch-service/latest/developerguide/Dedicated-coordinator-nodes.md index d87de3439..79cbf968d 100644 --- a//opensearch-service/latest/developerguide/Dedicated-coordinator-nodes.md +++ b//opensearch-service/latest/developerguide/Dedicated-coordinator-nodes.md @@ -88 +88,5 @@ Consider the following best practices when you use dedicated coordinator nodes. - * A good starting point is to provision between 5% and 10% of your data nodes as dedicated coordinator nodes. For example, if your domain has 90 `r6g.large` data nodes, consider provisioning 5 to 9 `r6g.large` coordinator nodes. + * A good starting point is to provision between 5% and 10% of your data nodes as dedicated coordinator nodes. For example, if your domain has 90 data nodes of a particular instance type, consider provisioning 5 to 9 coordinator nodes of the same instance type. + +###### Note + +Instance type availability varies by region. When selecting instance types for coordinator nodes, verify that your chosen instance type is available in your target region. You can check instance type availability in the OpenSearch Service console when creating or modifying your domain.