- Why 10MB?
This was determined after reviewing with customers at the time of launch and after load testing the service at various values.
And why can't we configure that limit?
We may add this as a future enhancement to the service, but likely only for customers who may want to limit the payload further.
A lot of api service provide to upload binary file that size are often over 10MB.
Scaling a service to support arbitrary file uploads was not our core mission. AWS already offers another service that does this quite well, Amazon S3. We recommend that customers that have needs for large file transfers consider using S3 as the upload target and use API Gateway/Lambda to trigger processing of the data.
How will the aws api gateway behave when a compressed payload of size less than 10mb limit passed to api gateway? Will it accept it? Suppose the uncompressed version of the payload is more than 10mb but the compressed version is less than 10mb, then when aws api gateway auto decompress it, will it reject the request stating "Error "413 Request entity too large".
Please help me in understaning this.
API Gateway Websockets size limit Feedbackasked 3 years ago
Recommendations for Amazon's API Gateway 10MB payload limitAccepted Answerasked 3 years ago
API Gateway Websocket - payload quotasasked 8 months ago
Lambda Authorizer Context Response Size LimitAccepted Answerasked 10 months ago
Api Gateway Payload size limit increaseasked 5 years ago
AWS API Gateway 413 Request Entity Too Large on response size (NOT request payload) greater than 10MBasked 3 months ago
Application Load Balancer payload limit?asked 2 months ago
Payload size limit on API GatewayAccepted Answerasked 6 years ago
REST API payload max size with compressionasked a month ago
AWS Lambda - Body Size is Too Large Error, but Body Size is Under Limitasked 2 years ago