Not able to use deepeval on Lambda

If the issue is in Lambda storage size, it may be improved by applying for a cap relaxation. The default limit is 75 GB, but it can be increased to Terabytes.

https://docs.aws.amazon.com/lambda/latest/dg/gettingstarted-limits.html

The 413 error you're encountering during upload typically indicates that the request entity is too large, which in the context of AWS Cloud9 to AWS Lambda deployment, suggests you're hitting a limit on the deployment package size rather than the total storage capacity of Lambda functions.

AWS Lambda has specific limits for the size of the deployment package when uploading directly through the AWS Management Console, AWS CLI, or AWS SDKs. As of my last update, these limits are:

• 50 MB for direct upload through the AWS Management Console.
• 250 MB for zipped files when uploaded through AWS CLI or AWS SDKs.
• 10 GB for container images.

The 75 GB limit you mentioned refers to the total storage space for all Lambda functions and layers in your AWS account, not for individual Lambda functions or deployment packages.

Given these constraints, here are a few strategies you might consider to work around the size limitations:

• Upload your package to an S3 bucket and link it in Lambda to handle packages up to 250 MB (zipped).
• Remove unnecessary files or dependencies to reduce the package size.
• Request a quota increase for total Lambda storage from AWS Support if consistently hitting limits.
• Use Lambda layers for common dependencies, mindful of individual layer size limits.
• Consider packaging your Lambda function as a container image for up to 10 GB size.

Lambda, when using the zip packaging option, has a package size limit of 250MB unzipped. If your package is larger, you can use a container image to package yout function, which is limited to 10 GB.