Which solution will provide the Lambda functions with access to the libraries and data?
Attach an Amazon Elastic Block Store (Amazon EBS) volume to the Lambda functions by using EBS Multi-Attach in the central VPC. Update the Lambda function execution roles to give the functions to access the EBS volume. Update the Lambda function code to reference the files in the EBS volume.
Compress the libraries and reference data in a Lambda /tmp folder. Update the Lambda function code to reference the files in the /tmp folder.
Set up an Amazon Elastic File System (Amazon EFS) file system with mount targets in the central VPConfigure the Lambda functions to mount the EFS file system. Update the Lambda function execution roles to give the functions to access the EFS file system.
Set up an Amazon FSx for Windows File Server file system with mount targets in the central VPC. Configure the Lambda functions to mount the Amazon FSx file system. Update the Lambda function execution roles to give the functions to access the Amazon FSx file system.
Explanations:
EBS volumes cannot be attached to Lambda functions. Lambda does not support block storage like EBS; instead, it requires file systems or other storage solutions.
The /tmp folder has a limited size (512 MB) and is ephemeral, which means it does not persist across function invocations. This option would not support independent updates by different teams.
Amazon EFS can be mounted to Lambda functions, allowing for shared access to libraries and data. EFS is designed for concurrent access and supports independent updates, making it suitable for this scenario.
While Amazon FSx can be used for file sharing, it is not optimized for Lambda functions. EFS is a better fit for this use case as it is specifically designed for serverless architectures.