AWS Security ChangesHomeSearch

AWS sap documentation change

Service: sap · 2025-04-25 · Documentation low

File: sap/latest/sap-hana/sap-hana-on-aws-test-3-crash-primary-sap-hana-database-on-node-1-sles.md

Summary

Fixed command prompt formatting, corrected markdown syntax, and improved documentation structure for test procedures

Security assessment

Changes are purely editorial/formatting improvements to command examples and documentation structure. No security-related content was added or modified. The test procedure remains functionally identical in terms of cluster recovery operations.

Diff

diff --git a/sap/latest/sap-hana/sap-hana-on-aws-test-3-crash-primary-sap-hana-database-on-node-1-sles.md b/sap/latest/sap-hana/sap-hana-on-aws-test-3-crash-primary-sap-hana-database-on-node-1-sles.md
index 2e646fdd4..c5536bb2c 100644
--- a//sap/latest/sap-hana/sap-hana-on-aws-test-3-crash-primary-sap-hana-database-on-node-1-sles.md
+++ b//sap/latest/sap-hana/sap-hana-on-aws-test-3-crash-primary-sap-hana-database-on-node-1-sles.md
@@ -15 +15 @@
-        prihana:~ # sudo su - hdbadm
+        prihana:~  sudo su - hdbadm
@@ -33,4 +33 @@
-
-
-
-**Expected result** : 
+    * Expected result**:
@@ -40 +37 @@
-        prihana:~ # crm status
+        prihana:~  crm status
@@ -72 +66 @@
-  * With the `AUTOMATIC_REGISTER` parameter set to "`true`", the cluster restarts the failed SAP HANA database and automatically registers it against the new primary. 
+  * With the `AUTOMATIC_REGISTER` parameter set to "true", the cluster restarts the failed SAP HANA database and automatically registers it against the new primary.
@@ -73,0 +68 @@
+    * Recovery procedure**:
@@ -74,0 +70 @@
+  * Clean up the cluster "failed actions" on node 1 as root.
@@ -76,6 +72 @@
-
-**Recovery procedure** : 
-
-  * Clean up the cluster “`failed actions`” on node 1 as root. 
-    
-        prihana:~ # crm resource cleanup rsc_SAPHana_HDB_HDB00 prihana
+        prihana:~  crm resource cleanup rsc_SAPHana_HDB_HDB00 prihana
@@ -86,4 +77 @@
-
-
-
-  * After resource cleanup, the cluster “`failed actions`” are cleaned up. 
+  * After resource cleanup, the cluster "failed actions" are cleaned up.