Beta: AWS Lambda integration

Use Gloo Gateway to route traffic requests directly to an Amazon Web Services (AWS) Lambda function.

The AWS Lambda integration is a beta feature. Beta features might change and are not supported for production. For more information, see Gloo feature maturity.


Serverless functions, such as Lambda functions, provide an alternative to traditional applications or services. The functions run on servers that you do not have to manage yourself, and you pay for only for the compute time you use. However, you might want to invoke your serverless functions from other services or apps, such as the Kubernetes workloads that run in clusters in your Gloo Gateway environment. By abstracting a Lambda as a type of destination in your Gloo Gateway environment, your workloads can send requests to the Lambda destination in the same way that you set up routing through Gloo Gateway to other types of destinations. Gloo Gateway does the work of assuming an AWS IAM role to invoke the actual Lambda function in your AWS account.

Gloo Gateway integration

Gloo Gateway supports multiple features to help you seamlessly invoke Lambda functions from your Gloo environment:

Get started

Check out the following pages to integrate Lambda invocation in your Gloo environment.

Known issues

In Gloo Gateway 2.3, the Gloo custom resources for the AWS Lambda integration are changed in the following breaking ways. If you used the AWS Lambda integration in 2.2, create copies of your existing CloudProvider, CloudResources, and any Lambda RouteTable resources and update the copies to the new format, which you apply during the migration from 2.2 to 2.3.