AWS opensearch-service documentation change
Summary
Updated terminology from 'manager' to 'master' in alarm names and documentation references (e.g., ManagerCPUUtilization → MasterCPUUtilization, dedicated manager nodes → dedicated master nodes)
Security assessment
Changes involve terminology alignment rather than addressing security vulnerabilities or introducing security features. No evidence of security context in the diff.
Diff
diff --git a/opensearch-service/latest/developerguide/cloudwatch-alarms.md b/opensearch-service/latest/developerguide/cloudwatch-alarms.md index ab59df03f..3f713db34 100644 --- a//opensearch-service/latest/developerguide/cloudwatch-alarms.md +++ b//opensearch-service/latest/developerguide/cloudwatch-alarms.md @@ -35,3 +35,3 @@ Alarm | Issue -`ManagerCPUUtilization` maximum is >= 50% for 15 minutes, 3 consecutive times | Consider using larger instance types for your [dedicated manager nodes](./managedomains-dedicatedmasternodes.html). Because of their role in cluster stability and [blue/green deployments](./managedomains-configuration-changes.html), dedicated manager nodes should have lower CPU usage than data nodes. -`ManagerJVMMemoryPressure` maximum is >= 95% for 1 minute, 3 consecutive times -`ManagerOldGenJVMMemoryPressure` maximum is >= 80% for 1 minute, 3 consecutive times +`MasterCPUUtilization` maximum is >= 50% for 15 minutes, 3 consecutive times | Consider using larger instance types for your [dedicated master nodes](./managedomains-dedicatedmasternodes.html). Because of their role in cluster stability and [blue/green deployments](./managedomains-configuration-changes.html), dedicated master nodes should have lower CPU usage than data nodes. +`MasterJVMMemoryPressure` maximum is >= 95% for 1 minute, 3 consecutive times +`MasterOldGenJVMMemoryPressure` maximum is >= 80% for 1 minute, 3 consecutive times @@ -42 +42 @@ Alarm | Issue -`ManagerReachableFromNode` maximum is < 1 for 5 minutes, 1 consecutive time | This alarm indicates that the manager node stopped or is unreachable. These failures are usually the result of a network connectivity issue or an AWS dependency problem. +`MasterReachableFromNode` maximum is < 1 for 5 minutes, 1 consecutive time | This alarm indicates that the master node stopped or is unreachable. These failures are usually the result of a network connectivity issue or an AWS dependency problem. @@ -81 +81 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please -Dedicated manager nodes +Dedicated master nodes