Feature- Run Lambda Web Functions in the CloudFront request path (Lambda@Edge-style triggers)
@sam-karak ya está trabajando en esto.
Desde el 13/10/2026.
Evaluación
Este issue todavía no se ha evaluado.
Descripción
Note
- Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
- Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do * not help prioritize the request
If you are interested in providing additional feedback, please leave a comment
Description
Let you associate a Lambda Web Function with an Amazon CloudFront distribution as request-path compute, similar to Lambda@Edge. Your Web Function would run on CloudFront requests and responses, for example to rewrite or redirect requests, authenticate viewers, personalize responses, or run middleware for a web framework. It would run close to your viewers, and you wouldn't need to configure it as a separate origin. You would write it as a standard HTTP server using familiar web frameworks, with the same development, deployment, and observability experience as other Web Functions.
Tell us how you would use this: which CloudFront events you need (viewer request, viewer response, origin request, origin response), your latency and runtime preference requirements, and whether you would move existing Lambda@Edge code. Please add details as comments.
- Lenguaje dominante
- Sin datos de lenguaje
- Estrellas
- 198
- Forks
- 5
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Sin plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de aws/aws-lambda-roadmap
-
[Lambda Web Functions] Mutable region set on an endpoint, plus per-region health-based routingAbiertoLambda/Developer Experience Lambda/Web Functions
Dificultad 5/5 Más de una semana Aptitud para principiantes 6/100
aws/aws-lambda-roadmap#118 · 2 comentarios · 1 reacción ·
-
Lambda PM request Lambda/MicroVMs
Dificultad 5/5 Más de una semana Aptitud para principiantes 5/100
aws/aws-lambda-roadmap#117 ·
-
Lambda PM request Lambda/MicroVMs
Dificultad 5/5 Más de una semana Aptitud para principiantes 5/100
aws/aws-lambda-roadmap#116 ·
-
Lambda PM request Lambda/MicroVMs
Dificultad 5/5 Más de una semana Aptitud para principiantes 5/100
aws/aws-lambda-roadmap#115 ·
-
Feature- Private endpoints for Lambda Web FunctionsPosiblemente ocupada @sam-karak la tomó hace 1 día. AbiertoLambda/Web Functions
aws/aws-lambda-roadmap#114 · 1 asignado ·