Skip to content

Unable to upload files to my S3 management console

0

Issue: I am encountering a "Networking Error" when attempting to upload files to my S3 bucket. The error occurs specifically when I try to upload files larger than 200 KB. Smaller files are uploading successfully.

Solutions I've Already Tried:

  • Clearing Browser Cache: I’ve cleared my browser's cache and tried again — no success.
  • Incognito Mode: I’ve tried using the S3 console in incognito mode.
  • Different Network/Machine: I’ve tested on a different network and machine. However, since I’m using a personal laptop with no firewalls or proxies on a home network, this doesn't seem to be the issue.
  • Different Browsers: I’ve tested uploading through different browsers, including Chrome, Safari, and Firefox.

Additional Information:

  1. The S3 bucket is set to public, and smaller files are uploading without issue, so access does not appear to be the problem.
  2. Versioning is not enabled on the bucket.
  3. My internet speed is fast (100 Mbps+), so it’s not a network issue.
  4. I also tried uploading using the AWS CLI, but encountered a different error (SSL/timeout).
  5. This issue started after upgrading my laptop from a MacBook Air M2 to a MacBook Air M4. Everything else (Wi-Fi, bucket configuration, code) has remained the same, and the uploads were working fine on my old laptop.

Question: Could there be an issue with AWS, or am I possibly missing something in my setup? I’m at a loss as to why this is suddenly happening after the laptop upgrade.

  • Hi there, did you ever find a solution to this problem? I am having the exact same issue on my Mac. I simply can't upload to S3 - either via API, CLI, or the console. tiny files are fine but larger fails fail, except for 1/10 times where it succeeds.

2 Answers
0

Since you mentioned SSL issues, is your laptop where you trying the upload behind a firewall. It could be the firewall is causing the upload error. If possible, try disabling firewall and retry

EXPERT
answered a year ago
0

Based on the information provided, it seems that the issue you're experiencing is not likely related to AWS itself, but rather to your local setup or network configuration. Since the problem started after upgrading your laptop, it's possible that there's a compatibility issue or a configuration change that's affecting your ability to upload larger files.

Here are a few suggestions to troubleshoot and potentially resolve the issue:

  1. Check your AWS CLI version and update it if necessary. The new laptop might have a different version installed, which could be causing the SSL/timeout error you encountered.

  2. Verify that your laptop's date and time settings are correct and synced. Incorrect time settings can sometimes cause SSL issues.

  3. Try adjusting the multipart upload settings in your AWS CLI configuration. You can modify parameters like multipart_threshold and multipart_chunksize to see if it helps with larger file uploads.

  4. Enable versioning on your S3 bucket. While this may not directly solve the upload issue, it can help you track changes and potentially identify any problems with object versions.

  5. Check if there are any security software or settings on your new laptop that might be interfering with the upload process for larger files.

  6. Test uploading through a VPN to rule out any potential ISP or routing issues that might have coincidentally started after your laptop upgrade.

  7. If possible, try uploading from your old laptop again to confirm if the issue is indeed related to the new hardware.

If none of these solutions work, you may want to contact AWS support for further assistance, as there could be an underlying issue that's not immediately apparent. They can help you investigate any potential account-specific or regional problems that might be affecting your uploads.
Sources
Unable to upload to S3 bucket | AWS re:Post
Failed to upload file to s3 | AWS re:Post

answered a year ago
EXPERT
reviewed a year ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.