Symptom
When connecting the SAP Datasphere to a third-party application with AWS S3 or Amazon AWS S3 directly, the following error appears:
- Error for connection "<CONNECTION NAME>":
Data Flows: Cause: Possible causes of error: Detailed error message (access denied (service: amazon s3; status code: 403; error code: accessdenied; request id:XXXXXXX; s3 extended request id: XXXXXXXXX=; proxy: null))
Replication Flows: Cause: Possible causes of error: Detailed error message (access denied (service: amazon s3; status code: 403; error code: accessdenied; request id: XXXXXXXX; s3 extended request id: XXXXXXXX=; proxy: null))
- Connection "<CONNECTION NAME>" couldn't be established.
- Data flows can't be used because of errors in the connection.
- Replication flows can't be used because of errors in the connection
- Remote tables are not supported
Data flows: Cause: Possible causes of errors: Detailed error message (forbidden)
Replication flows: Cause: Possible causes of error: Detailed error message (forbidden)
Environment
SAP Datasphere
Cause
The AWS S3 server did not authorize access due to some erroneous configuration set in the SAP Datasphere.
Resolution
This error usually occurs when some configuration is wrong. Check the SAP Help Amazon Simple Storage Service Connections and review the configuration, especially the endpoint (the endpoint should not be only "s3.amazonaws.com" with the root path empty). If the problem persists, use the Amazon S3 guide to find out more about the reason for the 403 error on the AWS S3 side.
See Also
Data Integration between SAP Data Warehouse Cloud and Amazon S3 to Blend Business Data with External Data
Access Denied (403 Forbidden) errors in Amazon S3
Amazon Simple Storage Service Connections
3456649 - FAQ: Datasphere simple questions
SAP Datasphere - Data Provisioning Agent Guided Answer
SAP Datasphere Troubleshooting Help
Keywords
Amazon, S3, Connection, HTTP, 403, Forbidden, issue, test, ping, third, party, 3rd, DS, Datasphere , KBA , DS-DI-CON , Connections , Problem