AWS sap documentation change
Summary
Updated section headers, fixed punctuation/formatting, and clarified fencing agent documentation
Security assessment
Changes are primarily structural (e.g., 'Concepts' to 'Topics' header), formatting fixes (quotation marks, italics removal), and punctuation corrections. The fencing agent explanation remains functionally unchanged - while fencing relates to cluster reliability, the changes don't introduce new security content or address vulnerabilities.
Diff
diff --git a/sap/latest/sap-netweaver/rhel-netweaver-ha-planning.md b/sap/latest/sap-netweaver/rhel-netweaver-ha-planning.md index 333e8d03c..89d1e6c65 100644 --- a//sap/latest/sap-netweaver/rhel-netweaver-ha-planning.md +++ b//sap/latest/sap-netweaver/rhel-netweaver-ha-planning.md @@ -5 +5 @@ -PrerequisitesReliabilitySAP and Red Hat referencesConceptsLaunch Wizard for SAP +PrerequisitesReliabilitySAP and Red Hat referencesConceptsAutomation and AWS Launch Wizard for SAP @@ -64 +64 @@ SAP and Red Hat recommend the use of Red Hat Enterprise Linux for SAP. Starting -Built on the Red Hat Enterprise Linux operating system, Red Hat Enterprise Linux for SAP expands existing capabilities, lso you can get the most out of SAP's powerful analytics and data management portfolio. See [Red Hat Enterprise Solutions for SAP](https://www.redhat.com/en/technologies/linux-platforms/enterprise-linux/sap) product page from Red Hat. +Built on the Red Hat Enterprise Linux operating system, Red Hat Enterprise Linux for SAP expands existing capabilities, lso you can get the most out of SAP’s powerful analytics and data management portfolio. See [Red Hat Enterprise Solutions for SAP](https://www.redhat.com/en/technologies/linux-platforms/enterprise-linux/sap) product page from Red Hat. @@ -124 +124 @@ This section covers AWS, SAP, and Red Hat concepts. -###### Concepts +###### Topics @@ -209 +209 @@ An enterprise landing zone setup or security requirements may require the use of -Evaluate the operational impact against your security posture before setting up shared VPC. To set up, see [Shared VPC – _optional_](https://docs.aws.amazon.com/sap/latest/sap-netweaver/rhel-netweaver-ha-settings.html#rhel-netweaver-ha-shared-vpc). +Evaluate the operational impact against your security posture before setting up shared VPC. To set up, see [Shared VPC – optional](https://docs.aws.amazon.com/sap/latest/sap-netweaver/rhel-netweaver-ha-settings.html#rhel-netweaver-ha-shared-vpc). @@ -215 +215 @@ In a two-node cluster setup for a primary resource and its replication pair, it -Since a two-node cluster introduces the possibility of a fence race in which a dual shoot out can occur with communication failures resulting in both nodes simultaneously claiming, “I can’t see you, so I am going to power you off”. The fencing agent is designed to minimise this risk by providing an external witness. +Since a two-node cluster introduces the possibility of a fence race in which a dual shoot out can occur with communication failures resulting in both nodes simultaneously claiming, "I can’t see you, so I am going to power you off". The fencing agent is designed to minimise this risk by providing an external witness. @@ -217 +217 @@ Since a two-node cluster introduces the possibility of a fence race in which a d -Red Hat supports several fencing agents, including the one recommended for use with Amazon EC2 Instances (`fence_aws `). This resource uses API commands to check its own instance status - “Is my instance state anything other than running?” before proceeding to power off its pair. If it is already in a stopping or stopped state it will admit defeat and leave the surviving node untouched. +Red Hat supports several fencing agents, including the one recommended for use with Amazon EC2 Instances (`fence_aws `). This resource uses API commands to check its own instance status - "Is my instance state anything other than running?" before proceeding to power off its pair. If it is already in a stopping or stopped state it will admit defeat and leave the surviving node untouched.