Application Load Balancer can now Invoke Lambda Functions to Serve HTTP(S) Requests
Application Load Balancers now support invoking Lambda functions to serve HTTP(S) requests. This enables users to access serverless applications from any HTTP client, including web browsers. With the Application Load Balancers' support for content-based routing rules, you can also route requests to different Lambda functions based on the request content. Prior to this launch, you could only use EC2 instances, containers, and on-premises servers, as targets for Application Load Balancers, and you needed other proxy solutions to invoke Lambda functions over HTTP(S). You can now use an Application Load Balancer as a common HTTP endpoint to simplify operations and monitoring for applications that use servers and serverless computing.
You can register Lambda functions as targets for an Application Load Balancer using the Elastic Load Balancing Console, AWS SDK, or AWS Command Line Interface (CLI). You can also configure an Application Load Balancer as a trigger for a Lambda functions from the AWS Lambda console in few clicks.
Usual AWS Lambda and Application Load Balancer charges apply. Please visit the Application Load Balancer pricing page for more information.
Support for Lambda invocation via Application Load Balancer is available for existing and new Application Load Balancers in US East (N. Virginia), US East (Ohio), US West (Northern California), US West (Oregon), Asia Pacific (Mumbai), Asia Pacific (Seoul), Asia Pacific (Singapore), Asia Pacific (Sydney), Asia Pacific (Tokyo), Canada ( Central), EU (Frankfurt), EU (Ireland), EU (London), EU (Paris), South America (São Paulo), and GovCloud (US-West) AWS Regions.
To learn more, please refer to the demo, the blog, and the Application Load Balancer documentation.
Application Load Balancers now support invoking Lambda functions to serve HTTP(S) requests. This enables users to access serverless applications from any HTTP client, including web browsers. With the Application Load Balancers' support for content-based routing rules, you can also route requests to different Lambda functions based on the request content. Prior to this launch, you could only use EC2 instances, containers, and on-premises servers, as targets for Application Load Balancers, and you needed other proxy solutions to invoke Lambda functions over HTTP(S). You can now use an Application Load Balancer as a common HTTP endpoint to simplify operations and monitoring for applications that use servers and serverless computing.
You can register Lambda functions as targets for an Application Load Balancer using the Elastic Load Balancing Console, AWS SDK, or AWS Command Line Interface (CLI). You can also configure an Application Load Balancer as a trigger for a Lambda functions from the AWS Lambda console in few clicks.
Usual AWS Lambda and Application Load Balancer charges apply. Please visit the Application Load Balancer pricing page for more information.
Support for Lambda invocation via Application Load Balancer is available for existing and new Application Load Balancers in US East (N. Virginia), US East (Ohio), US West (Northern California), US West (Oregon), Asia Pacific (Mumbai), Asia Pacific (Seoul), Asia Pacific (Singapore), Asia Pacific (Sydney), Asia Pacific (Tokyo), Canada ( Central), EU (Frankfurt), EU (Ireland), EU (London), EU (Paris), South America (São Paulo), and GovCloud (US-West) AWS Regions.
To learn more, please refer to the demo, the blog, and the Application Load Balancer documentation.