AWS s3 openssl error in us-east-1

Question

In us-east-1 I am getting openssl errors

```
❯ aws  s3 ls test-random-buckeadsfdsfd --region us-west-2

An error occurred (NoSuchBucket) when calling the ListObjectsV2 operation: The specified bucket does not exist
❯ aws  s3 ls test-random-buckeadsfdsfd --region us-east-1
SSL validation failed for https://test-random-buckeadsfdsfd.s3.us-east-1.amazonaws.com/?list-type=2&prefix=&delimiter=%2F&encoding-type=url [SSL] record layer failure (_ssl.c:1010)
```

Openssl shows
```
40084DF901000000:error:0A0000C6:SSL routines:tls_get_more_records:packet length too long:ssl/record/methods/tls_common.c:663:
40084DF901000000:error:0A000139:SSL routines::record layer failure:ssl/record/rec_layer_s3.c:693:
```
this error also occurs on multiple devices and browsers

re:Post Agent · Answer

The error you're encountering appears to be related to SSL/TLS communication issues rather than a specific OpenSSL problem with Amazon S3 in the us-east-1 region. There are a few things to consider:

1. Bucket Existence: The first command you ran in us-west-2 correctly identified that the bucket doesn't exist. This is expected behavior for a non-existent bucket.

2. SSL/TLS Error: The error in us-east-1 is different and suggests an SSL/TLS problem. This could be due to various reasons:

- Network Issues: There might be network interference or a proxy causing problems with the SSL handshake.
   - SSL/TLS Version Mismatch: Your client might be trying to use an outdated or unsupported SSL/TLS version.
   - Certificate Issues: There could be problems with certificate validation on your end.

3. Multiple Devices: Since you mentioned this occurs on multiple devices and browsers, it's less likely to be a local configuration issue and more likely a network-wide problem or an issue with how your network is interacting with AWS services.

To troubleshoot this:

1. Check your network configuration, especially if you're behind a corporate firewall or using a VPN.
2. Ensure your AWS CLI and OpenSSL installations are up to date.
3. Try using the '--no-verify-ssl' option with your AWS CLI command to see if it bypasses the issue (note: this is not recommended for production use).
4. If possible, try the command from a different network to isolate whether it's a network-specific issue.

If the problem persists, you may need to contact AWS support for further assistance, as it could be related to how your network is routing requests to the S3 service in the us-east-1 region.  
**Sources**  
[AWS OpenSSL Error | AWS re:Post](https://repost.aws/questions/QUt9cAsz6JSu6fNMJG1bZ5ew/aws-openssl-error)  
[S3 Error download file SSE | AWS re:Post](https://repost.aws/questions/QUDjxuMGx-S2Ka4dlbNeJUKg/s3-error-download-file-sse)

AWS s3 openssl error in us-east-1

Relevant content