AWS lambda documentation change
Summary
Completely restructured documentation from Amazon EFS-specific content to a general overview of file system types (Amazon EFS and Amazon S3 Files), removing detailed EFS configuration instructions and replacing them with links to separate documentation pages
Security assessment
This is a documentation reorganization that removes detailed security configuration information (IAM permissions, access point security settings, VPC networking requirements) rather than addressing a specific security vulnerability. The change appears to be structural - moving EFS-specific content to a dedicated page and introducing new S3 Files documentation. No evidence of security incident remediation or vulnerability disclosure in the diff.
Diff
diff --git a/lambda/latest/dg/configuration-filesystem.md b/lambda/latest/dg/configuration-filesystem.md index 7938cfc63..d41c1b1be 100644 --- a//lambda/latest/dg/configuration-filesystem.md +++ b//lambda/latest/dg/configuration-filesystem.md @@ -5,2 +4,0 @@ -Supported RegionsExecution role and user permissionsConfiguring a file system and access pointConnecting to a file system (console) - @@ -9,48 +7 @@ Supported RegionsExecution role and user permissionsConfiguring a file system an -You can configure a function to mount an Amazon Elastic File System (Amazon EFS) file system to a local directory. With Amazon EFS, your function code can access and modify shared resources safely and at high concurrency. - -## Supported Regions - -Amazon EFS for Lambda is available in all [commercial Regions](https://docs.aws.amazon.com/general/latest/gr/glos-chap.html#region) except Asia Pacific (New Zealand), Asia Pacific (Taipei), Asia Pacific (Malaysia), Mexico (Central), Asia Pacific (Thailand), and Canada West (Calgary). - -###### Sections - - * Execution role and user permissions - - * Configuring a file system and access point - - * Connecting to a file system (console) - - - - -## Execution role and user permissions - -If the file system doesn't have a user-configured AWS Identity and Access Management (IAM) policy, EFS uses a default policy that grants full access to any client that can connect to the file system using a file system mount target. If the file system has a user-configured IAM policy, your function's execution role must have the correct `elasticfilesystem` permissions. - -###### Execution role permissions - - * **elasticfilesystem:ClientMount** - - * **elasticfilesystem:ClientWrite (not required for read-only connections)** - - - - -These permissions are included in the **AmazonElasticFileSystemClientReadWriteAccess** managed policy. Additionally, your execution role must have the [permissions required to connect to the file system's VPC](./configuration-vpc.html#configuration-vpc-permissions). - -When you configure a file system, Lambda uses your permissions to verify mount targets. To configure a function to connect to a file system, your user needs the following permissions: - -###### User permissions - - * **elasticfilesystem:DescribeMountTargets** - - - - -## Configuring a file system and access point - -Create a file system in Amazon EFS with a mount target in every Availability Zone that your function connects to. For performance and resilience, use at least two Availability Zones. For example, in a simple configuration you could have a VPC with two private subnets in separate Availability Zones. The function connects to both subnets and a mount target is available in each. Ensure that NFS traffic (port 2049) is allowed by the security groups used by the function and mount targets. - -###### Note - -When you create a file system, you choose a performance mode that can't be changed later. **General purpose** mode has lower latency, and **Max I/O** mode supports a higher maximum throughput and IOPS. For help choosing, see [Amazon EFS performance](https://docs.aws.amazon.com/efs/latest/ug/performance.html) in the _Amazon Elastic File System User Guide_. +You can configure a Lambda function to mount a file system to a local directory. Lambda supports the following file system types: @@ -58 +9 @@ When you create a file system, you choose a performance mode that can't be chang -An access point connects each instance of the function to the right mount target for the Availability Zone it connects to. For best performance, create an access point with a non-root path, and limit the number of files that you create in each directory. The following example creates a directory named `my-function` on the file system and sets the owner ID to 1001 with standard directory permissions (755). + * **[Amazon Elastic File System (Amazon EFS)](./configuration-filesystem-efs.html)** – Serverless file system that scales automatically with your workloads. @@ -60 +11 @@ An access point connects each instance of the function to the right mount target -###### Example access point configuration + * **[Amazon S3 Files](./configuration-filesystem-s3files.html)** – Serverless file system for mounting your Amazon S3 bucket. Amazon S3 Files provides access to your Amazon S3 objects as files using standard file system operations such as read and write on the local mount path. @@ -62 +12,0 @@ An access point connects each instance of the function to the right mount target - * **Name** – `files` @@ -64 +13,0 @@ An access point connects each instance of the function to the right mount target - * **User ID** – `1001` @@ -66,27 +14,0 @@ An access point connects each instance of the function to the right mount target - * **Group ID** – `1001` - - * **Path** – `/my-function` - - * **Permissions** – `755` - - * **Owner user ID** – `1001` - - * **Group user ID** – `1001` - - - - -When a function uses the access point, it is given user ID 1001 and has full access to the directory. - -For more information, see the following topics in the _Amazon Elastic File System User Guide_ : - - * [Creating resources for Amazon EFS](https://docs.aws.amazon.com/efs/latest/ug/creating-using.html) - - * [Working with users, groups, and permissions](https://docs.aws.amazon.com/efs/latest/ug/accessing-fs-nfs-permissions.html) - - - - -## Connecting to a file system (console) - -A function connects to a file system over the local network in a VPC. The subnets that your function connects to can be the same subnets that contain mount points for your file system, or subnets in the same Availability Zone that can route NFS traffic (port 2049) to the file system. @@ -96,26 +18 @@ A function connects to a file system over the local network in a VPC. The subnet -If your function is not already connected to a VPC, see [Giving Lambda functions access to resources in an Amazon VPC](./configuration-vpc.html). - -###### To configure file system access - - 1. Open the [Functions page](https://console.aws.amazon.com/lambda/home#/functions) of the Lambda console. - - 2. Choose a function. - - 3. Choose **Configuration** and then choose **File systems**. - - 4. Under **File system** , choose **Add file system**. - - 5. Configure the following properties: - - * **EFS file system** – The access point for a file system in the same VPC. - - * **Local mount path** – The location where the file system is mounted on the Lambda function, starting with `/mnt/`. - - - - -###### Pricing - -Amazon EFS charges for storage and throughput, with rates that vary by storage class. For details, see [Amazon EFS pricing](https://aws.amazon.com/efs/pricing). - -Lambda charges for data transfer between VPCs. This only applies if your function's VPC is peered to another VPC with a file system. The rates are the same as for Amazon EC2 data transfer between VPCs in the same Region. For details, see [Lambda pricing](https://aws.amazon.com/lambda/pricing). +A Lambda function can use either Amazon EFS or Amazon S3 Files, but not both. If your function is already configured with one file system type, you must remove it before configuring the other. @@ -131 +28 @@ Inbound networking -Aliases +Amazon EFS