When pushing the package to Lambda, the console returns the following error:An error occurred (RequestEntityTooLargeException) when calling the UpdateFunctionCode operationWhich solutions can the developer use to publish the code?
(Choose two.)
Upload the package to Amazon S3. Use the Functions page on the Lambda console to upload the package from the S3 location.
Create an AWS Support ticket to increase the maximum package size.
Use the update-function-code AWS CLI command. Pass the –publish parameter.
Repackage the Lambda function as a Docker container image. Upload the image to Amazon Elastic Container Registry (Amazon ECR). Create a new Lambda function by using the Lambda console. Reference the image that is deployed to Amazon ECR.
Sign the .zip file digitally. Create a new Lambda function by using the Lambda console. Update the configuration of the new Lambda function to include the Amazon Resource Name (ARN) of the code signing configuration.
Explanations:
Uploading the .zip file to Amazon S3 and using the Lambda console to reference the S3 location allows you to bypass the size limit on direct uploads from the console. Lambda can accept larger files this way.
AWS does not allow users to request an increase in the maximum size limit for Lambda function packages. The size limit is fixed.
The–publishparameter in the AWS CLI command is used to publish a new version of the function, but it does not address the issue of the file size exceeding the limit. The size limit remains the same.
Lambda functions can be packaged as Docker container images. By deploying the container to Amazon ECR, the function can exceed the .zip file size limits and be referenced in Lambda.
Code signing for Lambda functions does not resolve the size limitation issue. The code signing configuration helps ensure the integrity and authenticity of the code but does not affect the file size constraints.
From my point of view, the answer is:
Upload the package to Amazon S3. Use the Functions page on the Lambda console to upload the package from the S3 location.