AWS S3/Accelerated bucket upload fails ONLY for slow connection users

Question

We're enabling our users to upload videos onto our S3 bucket. It's been fitted with the "acceleration" option and using Multi-Part upload from our JS. However, we've noticed something very disturbing: We have thousands of successful uploads from countries where the Internet is fast.

However, virtually all slow connection users (who all happen to be from places the internet isn't famous for speed) fail to upload. Once they do begin to upload they get dozens these errors on their console and the upload gets stuck and fails.

Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://our-secret-bucket-xxxxxx.s3-accelerate.amazonaws.com/tyoeu/Abbey%…BAYmLRf4.YqtrWLwkD9uc5wGp0.rpyIV6xqDHxHqNaEsaxQTMAHs3g8DXdL3. (Reason: CORS request did not succeed).

The CORS setup for this bucket is as follows:

<?xml version="1.0" encoding="UTF-8"?>
<CORSConfiguration xmlns="http://s3.amazonaws.com/doc/2006-03-01/">
<CORSRule>
    <AllowedOrigin>*</AllowedOrigin>
    <AllowedMethod>PUT</AllowedMethod>
    <AllowedMethod>POST</AllowedMethod>
    <AllowedMethod>GET</AllowedMethod>
    <AllowedMethod>HEAD</AllowedMethod>
    <MaxAgeSeconds>43200</MaxAgeSeconds>
    <ExposeHeader>ETag</ExposeHeader>
    <AllowedHeader>*</AllowedHeader>
</CORSRule>
</CORSConfiguration>

We help the upload failed users manually by asking them to upload to dropbox and share a link with us -- but this is just another proof something is wrong -- if they can upload to Dropbox with their slow connections, why can't they upload to AWS/S3? This has been gnawing at our souls for quite some time now and we can't understand what's wrong.

Surely we're not the only company on planet Earth allowing folks from around the world to upload large files. Why are we failing with slow connection users?

I recommend that you open a ticket with AWS if you haven't already. — Greg
@JasonGenX, did you try to emulate behaviour on chrome by setting poor network profile? are you able to reproduce the issue that way? And if you do what do you see in the network tab? — Tarun Lalwani
Did you try to enable logs for your bucket? If you see connections and data flowing to your bucket from these places, then you may discard CORS problems. I have read sometimes browsers confuses issues with CORS matters. — Perimosh

ketcham ketcham · Accepted Answer · 2019-07-23T15:19:25

Seems like this may be a request timeout issue, have you tried changing your aws.config.httpOptions.timeout? This defaults to two minutes but you can completely remove the timeout by setting it to zero. More info on this can be found here.

Edited to fix broken link.

AWS S3/Accelerated bucket upload fails ONLY for slow connection users

2 Answers