Which solution will meet these requirements?
Save the library in Lambda layers. Attach the layers to all Lambda functions.
Save the library in Amazon S3. Download the library from Amazon S3 inside the Lambda function.
Save the library as a Lambda container image. Redeploy the Lambda functions with the new image.
Save the library in an Amazon Elastic File System (Amazon EFS) file system. Mount the EFS file system in all the Lambda functions.
Explanations:
Lambda layers are limited to 250 MB in size, which is much smaller than the required 15 GB library size.
While you can download the library from S3 inside the Lambda function, it would introduce latency, and storing a 15 GB library in S3 is inefficient for frequent access by Lambda functions.
Lambda container images can be used for larger libraries, but the size limit for container images is 10 GB, which is still smaller than the required 15 GB.
Amazon EFS can be mounted to Lambda functions, providing scalable storage. It supports large libraries and allows all Lambda functions to access the library concurrently.
I opine that the answer is:
Save the library in an Amazon Elastic File System (Amazon EFS) file system. Mount the EFS file system in all the Lambda functions.
I estimate that the answer is:
Save the library in an Amazon Elastic File System (Amazon EFS) file system. Mount the EFS file system in all the Lambda functions.