AWS sap documentation change
Summary
Corrects command syntax and formatting in Pacemaker cluster setup documentation; uncomments EC2 source/destination check command; updates AWS CLI examples with placeholder syntax and Markdown formatting
Security assessment
The change replaces 'AWS' with '{aws}' in access key examples, promoting placeholder usage to avoid exposing credential formats. This improves security documentation by emphasizing placeholder substitution. The uncommented EC2 source/dest check command corrects documentation accuracy but does not directly address a vulnerability. Other changes are syntax/formatting fixes without security impact.
Diff
diff --git a/sap/latest/sap-AnyDB/sap-ibm-pacemaker-deployment.md b/sap/latest/sap-AnyDB/sap-ibm-pacemaker-deployment.md index 87c95669a..6f52b21a2 100644 --- a//sap/latest/sap-AnyDB/sap-ibm-pacemaker-deployment.md +++ b//sap/latest/sap-AnyDB/sap-ibm-pacemaker-deployment.md @@ -59,2 +59 @@ You need to disable source/destination check for your EC2 instance hosting prima - # aws ec2 modify-instance-attribute --profile cluster --instance-id EC2-instance-id --no-source-dest-check - + aws ec2 modify-instance-attribute --profile cluster --instance-id EC2-instance-id --no-source-dest-check @@ -403 +388 @@ This section focuses on setting up the Pacemaker cluster on the RHEL operating s - [root@dbprim00 ~]# pcs cluster auth dbprim00 dbsec00 + [root@dbprim00 ~] pcs cluster auth dbprim00 dbsec00 @@ -408,2 +393 @@ This section focuses on setting up the Pacemaker cluster on the RHEL operating s - [root@dbprim00 ~]# - + [root@dbprim00 ~] @@ -413 +397 @@ This section focuses on setting up the Pacemaker cluster on the RHEL operating s - [root@dbprim00 ~]# pcs cluster setup --name db2ha dbprim00 dbsec00 + [root@dbprim00 ~] pcs cluster setup --name db2ha dbprim00 dbsec00 @@ -433 +417 @@ This section focuses on setting up the Pacemaker cluster on the RHEL operating s - [root@dbprim00 ~]# pcs cluster enable --all + [root@dbprim00 ~] pcs cluster enable --all @@ -436 +420 @@ This section focuses on setting up the Pacemaker cluster on the RHEL operating s - [root@dbprim00 ~]# pcs cluster start --all + [root@dbprim00 ~] pcs cluster start --all @@ -439,2 +423 @@ This section focuses on setting up the Pacemaker cluster on the RHEL operating s - [root@dbprim00 ~]# - + [root@dbprim00 ~] @@ -446 +429 @@ This section focuses on setting up the Pacemaker cluster on the RHEL operating s - [root@dbprim00 corosync]# more /etc/corosync/corosync.conf + [root@dbprim00 corosync] more /etc/corosync/corosync.conf @@ -481 +463 @@ This section focuses on setting up the Pacemaker cluster on the RHEL operating s - [root@dbprim00 corosync]# **pcs cluster sync** + [root@dbprim00 corosync] pcs cluster sync @@ -488 +469 @@ This section focuses on setting up the Pacemaker cluster on the RHEL operating s - [root@dbprim00 corosync]# pcs cluster reload corosync + [root@dbprim00 corosync] pcs cluster reload corosync @@ -494 +474 @@ This section focuses on setting up the Pacemaker cluster on the RHEL operating s - [root@dbprim00 corosync]# corosync-cmapctl | grep totem.token + [root@dbprim00 corosync] corosync-cmapctl | grep totem.token @@ -503,2 +482 @@ This section focuses on setting up the Pacemaker cluster on the RHEL operating s - [root@dbprim00 ~]# pcs property set maintenance-mode=’true’ - + [root@dbprim00 ~] pcs property set maintenance-mode=’true’ @@ -510 +488 @@ If you want to have the instance remain in a stopped state until it has been inv - [root@dbprim00 ~]# pcs stonith create clusterfence fence_aws + [root@dbprim00 ~] pcs stonith create clusterfence fence_aws @@ -518 +495 @@ If you want to have the instance remain in a stopped state until it has been inv - [root@dbprim00 ~]# pcs resource create Db2_HADR_STJ db2 + [root@dbprim00 ~] pcs resource create Db2_HADR_STJ db2 @@ -529,2 +505,2 @@ If you want to have the instance remain in a stopped state until it has been inv - [root@dbprim00 ~]# ip address add 192.168.1.81/32 dev eth0 - [root@dbprim00 ~]# ip addr show + [root@dbprim00 ~] ip address add 192.168.1.81/32 dev eth0 + [root@dbprim00 ~] ip addr show @@ -545,2 +521 @@ If you want to have the instance remain in a stopped state until it has been inv - [root@dbprim00 ~]# - + [root@dbprim00 ~] @@ -552 +527 @@ If you want to have the instance remain in a stopped state until it has been inv - [root@dbprim00 ~]# aws ec2 create-route --route-table-id rtb- + [root@dbprim00 ~] aws ec2 create-route --route-table-id rtb- @@ -558 +533 @@ If you want to have the instance remain in a stopped state until it has been inv - [root@dbprim00 ~]# pcs resource create db2-oip aws-vpc-move-ip + [root@dbprim00 ~] pcs resource create db2-oip aws-vpc-move-ip @@ -568,2 +542 @@ If you want to have the instance remain in a stopped state until it has been inv - [root@dbprim00 ~]# pcs constraint colocation add db2-oip with master Db2_HADR_STJ-master 2000 - + [root@dbprim00 ~] pcs constraint colocation add db2-oip with master Db2_HADR_STJ-master 2000 @@ -573,2 +546 @@ If you want to have the instance remain in a stopped state until it has been inv - [root@dbprim00 ~]# pcs property set maintenance-mode=’false’ - + [root@dbprim00 ~] pcs property set maintenance-mode=’false’ @@ -578 +550 @@ This is the final configuration of the cluster: - [root@dbprim00 ~]# **pcs config show** + [root@dbprim00 ~] pcs config show @@ -631,2 +603 @@ This is the final configuration of the cluster: - [root@dbprim00 ~]# - + [root@dbprim00 ~] @@ -649,3 +620,3 @@ The SLES operating system’s resource agents use the [AWS Command Line Interfac - dbprim00:~ # aws configure - AWS Access Key ID [None]: - AWS Secret Access Key [None]: + dbprim00:~ aws configure + {aws} Access Key ID [None]: + {aws} Secret Access Key [None]: @@ -654,3 +625,3 @@ The SLES operating system’s resource agents use the [AWS Command Line Interfac - dbprim00:~ # aws configure --profile cluster - AWS Access Key ID [None]: - AWS Secret Access Key [None]: + dbprim00:~ aws configure --profile cluster + {aws} Access Key ID [None]: + {aws} Secret Access Key [None]: @@ -667 +637 @@ You don’t need to provide the Access Key and Secret Access key, because access -See [_To assign a secondary private IPv4 address to a network interface_](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/MultipleIP.html#assignIP-existing). +See [To assign a secondary private IPv4 address to a network interface](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/MultipleIP.html#assignIP-existing). @@ -669 +639 @@ See [_To assign a secondary private IPv4 address to a network interface_](https: - 4. Add a tag with an arbitrary “key” (in this case, `pacemaker`). The value of this tag is the hostname of the respective Db2 instance. This is required to enable AWS CLI to use filters in the API calls. + 4. Add a tag with an arbitrary "key" (in this case, `pacemaker`). The value of this tag is the hostname of the respective Db2 instance. This is required to enable AWS CLI to use filters in the API calls. @@ -679,2 +649 @@ See [_To assign a secondary private IPv4 address to a network interface_](https: - dbprim00:~ # zypper info cloud-netconfig-ec2 - + dbprim00:~ zypper info cloud-netconfig-ec2 @@ -682,3 +651 @@ See [_To assign a secondary private IPv4 address to a network interface_](https: - 9. Update the file `/etc/sysconfig/network/ifcfg-eth0` if this package is installed. Change the following line to a ‘no’ setting or add the following line if the package is not yet installed: - - dbprim00:~ # CLOUD_NETCONFIG_MANAGE='no' + 9. Update the file `/etc/sysconfig/network/ifcfg-eth0` if this package is installed. Change the following line to a "no" setting or add the following line if the package is not yet installed: @@ -685,0 +653 @@ See [_To assign a secondary private IPv4 address to a network interface_](https: + dbprim00:~ CLOUD_NETCONFIG_MANAGE='no' @@ -691,2 +659,2 @@ See [_To assign a secondary private IPv4 address to a network interface_](https: - dbprim00:~ # SUSEConnect --list-extensions - dbprim00:~ # SUSEConnect -p sle-module-public-cloud/12/x86_64 + dbprim00:~ SUSEConnect --list-extensions + dbprim00:~ SUSEConnect -p sle-module-public-cloud/12/x86_64 @@ -703,2 +670 @@ See [_To assign a secondary private IPv4 address to a network interface_](https: - dbprim00:~ # zypper -n update - + dbprim00:~ zypper -n update @@ -708,2 +674 @@ See [_To assign a secondary private IPv4 address to a network interface_](https: - dbprim00:~ # zypper install -t pattern ha_sles - + dbprim00:~ zypper install -t pattern ha_sles @@ -784 +747 @@ The chosen settings for `crypto_cipher` and `crypto_hash` are suitable for clust - dbprim00:~ # corosync-cfgtool -s + dbprim00:~ corosync-cfgtool -s @@ -793 +756 @@ The chosen settings for `crypto_cipher` and `crypto_hash` are suitable for clust - dbprim00:~ # + dbprim00:~ @@ -796 +759 @@ The chosen settings for `crypto_cipher` and `crypto_hash` are suitable for clust - dbprim00:~ # crm_mon -1 + dbprim00:~ crm_mon -1 @@ -817,2 +779,2 @@ The chosen settings for `crypto_cipher` and `crypto_hash` are suitable for clust - dbprim00:~ # crm configure property maintenance-mode="true" - dbprim00:~ # crm status + dbprim00:~ crm configure property maintenance-mode="true" + dbprim00:~ crm status @@ -837,2 +798,2 @@ The chosen settings for `crypto_cipher` and `crypto_hash` are suitable for clust - dbprim00:/ha-files # **vi crm-bs.txt** - dbprim00:/ha-files # more crm-bs.txt + dbprim00:/ha-files vi crm-bs.txt + dbprim00:/ha-files more crm-bs.txt @@ -855 +815 @@ The `off` setting forces the agents to shut down the instance. You have the opti - dbprim00:~ # crm configure load update crm-bs.txt + dbprim00:~ crm configure load update crm-bs.txt @@ -860,2 +820 @@ The `off` setting forces the agents to shut down the instance. You have the opti - -**To configure the AWS-specific STONITH resource #** : +**To configure the AWS-specific STONITH resource** : @@ -876,3 +834,3 @@ The EC2 tag `pacemaker` entry needs to match the tag chosen for the EC2 instance - dbprim00:/ha-files # **vi aws-stonith.txt** - dbprim00:/ha-files # more aws-stonith.txt - primitive res_AWS_STONITH stonith:external/ec2 \ + dbprim00:/ha-files vi aws-stonith.txt + dbprim00:/ha-files more aws-stonith.txt + primitive res_{aws}_STONITH stonith:external/ec2 \ @@ -884,2 +842 @@ The EC2 tag `pacemaker` entry needs to match the tag chosen for the EC2 instance - dbprim00:/ha-files # **crm configure load update aws-stonith.txt** - + dbprim00:/ha-files crm configure load update aws-stonith.txt @@ -905,2 +861,2 @@ The EC2 tag `pacemaker` entry needs to match the tag chosen for the EC2 instance - dbprim00:/ha-files # **vi db2res.txt** - dbprim00:/ha-files # more db2res.txt + dbprim00:/ha-files vi db2res.txt + dbprim00:/ha-files more db2res.txt @@ -915,2 +871 @@ The EC2 tag `pacemaker` entry needs to match the tag chosen for the EC2 instance - dbprim00:/ha-files # **crm configure load update db2res.txt** - + dbprim00:/ha-files crm configure load update db2res.txt @@ -925,2 +880,2 @@ The EC2 tag `pacemaker` entry needs to match the tag chosen for the EC2 instance - dbprim00:~# ip address add 192.168.1.81/32 dev eth0 - dbprim00:~# ip addr show + dbprim00:~ ip address add 192.168.1.81/32 dev eth0 + dbprim00:~ ip addr show @@ -944,2 +899 @@ The EC2 tag `pacemaker` entry needs to match the tag chosen for the EC2 instance - [root@dbprim00 ~]# - + [root@dbprim00 ~] @@ -954 +907 @@ The EC2 tag `pacemaker` entry needs to match the tag chosen for the EC2 instance - dbprim00:~ # aws ec2 create-route --route-table-id rtb-dbe0eba1 -- + dbprim00:~ aws ec2 create-route --route-table-id rtb-dbe0eba1 -- @@ -962 +915 @@ The `aws-vpc-move-ip` resource agent call the AWS command from the location `/us - dbprim00:/usr/bin # which aws + dbprim00:/usr/bin which aws @@ -964 +917 @@ The `aws-vpc-move-ip` resource agent call the AWS command from the location `/us - dbprim00:/usr/bin # ls -ltr aws + dbprim00:/usr/bin ls -ltr aws @@ -972,2 +924,2 @@ The `aws-vpc-move-ip` resource agent call the AWS command from the location `/us - dbprim00:/ha-files # **vi aws-move-ip.txt** - dbprim00:/ha-files # more aws-move-ip.txt + dbprim00:/ha-files vi aws-move-ip.txt + dbprim00:/ha-files more aws-move-ip.txt @@ -980,2 +932 @@ The `aws-vpc-move-ip` resource agent call the AWS command from the location `/us - dbprim00:/ha-files # **crm configure load update aws-move-ip.txt** - + dbprim00:/ha-files crm configure load update aws-move-ip.txt @@ -985 +936 @@ The `aws-vpc-move-ip` resource agent call the AWS command from the location `/us - dbprim00:/ha-files # more crm-cs.txt + dbprim00:/ha-files more crm-cs.txt