Forum Discussion
S3 Copy Data Unable to View Directory
- 1 year ago
It has not resolved it. I am going to just utilize spark scripts to read from the S3 shortcut instead and write to my OneLake.
Hi RLouis24 ,
Thank you for using Microsoft Community Forum.
Based on the TLS error you're encountering during the Copy Data activity “TrustFailure The remote certificate is invalid” the issue is due to Microsoft Fabric being unable to validate the SSL/TLS certificate presented by your S3 endpoint.
This commonly happens when:
- The certificate is self-signed or from an untrusted Certificate Authority (CA).
- There's a mismatch between the certificate domain and the endpoint URL.
- You're using a custom S3-compatible service with an unsupported certificate.
To resolve this, please ensure your S3 endpoint uses a valid SSL certificate from a trusted CA, and that the endpoint domain matches the certificate. If you’re behind a firewall or using SSL inspection, verify that no intermediary certificates are causing the trust issue.
As a temporary workaround, you can manually enter the full file path in the Copy Data activity instead of using the browse option.
For more guidance, refer to the following documentation : setting up Amazon S3 connections.
I hope this will reslove your issue, if you need any further assistance, feel free to reach out.
If this post helps, then please give us Kudos and consider Accept it as a solution to help the other members find it more quickly.
Thankyou.
- Anonymous1 year agoNot applicable
Hi RLouis24 ,
May I ask if you have resolved this issue? If so, please mark the helpful reply and accept it as the solution. This will be helpful for other community members who have similar problems to solve it faster.
Thank you.
- RLouis241 year agoNew Member
Good Morning, no this did not solve the issue. Thank you for the effort though!
- Anonymous1 year agoNot applicable
Hi RLouis24 ,
Thanks for the update. Since the connection works for shortcuts but fails during Copy Data browsing, it indicates stricter SSL validation is enforced in the Copy Data UI.
This error typically occurs if:
-
The S3 endpoint uses a self-signed or untrusted SSL certificate.
-
The certificate domain doesn't exactly match the endpoint URL.
-
A custom S3-compatible service is being used.
Could you confirm:
-
Are you using standard AWS S3 or a custom endpoint?
-
Is the certificate from a trusted CA and does it match the endpoint domain?
In the meantime, try entering the full S3 path manually in the Copy Data activity this often bypasses the TLS check in the UI.
Thank you.
-