AWS sap documentation change
Summary
Formatting changes to command examples (removed leading #), templatized hostnames with angle brackets, updated section headers, and restructured SNS alert configuration instructions with proper syntax
Security assessment
Changes focus on documentation formatting, command syntax corrections, and templating placeholders. No evidence of addressing vulnerabilities or security incidents. The SNS alert configuration improvements relate to operational monitoring rather than introducing new security features or mitigating specific vulnerabilities.
Diff
diff --git a/sap/latest/sap-AnyDB/rhel-ase-ha-operations-topics.md b/sap/latest/sap-AnyDB/rhel-ase-ha-operations-topics.md index 588139071..2caa8e90f 100644 --- a//sap/latest/sap-AnyDB/rhel-ase-ha-operations-topics.md +++ b//sap/latest/sap-AnyDB/rhel-ase-ha-operations-topics.md @@ -33 +33 @@ There are multiple operating system commands that can be run as root or as a use - # pcs status + pcs status @@ -38 +38 @@ Sample output: - # pcs status + pcs status @@ -42 +42 @@ Sample output: - * Current DC: rhxdbhost01 (version 2.1.2-4.el8_6.5-ada5c3b36e2) - partition with quorum + * Current DC: <rhxdbhost01> (version 2.1.2-4.el8_6.5-ada5c3b36e2) - partition with quorum @@ -44 +44 @@ Sample output: - * Last change: Mon Apr 10 14:55:08 2023 by root via crm_resource on rhxdbhost01 + * Last change: Mon Apr 10 14:55:08 2023 by root via crm_resource on <rhxdbhost01> @@ -52,6 +52,6 @@ Sample output: - * rsc_ip_ARD_ASEDB (ocf::heartbeat:aws-vpc-move-ip): Started rhxdbhost01 - * rsc_fs_ARD_sybase (ocf::heartbeat:Filesystem): Started rhxdbhost01 - * rsc_fs_ARD_data (ocf::heartbeat:Filesystem): Started rhxdbhost01 - * rsc_fs_ARD_log (ocf::heartbeat:Filesystem): Started rhxdbhost01 - * rsc_fs_ARD_sapdiag (ocf::heartbeat:Filesystem): Started rhxdbhost01 - SAP NetWeaver on AWS SAP NetWeaver Guides + * rsc_ip_ARD_ASEDB (ocf::heartbeat:aws-vpc-move-ip): Started <rhxdbhost01> + * rsc_fs_ARD_sybase (ocf::heartbeat:Filesystem): Started <rhxdbhost01> + * rsc_fs_ARD_data (ocf::heartbeat:Filesystem): Started <rhxdbhost01> + * rsc_fs_ARD_log (ocf::heartbeat:Filesystem): Started <rhxdbhost01> + * rsc_fs_ARD_sapdiag (ocf::heartbeat:Filesystem): Started <rhxdbhost01> + SAP NetWeaver on {aws} SAP NetWeaver Guides @@ -60,4 +60,4 @@ Sample output: - * rsc_fs_ARD_saptmp (ocf::heartbeat:Filesystem): Started rhxdbhost01 - * rsc_fs_ARD_backup (ocf::heartbeat:Filesystem): Started rhxdbhost01 - * rsc_fs_ARD_usrsap (ocf::heartbeat:Filesystem): Started rhxdbhost01 - * rsc_ase_ARD_ASEDB (ocf::heartbeat:SAPDatabase): Started rhxdbhost01 + * rsc_fs_ARD_saptmp (ocf::heartbeat:Filesystem): Started <rhxdbhost01> + * rsc_fs_ARD_backup (ocf::heartbeat:Filesystem): Started <rhxdbhost01> + * rsc_fs_ARD_usrsap (ocf::heartbeat:Filesystem): Started <rhxdbhost01> + * rsc_ase_ARD_ASEDB (ocf::heartbeat:SAPDatabase): Started <rhxdbhost01> @@ -85 +85 @@ There are different options to perform planned maintenance on nodes, resources, -###### Options +###### Topics @@ -106 +106 @@ Use the following command to turn on maintenance mode. - # pcs property set maintenance-mode="true" + pcs property set maintenance-mode="true" @@ -111 +111,4 @@ Off -Use the following command to turn off maintenance mode. + * Use the following command to turn off maintenance mode. + + pcs property set maintenance-mode="false" + @@ -114 +116,0 @@ Use the following command to turn off maintenance mode. - # pcs property set maintenance-mode="false" @@ -121 +123 @@ To perform maintenance on the cluster without system outage, the recommended met - # pcs node standby rhxdbhost01 + pcs node standby <rhxdbhost01> @@ -126 +128 @@ The cluster will cleanly relocate resources, and you can perform activities, inc - # pcs node unstandby rhxdbhost01 + pcs node unstandby <rhxdbhost01> @@ -133 +135 @@ Moving individual resources is not recommended because of the migration or move - rhxdbhost01:~ # pcs resource move grp_ARD_ASEDB + <rhxdbhost01>:~ # pcs resource move <grp_ARD_ASEDB> @@ -135 +137 @@ Moving individual resources is not recommended because of the migration or move - Note: Move constraint created for grp_ARD_ASEDB to rhxdbhost02 + Note: Move constraint created for <grp_ARD_ASEDB> to <rhxdbhost02> @@ -187 +188 @@ Use the help command to understand the impact of these commands. -It is recommended that failed (or fenced) nodes are not automatically restarted. It gives operators a chance to investigate the failure, and ensure that the cluster doesn't make assumptions about the state of resources. +It is recommended that failed (or fenced) nodes are not automatically restarted. It gives operators a chance to investigate the failure, and ensure that the cluster doesn’t make assumptions about the state of resources. @@ -221 +222 @@ The agents can then be configured to send emails, log to a file, update a monito - # + @@ -224 +225 @@ The agents can then be configured to send emails, log to a file, update a monito - # + @@ -227,7 +228,7 @@ The agents can then be configured to send emails, log to a file, update a monito - # * Create an SNS Topic and subscribe email or chatbot - # * Note down the ARN for the SNS topic - # * Give the IAM Role attached to both Instances permission to publish to the SNS Topic - # * Ensure the aws cli is installed - # * Copy this file to /usr/share/pacemaker/alerts/alert_sns.sh or other location on BOTH nodes - # * Ensure the permissions allow for hacluster and root to execute the script - # * Run the following as root (modify file location if necessary and replace SNS ARN): + * Create an SNS Topic and subscribe email or chatbot + * Note down the ARN for the SNS topic + * Give the IAM Role attached to both Instances permission to publish to the SNS Topic + * Ensure the aws cli is installed + * Copy this file to /usr/share/pacemaker/alerts/alert_sns.sh or other location on BOTH nodes + * Ensure the permissions allow for hacluster and root to execute the script + * Run the following as root (modify file location if necessary and replace SNS ARN): @@ -236 +237,2 @@ The agents can then be configured to send emails, log to a file, update a monito - # crm configure alert aws_sns_alert /usr/share/pacemaker/alerts/alert_sns.sh meta timeout=30s timestamp-format="%Y-%m-%d_%H:%M:%S" to { arn:aws:sns:region:account-id:myPacemakerAlerts } + crm configure alert aws_sns_alert /usr/share/pacemaker/alerts/alert_sns.sh meta timeout=30s timestamp-format="%Y-%m-%d_%H:%M:%S" to <{ arn:aws:sns:region:account-id:myPacemakerAlerts }> + @@ -238,2 +240,2 @@ The agents can then be configured to send emails, log to a file, update a monito - # pcs alert create id=aws_sns_alert path=/usr/share/pacemaker/alerts/alert_sns.sh meta timeout=30s timestamp-format="%Y-%m-%d_%H:%M:%S" - # pcs alert recipient add aws_sns_alert value=arn:aws:sns:region:account-id:myPacemakerAlerts + pcs alert create id=aws_sns_alert path=/usr/share/pacemaker/alerts/alert_sns.sh meta timeout=30s timestamp-format="%Y-%m-%d_%H:%M:%S" + pcs alert recipient add aws_sns_alert value=<arn:aws:sns:region:account-id:myPacemakerAlerts>