AWS sap medium security documentation change
Summary
Updated problem headers to bold formatting, corrected markdown links (case sensitivity and syntax), fixed credential path typo (from './aws' to '~/.aws'), adjusted error message formatting, and updated documentation references.
Security assessment
The correction of the credentials path from './aws' to '~/.aws' addresses a critical documentation error. Misconfiguration due to an incorrect path could lead the AWS Backint agent to use unintended credentials or fail to assume the required IAM role, resulting in AccessDenied errors and potential backup/restore failures. This change ensures proper credential configuration, mitigating security risks from misauthentication.
Diff
diff --git a/sap/latest/sap-hana/aws-backint-agent-troubleshooting.md b/sap/latest/sap-hana/aws-backint-agent-troubleshooting.md index f0a748622..0cbda8291 100644 --- a//sap/latest/sap-hana/aws-backint-agent-troubleshooting.md +++ b//sap/latest/sap-hana/aws-backint-agent-troubleshooting.md @@ -47 +47 @@ To find logs to help you troubleshoot errors and failures, check the following l -###### Problem: Error returned when installing AWS Backint agent. +**Problem: Error returned when installing AWS Backint agent.** @@ -60 +59,0 @@ Error returned: - ln -s /usr/bin/python2.7 /usr/bin/python @@ -65 +64,3 @@ Error returned: -###### Problem: Unable to view the instance listed for installation with the SSM document. + ln -s /usr/bin/python2.7 /usr/bin/python + +**Problem: Unable to view the instance listed for installation with the SSM document.** @@ -82 +83 @@ Error returned: -###### Problem: The following error is returned when you use the SSM installation document. +**Problem: The following error is returned when you use the SSM installation document.** @@ -95 +96 @@ Error returned: -###### Problem: `AccessDenied` appears in agent logs. +**Problem:`AccessDenied` appears in agent logs.** @@ -107 +108 @@ Error returned: - * **Resolution** : Verify the [prerequisite steps](./aws-backint-agent-Amazon-S3.html#aws-backint-agent-s3-prerequisites) for installing the AWS Backint agent. + * **Resolution** : Verify the [prerequisite steps](./aws-backint-agent-amazon-s3.html#aws-backint-agent-s3-prerequisites) for installing the AWS Backint agent. @@ -112 +113 @@ Error returned: -###### Problem: Backup or recovery failed due to S3 connectivity +**Problem: Backup or recovery failed due to S3 connectivity** @@ -116 +117 @@ Error returned: - * **Resolution** : Verify the [prerequisite steps](./aws-backint-agent-Amazon-S3.html#aws-backint-agent-s3-prerequisites) for installing the AWS Backint agent. + * **Resolution** : Verify the [prerequisite steps](./aws-backint-agent-amazon-s3.html#aws-backint-agent-s3-prerequisites) for installing the AWS Backint agent. @@ -121 +122 @@ Error returned: -###### Problem: Agent logs display `Backint cannot execute hdbbackint` or `No such file or directory`. +**Problem: Agent logs display`Backint cannot execute hdbbackint` or `No such file or directory`.** @@ -134 +135 @@ Error returned: -###### Problem: The following error is displayed when initiating a backup from the SAP HANA console: +**Problem: The following error is displayed when initiating a backup from the SAP HANA console:** @@ -140 +141 @@ Error returned: - * **Resolution** : Add the SAP HANA system to SAP HANA Studio and select multiple container mode, and then try to initiate your backup again. For more details, see [Invalid path selection for data backup using backint](https://launchpad.support.sap.com/#/notes/2803753) (portal access required). + * **Resolution** : Add the SAP HANA system to SAP HANA Studio and select multiple container mode, and then try to initiate your backup again. For more details, see {https---launchpad-support-sap-com---notes-2803753}[Invalid path selection for data backup using backint] (portal access required). @@ -145 +146 @@ Error returned: -###### Problem: Your backup fails and the following error appears in `aws-backint-agent.log`: +**Problem: Your backup fails and the following error appears in`aws-backint-agent.log`:** @@ -156 +157 @@ Error returned: -###### Problem: Any AWS Backint agent operation fails with one of the following errors, which appear in the `aws-backint-agent.log`: +**Problem: Any AWS Backint agent operation fails with one of the following errors, which appear in the`aws-backint-agent.log`:** @@ -158 +159 @@ Error returned: -`“Error creating upload id for bucket:<mys3bucket>" ` +`"`Error creating upload id for bucket:<mys3bucket>" ` @@ -166 +167 @@ or - * **Resolution** : AWS Backint agent requires an attached IAM role to your EC2 instance to access AWS resources for backup and restore operations. Attach an IAM role to your EC2 instance and attempt the operation again. For more information, see the [prerequisites](./aws-backint-agent-Amazon-S3.html#aws-backint-agent-s3-prerequisites) for installing AWS Backint agent. + * **Resolution** : AWS Backint agent requires an attached IAM role to your EC2 instance to access AWS resources for backup and restore operations. Attach an IAM role to your EC2 instance and attempt the operation again. For more information, see the [prerequisites](./aws-backint-agent-amazon-s3.html#aws-backint-agent-s3-prerequisites) for installing AWS Backint agent. @@ -185 +186 @@ For more information about using a proxy address in your SAP HANA environment, s -###### Problem: When you initiate a backup or restore, you get the following error in SAP HANA Studio or SAP HANA Cockpit: +**Problem: When you initiate a backup or restore, you get the following error in SAP HANA Studio or SAP HANA Cockpit:** @@ -196 +197 @@ For more information about using a proxy address in your SAP HANA environment, s -###### Problem: My backup is running too slowly and is taking a longer time to complete. +**Problem: My backup is running too slowly and is taking a longer time to complete.** @@ -205,6 +206 @@ For more information about using a proxy address in your SAP HANA environment, s -###### Problem: My backup and restore fails with one of the following errors: - - 1. `Backint exited with exit code 1 instead of 0. console output: Crashed during fetch and conversion read/write tcp 10.0.2.83:56192->52.216.88.123:443: use of closed network connection` - - 2. `Backint exited with exit code 1 instead of 0. console output: Crashed during fetch and conversion caused by: read tcp 10.0.2.83:54890->52.216.130.243:443: read: connection reset by peer` - +**Problem: My backup and restore fails with one of the following errors:** @@ -211,0 +208 @@ For more information about using a proxy address in your SAP HANA environment, s + 1. `Backint exited with exit code 1 instead of 0. console output: Crashed during fetch and conversion read/write tcp 10.0.2.83:56192→52.216.88.123:443: use of closed network connection` @@ -212,0 +210 @@ For more information about using a proxy address in your SAP HANA environment, s + 2. `Backint exited with exit code 1 instead of 0. console output: Crashed during fetch and conversion caused by: read tcp 10.0.2.83:54890→52.216.130.243:443: read: connection reset by peer` @@ -218 +216 @@ For more information about using a proxy address in your SAP HANA environment, s - 1. Update AWS Backint agent version to 2.0.4.768 or higher. These versions have improved resiliency to S3 connection timeouts. + 3. Update AWS Backint agent version to 2.0.4.768 or higher. These versions have improved resiliency to S3 connection timeouts. @@ -224 +222 @@ For more information about using a proxy address in your SAP HANA environment, s -For more information, see [Get the currently installed AWS Backint agent version](https://docs.aws.amazon.com/sap/latest/sap-hana/aws-backint-agent-s3-installing-configuring.html#aws-backint-agent-latest-version). +For more information, see {https---docs-aws-amazon-com-sap-latest-sap-hana-aws-backint-agent-s3-installing-configuring-html-aws-backint-agent-latest-version}[Get the currently installed AWS Backint agent version]. @@ -226 +224 @@ For more information, see [Get the currently installed AWS Backint agent version - 2. Use these steps if the issue persists – lower the following backup and restore parameters. + 4. Use these steps if the issue persists – lower the following backup and restore parameters. @@ -240 +238 @@ For more information, see [Get the currently installed AWS Backint agent version -_These values reduce concurrency and parallelism used by AWS Backint agent to achieve high performance during backup and restore. See[Modify AWS Backint agent configuration parameters](https://docs.aws.amazon.com/sap/latest/sap-hana/aws-backint-agent-s3-installing-configuring.html#aws-backint-agent-modifying-config) for the default values of the preceding parameters._ +_These values reduce concurrency and parallelism used by AWS Backint agent to achieve high performance during backup and restore. See{https---docs-aws-amazon-com-sap-latest-sap-hana-aws-backint-agent-s3-installing-configuring-html-aws-backint-agent-modifying-config}[Modify AWS Backint agent configuration parameters] for the default values of the preceding parameters._ @@ -242 +240 @@ _These values reduce concurrency and parallelism used by AWS Backint agent to ac - 3. Review network setup and configuration. + 5. Review network setup and configuration. @@ -244 +242 @@ _These values reduce concurrency and parallelism used by AWS Backint agent to ac - 4. Perform trace route to see if Amazon S3 traffic goes through firewall package scanners or any other software that could significantly increase network latency. + 6. Perform trace route to see if Amazon S3 traffic goes through firewall package scanners or any other software that could significantly increase network latency. @@ -249 +247 @@ _These values reduce concurrency and parallelism used by AWS Backint agent to ac -###### Problem: When you set the **S3ShortenBackupDestinationEnabled = ‘true’** parameter in the `aws-backint-agent-config.yaml`, a ‘No data backups found’ error is displayed when processing a database recovery. +**Problem: When you set the`S3ShortenBackupDestinationEnabled = ‘true’` parameter in the `aws-backint-agent-config.yaml`, a ‘No data backups found’ error is displayed when processing a database recovery.** @@ -251 +249 @@ _These values reduce concurrency and parallelism used by AWS Backint agent to ac - + @@ -253 +251 @@ _These values reduce concurrency and parallelism used by AWS Backint agent to ac - * **Root Cause** : AWS Backint agent searches for the logs and data backups only in the Amazon S3 path that's provided in the configuration file. Because the `S3ShortenBackupDestinationEnabled` parameter changes the Amazon S3 folder, it cannot find the backup. + * **Root Cause** : AWS Backint agent searches for the logs and data backups only in the Amazon S3 path that’s provided in the configuration file. Because the `S3ShortenBackupDestinationEnabled` parameter changes the Amazon S3 folder, it cannot find the backup. @@ -255 +253 @@ _These values reduce concurrency and parallelism used by AWS Backint agent to ac - * **Resolution** : You can either change the `S3ShortenBackupDestinationEnabled` parameter to `false` and run the restore, or you can move the previous backups and the SAP HANA backup catalog to the new S3 location. For more details, see [Configure AWS Backint agent to use shorter Amazon S3 paths](./aws-backint-agent-s3-installing-configuring.html#configure-aws-backint-agent-to-use-shorter-Amazon-S3-paths). + * **Resolution** : You can either change the `S3ShortenBackupDestinationEnabled` parameter to `false` and run the restore, or you can move the previous backups and the SAP HANA backup catalog to the new S3 location. For more details, see [Configure AWS Backint agent to use shorter Amazon S3 paths](./aws-backint-agent-s3-installing-configuring.html#configure-aws-backint-agent-to-use-shorter-amazon-s3-paths). @@ -260 +258 @@ _These values reduce concurrency and parallelism used by AWS Backint agent to ac -###### Problem: When processing a database recovery, a 'No data backups found' error is displayed and the agent log shows, 'The operation is not valid for the objects' access tier'. +**Problem: When processing a database recovery, a 'No data backups found' error is displayed and the agent log shows, 'The operation is not valid for the objects' access tier'.** @@ -264 +262 @@ _These values reduce concurrency and parallelism used by AWS Backint agent to ac - * **Root Cause** : With the **S3StorageClass = ‘INTELLIGENT_TIERING’** parameter set in the `aws-backint-agent-config.yaml`, the objects have moved to archival storage tiers. AWS Backint agent does not support recovery from archival tiers. + * **Root Cause** : With the *S3StorageClass = "INTELLIGENT_TIERING" * parameter set in the `aws-backint-agent-config.yaml`, the objects have moved to archival storage tiers. AWS Backint agent does not support recovery from archival tiers. @@ -271 +269 @@ _These values reduce concurrency and parallelism used by AWS Backint agent to ac -###### Problem: Backup request initiated by IAM doesn't have access to your Amazon S3 bucket. +**Problem: Backup request initiated by IAM doesn’t have access to your Amazon S3 bucket.** @@ -278 +276 @@ Error returned: - * **Root Cause** : Credentials for internal tasks are configured in the `./aws` folder which is picked by default instead of the configured IAM role for initiating a backup request. + * **Root Cause** : Credentials for internal tasks are configured in the `–0—/aws` folder which is picked by default instead of the configured IAM role for initiating a backup request. @@ -295 +293 @@ For more information, see [Configuring the AWS SDK for Go](https://docs.aws.amaz -###### Problem: "/bin/sh: error importing function definition for `which'" when performing backup and restore with AWS Backint agent. +**Problem: "/bin/sh: error importing function definition for `which'" when performing backup and restore with AWS Backint agent.** @@ -318 +313 @@ Based on your business requirements, use one of the following resolutions. - 2. _User-level_ : Add `unset -f which` to the user's `.bashrc` file. Verify if this is a scalable resolution for you. + 2. _User-level_ : Add `unset -f which` to the user’s `–0—bashrc` file. Verify if this is a scalable resolution for you. @@ -331 +326 @@ The system-level fix is a persistent solution that survives package updates to t -###### Problem: You deleted your SAP HANA backup from the SAP HANA backup console (SAP HANA Studio or SAP HANA Cockpit) but the deleted backup files still appear in the Amazon S3 folder. +**Problem: You deleted your SAP HANA backup from the SAP HANA backup console (SAP HANA Studio or SAP HANA Cockpit) but the deleted backup files still appear in the Amazon S3 folder.**