- Newest
- Most votes
- Most comments
I tried debugging with openssl s_client -connect <bucket-name>.s3.amazonaws.com:443 -tls1_2
SSL handshake was okay and my IAM user has administrator privileges
Also since I get it in AWS Console, It has to do some issue with s3 only and probably not at my end
The error you're encountering suggests there's an SSL/TLS version mismatch between your client (Node.js) and the Amazon S3 service. This issue can occur due to several reasons:
-
Outdated OpenSSL version: Your Node.js installation might be using an older version of OpenSSL that doesn't support the TLS version required by S3.
-
Network interference: If you're accessing S3 through a corporate network, there might be firewall rules or proxy settings interfering with the SSL/TLS handshake.
-
S3 client library version: An outdated AWS SDK for JavaScript in Node.js might not support the latest TLS versions used by S3.
To resolve this issue, try the following steps:
-
Update Node.js to the latest stable version, which should include an up-to-date OpenSSL library.
-
Ensure you're using the latest version of the AWS SDK for JavaScript.
-
Check if you're behind a corporate firewall or proxy. If so, consult with your network administrator to ensure S3 endpoints are accessible and not subject to SSL inspection that might interfere with the connection.
-
Verify that your system's date and time are set correctly, as SSL/TLS handshakes can fail if the client's clock is significantly off.
-
If the issue persists, try using a different network connection (e.g., switch from Wi-Fi to a wired connection or use a different internet service) to rule out network-related problems.
-
For the AWS Console issues, try clearing your browser cache and cookies, or use a different browser to access the S3 console.
If none of these steps resolve the issue, you may need to contact AWS Support for further assistance, especially if the problem is affecting multiple S3 buckets in the AWS Console.
Sources
Problem AWS S3 access: Failed to receive handshake, SSL/TLS connection failed | AWS re:Post
AWS OpenSSL Error | AWS re:Post

hi, Since 8 out of 10 buckets are failing to load, and the other two are working, the issue is likely specific to the failing buckets' configurations or network settings.
I'd focus on SSL/TLS connectivity and IAM permissions for failing buckets. if you can check policy aws s3api get-bucket-policy --bucket <bucket-name>
also all buckets are in same region? aws configure set region <your-region>
Test SSL connectivity: openssl s_client -connect <bucket-name>.s3.amazonaws.com:443 -tls1_2
hope it will help to drill down the real cause. AWS Documentation:https://docs.aws.amazon.com/general/latest/gr/s3.html