unable to upload zip folder from s3 to aws lambda

The issue you're facing is related to the size limit for Lambda deployment packages. While AWS Lambda allows deployment packages up to 250 MB when uploaded through AWS CLI or SDKs, there's a smaller limit of 50 MB when uploading directly through the AWS Management Console.

In your case, even though your zip file in S3 is 111.9 MB, which is below the 250 MB limit, it's still above the 50 MB limit for direct uploads through the console. This explains the "RequestEntityTooLargeException" error you're seeing.

To resolve this issue, you have a few options:

1. Use the AWS CLI or SDK to deploy your Lambda function instead of the console. This will allow you to use the full 250 MB limit.

2. Optimize your deployment package to reduce its size. This could involve removing unnecessary dependencies or files.

3. Consider using Lambda Layers to separate some of your dependencies from your main function code. This can help reduce the size of your main deployment package.

4. If your package size cannot be reduced below 250 MB, you should consider using container images for your Lambda function. Lambda supports container images up to 10 GB in size, which would easily accommodate your current package.

Remember, when using S3 to store your deployment package, make sure the S3 bucket is in the same region as your Lambda function to avoid any potential issues.

If you continue to face issues or if your package size grows beyond these limits, you might want to explore using container images for your Lambda function, which allows for much larger deployments up to 10 GB.
Sources
Troubleshoot deployment issues in Lambda - AWS Lambda
Not able to use deepeval on Lambda | AWS re:Post
Lambda Package Exceeds 60MB: Solutions for Large Dependencies? | AWS re:Post