AWS sap documentation change
Summary
Updated command syntax formatting (removed '#' from prompts), clarified secondary IP address purpose, and adjusted quotation marks for consistency
Security assessment
Changes involve formatting corrections (command prompts), clarifications about cluster redundancy, and typo fixes. No explicit security vulnerability fixes or new security guidance introduced. Security-related content like encryption keys and hacluster password updates were already present in previous version.
Diff
diff --git a/sap/latest/sap-hana/sap-hana-on-aws-cluster-configuration.md b/sap/latest/sap-hana/sap-hana-on-aws-cluster-configuration.md index 877e0b0c6..cb2a8ed06 100644 --- a//sap/latest/sap-hana/sap-hana-on-aws-cluster-configuration.md +++ b//sap/latest/sap-hana/sap-hana-on-aws-cluster-configuration.md @@ -5 +5 @@ -System loggingCorosync configurationCreate encryption keysCreate secondary IP addressesReview instance settingsCreate the Corosync configuration fileUpdate the hacluster passwordStart the cluster +System loggingCorosync configurationCreate encryption keysCreate secondary IP addresses for a redundant cluster ringReview instance settings that conflict with cluster actionsCreate the Corosync configuration fileUpdate the hacluster passwordStart the cluster @@ -35,3 +35,3 @@ SUSE recommends using the rsyslogd daemon for logging in the SUSE cluster. Insta - prihana:~ # zypper install rsyslog - prihana:~ # systemctl enable logd - prihana:~ # systemctl start logd + prihana:~ zypper install rsyslog + prihana:~ systemctl enable logd + prihana:~ systemctl start logd @@ -45 +45 @@ The cluster service (Pacemaker) should be in a stopped state when performing clu - prihana:~ # systemctl status pacemaker + prihana:~ systemctl status pacemaker @@ -49 +49 @@ The cluster service (Pacemaker) should be in a stopped state when performing clu - prihana:~ # systemctl stop pacemaker + prihana:~ systemctl stop pacemaker @@ -59 +59 @@ Run the following command to create a secret key which is used to encrypt all th - prihana:~ # corosync-keygen + prihana:~ corosync-keygen @@ -61 +61 @@ Run the following command to create a secret key which is used to encrypt all th -A new key file called “`authkey`” is created at location `/etc/corosync/`. Copy this file to the same location on the second cluster node with the same permissions and ownership. +A new key file called "authkey" is created at location `/etc/corosync/`. Copy this file to the same location on the second cluster node with the same permissions and ownership. @@ -83 +83 @@ You must ensure that stop protection is disabled for Amazon EC2 instances that a -All cluster nodes are required to have a local configuration file “`/etc/corosync/corosync.conf`”, as shown in the following example. +All cluster nodes are required to have a local configuration file "/etc/corosync/corosync.conf", as shown in the following example. @@ -86 +86 @@ All cluster nodes are required to have a local configuration file “`/etc/coros - prihana:/etc/corosync # cat corosync.conf + prihana:/etc/corosync cat corosync.conf @@ -161 +161 @@ Change the password of the user `haclustser` on both the nodes as shown in the f - prihana:~ # passwd hacluster + prihana:~ passwd hacluster @@ -164 +164 @@ Change the password of the user `haclustser` on both the nodes as shown in the f - sechana:~ # passwd hacluster + sechana:~ passwd hacluster @@ -172 +172 @@ Start the cluster on both the primary and secondary nodes and check the status. - prihana:~ # systemctl status pacemaker + prihana:~ systemctl status pacemaker @@ -176 +176 @@ Start the cluster on both the primary and secondary nodes and check the status. - prihana:~ # systemctl start pacemaker + prihana:~ systemctl start pacemaker @@ -184 +184 @@ After the cluster service (Pacemaker) is started, check the cluster status with - prihana:~ # crm_mon -r + prihana:~ crm_mon -r @@ -202 +202 @@ You can find the ring status and the associated IP address of the cluster with t - prihana:~ # corosync-cfgtool -s + prihana:~ corosync-cfgtool -s