新しいBoxサポートサイトへようこそ。 変更点の詳細はこちらをご確認ください .

Upload API limits and serverless environments

新規投稿

コメント

6件のコメント

  • 正式なコメント
    Alex Novotny

    Hi, 

    Thanks for reaching out. I will need to talk some folks internally and report back. Have you worked with anyone from Box in the past?

    Thanks, 

    Alex, Box Developer Advocate

    コメントアクション Permalink
  • Sand Box

    Hi,

    Thanks for getting back to us so quickly, we haven't worked with anyone from Box yet.

    0
    コメントアクション Permalink
  • jbesan

    Hi Sand Box

    I am the product manager for Uploads & Downloads.
    Thanks for your request and I don't think we have a workaround available today.

    We will evaluate if we can lower the minimum to 5MB to support this use-case but in the meantime have you reached out to AWS to see if they can support larger payload with Lambda?

    Jacques

    0
    コメントアクション Permalink
  • Sand Box

    Hi Jacques,

    We have reached out to AWS but the payload quota of 6MB cannot be changed, unfortunately. https://docs.aws.amazon.com/lambda/latest/dg/gettingstarted-limits.html

    When using API gateway with Lambda, the payload is base64 encoded, increasing the size by ~33%. This further lowers the limit from 6 to ~4.5MB. https://docs.aws.amazon.com/apigateway/latest/developerguide/api-gateway-payload-encodings.html


    This is the standard AWS approach to publish an API with Lambda functions. Would it be possible to lower the minimum to 4MB instead of 5MB?



    Thanks for your consideration,

    Team Apideck

    0
    コメントアクション Permalink
  • Sand Box

    Hi!

    Do you have an update on this? AWS can't raise this limit for us. 

    Thanks for your consideration,

    Team Apideck

    0
    コメントアクション Permalink
  • Ricardo Alves

    +1 on this. We also need it for our use case.

    0
    コメントアクション Permalink

サインインしてコメントを残してください。