Binary Multipart Uploads Don't Work about zappa HOT 9 CLOSED

File uploads appear to be ballooning up in size across the APIGW:

176372: local app
314044: Zappa app

Investigating..

from zappa.

I don't know. I suspect it has something to do with byte encodings, but it looks like the file is too big by the time it even makes it through the APIGW, before we even touch it.

from zappa.

Bugger. This is an API Gateway problem - B64 encoding image uploads is still necessary for the time being: https://forums.aws.amazon.com/thread.jspa?threadID=231371&tstart=0

from zappa.

@Miserlou we have implemented django admin file widget to upload files in django zappa admin panels. I hope this can help. check out: https://github.com/anush0247/zappa-file-widget

from zappa.

Woah, that's awesome!

from zappa.

Related: #481

from zappa.

Binary downloads work, could be interesting to revisit binary uploads now.

from zappa.

Binary uploads work now.

from zappa.

I have deployed my django project to s3 bucket about 3 weeks ago, and find out there was an issue about binary file uploads.
After seeing this issue closed, I updated zappa and tried to update but get the warning below:

Warning! Couldn't get function treasure-django-dev in us-east-1 - have you deployed yet?

My command:
zappa update dev

My zappa_settings.json:

{
    "dev": {
        "django_settings": "treasure.settings",
        "s3_bucket": "free-gifts-zappa"
    }
}

from zappa.