AWS sap documentation change
Summary
Consolidated duplicate steps about Nitro system EBS volume configuration and renumbered subsequent migration steps. Removed redundant step 3 (instance launch issues) and merged its consequence into step 2 (SAP HANA startup issues). Updated step numbering from 4-12 to 3-11.
Security assessment
The changes primarily address documentation clarity and redundancy removal. The EBS/Nitro system guidance focuses on operational correctness (preventing instance startup failures) rather than patching vulnerabilities or mitigating security risks. No explicit security vulnerabilities, access controls, or encryption mechanisms are mentioned. References to CloudTrail/Config in renumbered steps are not new security content.
Diff
diff --git a/sap/latest/sap-hana/migrating-hana-to-hm.md b/sap/latest/sap-hana/migrating-hana-to-hm.md index b21ffc0ab..c4ca24c76 100644 --- a//sap/latest/sap-hana/migrating-hana-to-hm.md +++ b//sap/latest/sap-hana/migrating-hana-to-hm.md @@ -132,3 +132 @@ In this option, if you are using `u7i*`, `u-6tb1.56xlarge` or `u-*tb1.112xlarge` - 2. EC2 High Memory instances are based on the Nitro system. On Nitro-based instances, EBS volumes are presented as NVMe block devices. If your source system has any mount point entries in `/etc/fstab` with reference to block devices such as `/dev/xvd<x>`, you need to create a label for these devices and mount them by label before migrating to EC2 High Memory instances. Otherwise, you will face issues during instance launch. - - 3. EC2 High Memory instances are based on the Nitro system. On Nitro-based instances, EBS volumes are presented as NVMe block devices. If your source system has any mount point entries in `/etc/fstab` with reference to block devices such as `/dev/xvd<x>`, you need to create a label for these devices and mount them by label before migrating to EC2 High Memory instances. Otherwise, you will face issues when you start SAP HANA on an EC2 High Memory instance. + 2. EC2 High Memory instances are based on the Nitro system. On Nitro-based instances, EBS volumes are presented as NVMe block devices. If your source system has any mount point entries in `/etc/fstab` with reference to block devices such as `/dev/xvd<x>`, you need to create a label for these devices and mount them by label before migrating to EC2 High Memory instances. Otherwise, you will face issues when you start SAP HANA on an EC2 High Memory instance. @@ -136 +134 @@ In this option, if you are using `u7i*`, `u-6tb1.56xlarge` or `u-*tb1.112xlarge` - 4. When you are ready to migrate, verify that you have a good backup of your source system. + 3. When you are ready to migrate, verify that you have a good backup of your source system. @@ -138 +136 @@ In this option, if you are using `u7i*`, `u-6tb1.56xlarge` or `u-*tb1.112xlarge` - 5. Stop the source instance in the Amazon EC2 console or by using the AWS CLI. + 4. Stop the source instance in the Amazon EC2 console or by using the AWS CLI. @@ -140 +138 @@ In this option, if you are using `u7i*`, `u-6tb1.56xlarge` or `u-*tb1.112xlarge` - 6. Change the instance type to target EC2 High Memory instance size such as `u7i*`, `u-6tb1.56xlarge` or `u-*tb1.112xlarge`. + 5. Change the instance type to target EC2 High Memory instance size such as `u7i*`, `u-6tb1.56xlarge` or `u-*tb1.112xlarge`. @@ -142 +140 @@ In this option, if you are using `u7i*`, `u-6tb1.56xlarge` or `u-*tb1.112xlarge` - 7. When you increase the memory of your SAP HANA system, you might need to adjust the storage size of SAP HANA data, log, shared, and backup volumes as well to accommodate data growth and to get improved performance. For details, see the [SAP HANA on AWS Operations Guide](https://docs.aws.amazon.com/sap/latest/sap-hana/sap-hana-on-aws-operations.html). + 6. When you increase the memory of your SAP HANA system, you might need to adjust the storage size of SAP HANA data, log, shared, and backup volumes as well to accommodate data growth and to get improved performance. For details, see the [SAP HANA on AWS Operations Guide](https://docs.aws.amazon.com/sap/latest/sap-hana/sap-hana-on-aws-operations.html). @@ -144 +142 @@ In this option, if you are using `u7i*`, `u-6tb1.56xlarge` or `u-*tb1.112xlarge` - 8. Start your SAP HANA database and perform your validation. + 7. Start your SAP HANA database and perform your validation. @@ -150 +148 @@ If necessary, complete any SAP HANA-specific post-migration activities. - 9. Check the connectivity between your SAP application servers and the new SAP HANA instance. + 8. Check the connectivity between your SAP application servers and the new SAP HANA instance. @@ -152 +150 @@ If necessary, complete any SAP HANA-specific post-migration activities. - 10. If necessary, complete any AWS-specific post-migration activities, such as setting up Amazon CloudWatch, AWS Config, and AWS CloudTrail. + 9. If necessary, complete any AWS-specific post-migration activities, such as setting up Amazon CloudWatch, AWS Config, and AWS CloudTrail. @@ -154 +152 @@ If necessary, complete any SAP HANA-specific post-migration activities. - 11. Configure your SAP HANA system for high availability on the EC2 High Memory instance with SAP HANA HSR and clustering software, and test it. + 10. Configure your SAP HANA system for high availability on the EC2 High Memory instance with SAP HANA HSR and clustering software, and test it. @@ -156 +154 @@ If necessary, complete any SAP HANA-specific post-migration activities. - 12. Complete post-migration tasks to ensure that you are not charged. + 11. Complete post-migration tasks to ensure that you are not charged.