AWS lambda documentation change
Summary
Added troubleshooting documentation for S3 file system mounting errors in Lambda functions, including three new error types and their resolutions
Security assessment
This change adds documentation for new S3 file system mounting errors in Lambda. While it mentions checking permissions and security group configurations, these are standard troubleshooting steps for connectivity issues rather than addressing a specific security vulnerability. The change appears to be routine documentation expansion for a new feature (S3 file system support in Lambda).
Diff
diff --git a/lambda/latest/dg/troubleshooting-invocation.md b/lambda/latest/dg/troubleshooting-invocation.md index 3e082f246..3e1aafdaa 100644 --- a//lambda/latest/dg/troubleshooting-invocation.md +++ b//lambda/latest/dg/troubleshooting-invocation.md @@ -5 +5 @@ -Lambda: Function times out during Init phase (Sandbox.Timedout)IAM: lambda:InvokeFunction not authorizedLambda: Couldn't find valid bootstrap (Runtime.InvalidEntrypoint)Lambda: Operation cannot be performed ResourceConflictExceptionLambda: Function is stuck in PendingLambda: One function is using all concurrencyGeneral: Cannot invoke function with other accounts or servicesGeneral: Function invocation is loopingLambda: Alias routing with provisioned concurrencyLambda: Cold starts with provisioned concurrencyLambda: Cold starts with new versionsLambda: Unexpected Node.js exit in runtime (Runtime.NodejsExit)EFS: Function could not mount the EFS file systemEFS: Function could not connect to the EFS file systemEFS: Function could not mount the EFS file system due to timeoutLambda: Lambda detected an IO process that was taking too longContainer: CodeArtifactUserException errorsContainer: InvalidEntrypoint errors +Lambda: Function times out during Init phase (Sandbox.Timedout)IAM: lambda:InvokeFunction not authorizedLambda: Couldn't find valid bootstrap (Runtime.InvalidEntrypoint)Lambda: Operation cannot be performed ResourceConflictExceptionLambda: Function is stuck in PendingLambda: One function is using all concurrencyGeneral: Cannot invoke function with other accounts or servicesGeneral: Function invocation is loopingLambda: Alias routing with provisioned concurrencyLambda: Cold starts with provisioned concurrencyLambda: Cold starts with new versionsLambda: Unexpected Node.js exit in runtime (Runtime.NodejsExit)EFS: Function could not mount the EFS file systemEFS: Function could not connect to the EFS file systemEFS: Function could not mount the EFS file system due to timeoutS3 Files: Function could not mount the S3 file systemS3 Files: Function could not connect to the S3 file systemS3 Files: Function could not mount the S3 file system due to timeoutLambda: Lambda detected an IO process that was taking too longContainer: CodeArtifactUserException errorsContainer: InvalidEntrypoint errors @@ -46,0 +47,6 @@ For a list of error types that the `Invoke` operation can return, see [Invoke](h + * S3 Files: Function could not mount the S3 file system + + * S3 Files: Function could not connect to the S3 file system + + * S3 Files: Function could not mount the S3 file system due to timeout + @@ -196 +202 @@ For more information about Node.js exit codes and process termination, see the [ -The mount request to the function's [file system](./configuration-filesystem.html) was rejected. Check the function's permissions, and confirm that its file system and access point exist and are ready for use. +The mount request to the function's file system was rejected. Check the function's permissions, and confirm that its file system and access point exist and are ready for use. @@ -202 +208 @@ The mount request to the function's [file system](./configuration-filesystem.htm -The function couldn't establish a connection to the function's [file system](./configuration-filesystem.html) with the NFS protocol (TCP port 2049). Check the [security group and routing configuration](https://docs.aws.amazon.com/efs/latest/ug/network-access.html) for the VPC's subnets. +The function couldn't establish a connection to the function's file system with the NFS protocol (TCP port 2049). Check the [security group and routing configuration](https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-files-prereq-policies.html) for the VPC's subnets. @@ -210 +216,21 @@ If you get these errors after updating your function's VPC configuration setting -The function could connect to the function's [file system](./configuration-filesystem.html), but the mount operation timed out. Try again after a short time and consider limiting the function's [concurrency](./configuration-concurrency.html) to reduce load on the file system. +The function could connect to the function's file system, but the mount operation timed out. Try again after a short time and consider limiting the function's [concurrency](./configuration-concurrency.html) to reduce load on the file system. + +## S3 Files: Function could not mount the S3 file system + +**Error:** _S3FilesMountFailureException: The function could not mount the Amazon S3 file system with access point arn:aws:s3files:us-east-2:123456789012:access-point/fsap-123456789abcde._ + +The mount request to the function's file system was rejected. Check the function's permissions, and confirm that its file system and access point exist and are ready for use. + +## S3 Files: Function could not connect to the S3 file system + +**Error:** _S3FilesMountConnectivityException: The function couldn't connect to the Amazon S3 file system with access point arn:aws:s3files:us-east-2:123456789012:access-point/fsap-123456789abcde. Check your network configuration and try again._ + +The function couldn't establish a connection to the function's file system with the NFS protocol (TCP port 2049). Check the [security group and routing configuration](https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-files-prereq-policies.html) for the VPC's subnets. + +If you get these errors after updating your function's VPC configuration settings, try unmounting and remounting the file system. + +## S3 Files: Function could not mount the S3 file system due to timeout + +**Error:** _S3FilesMountTimeoutException: The function could not mount the S3 file system with access point{arn:aws:s3files:us-east-2:123456789012:access-point/fsap-123456789abcde} due to mount time out._ + +The function could connect to the function's file system, but the mount operation timed out. Try again after a short time and consider limiting the function's [concurrency](./configuration-concurrency.html) to reduce load on the file system.