Configuring Amazon Lambda functions

You can find an overview of how to configure your Lambda function using the console and Amazon CLI.

You can make your function code portable and keep secrets out of your code by storing them in your function's configuration by using environment variables.

You create a layer manage your function's dependencies independently and keep your development package small.

You can use your Lambda function with Amazon resources in an Amazon VPC. Connecting your function to a VPC lets you access resources in a private subnet such as relational databases and caches.

You can use an interface VPC endpoint to invoke your Lambda functions without crossing the public internet.

You can use your Lambda function to mount a Amazon EFS to a local directory. A file system allows your function code to access and modify shared resources safely and at high concurrency.

You can configure your clients to invoke a specific Lambda function version by using an alias, instead of updating the client.

By publishing a version of your function, you can store your code and configuration as a separate resource that cannot be changed.

You can configure your Lambda function URLs to stream response payloads back to clients. Response streaming can benefit latency sensitive applications by improving time to first byte (TTFB) performance. This is because you can send partial responses back to the client as they become available. Additionally, you can use response streaming to build functions that return larger payloads.