PAS-C01 · Question #66
An SAP engineer is configuring AWS Backint Agent for SAP HANA (AWS Backint agent) for an SAP HANA database that is running on an Amazon EC2 instance. After the configuration, the backups fail…
The correct answer is A. Update the EC2 role permissions to allow S3 bucket access. B. Verify that the configuration file has the correct formatting of the S3BucketOwnerAccountID. AccessDenied errors from AWS Backint Agent indicate that the IAM identity being used lacks sufficient permissions to access the target S3 bucket. Updating the EC2 IAM role permissions to allow the necessary S3 actions (s3:PutObject, s3:GetObject, s3:ListBucket, etc.) on the…
Question
An SAP engineer is configuring AWS Backint Agent for SAP HANA (AWS Backint agent) for an SAP HANA database that is running on an Amazon EC2 instance. After the configuration, the backups fail. During investigation, the SAP engineer notices that the AWS Backint agent logs contain numerous AccessDenied messages. Which actions should the SAP engineer take to resolve this issue? (Choose two.)
Options
- AUpdate the EC2 role permissions to allow S3 bucket access.
- BVerify that the configuration file has the correct formatting of the S3BucketOwnerAccountID.
- CInstall AWS Systems Manager Agent (SSM Agent) correctly by using the sudo command.
- DInstall the correct version of Python for AWS Backint agent.
- EAdd the execute permission to the AWS Backint agent binary.
How the community answered
(39 responses)- A82% (32)
- C3% (1)
- D5% (2)
- E10% (4)
Explanation
AccessDenied errors from AWS Backint Agent indicate that the IAM identity being used lacks sufficient permissions to access the target S3 bucket. Updating the EC2 IAM role permissions to allow the necessary S3 actions (s3:PutObject, s3:GetObject, s3:ListBucket, etc.) on the target bucket (A) directly resolves the permissions gap. Additionally, an incorrectly formatted S3BucketOwnerAccountID in the Backint configuration file (B) can cause bucket ownership validation failures, which also manifest as AccessDenied errors - particularly when cross-account S3 bucket ownership is enforced. Installing SSM Agent (C) relates to credential fetching issues, not AccessDenied. Python version (D) and execute permissions on the binary (E) would prevent the agent from running at all, not cause AccessDenied log entries.
Topics
Community Discussion
No community discussion yet for this question.