A company needs to create an AWS Lambda function that will run in a VPC in the company's primary AWS account. The Lambda function needs to access files that the company stores in an Amazon Elastic…

Question

Options

• ACreate a new EFS file system in the primary account. Use AWS DataSync to copy the contents of
• BCreate a VPC peering connection between the VPCs that are in the primary account and the
• CCreate a second Lambda function in the secondary account that has a mount that is configured
• DMove the contents of the file system to a Lambda layer. Configure the Lambda layer's

• A
  13% (3)
• B
  58% (14)
• C
  4% (1)
• D
  25% (6)

Explanation

Amazon EFS is a regional, elastic file system that "scales to petabytes" and can be accessed from "thousands of compute instances" concurrently. You can mount EFS across VPCs and across AWS accounts by providing network connectivity (e.g., VPC peering) to the EFS mount targets and allowing NFS (TCP 2049) in the mount target security group, optionally using EFS access points and a file system policy for cross-account access control. VPC peering has no hourly charge and minimal operational overhead, and EFS automatically scales as files are added-meeting the scalability and cost goals. Option A duplicates data, incurs DataSync and extra storage costs, and adds sync lag. Option C adds an extra Lambda hop and complexity without exposing a shared filesystem to the primary function. Option D is impractical: Lambda layers are immutable artifacts with tight size limits (up to 50 MB compressed/250 MB uncompressed) and are not suited for dynamic, growing file sets.

No community discussion yet for this question.