-
### Gloo Edge Product
Enterprise
### Gloo Edge Version
1.17.0
### Is your feature request related to a problem? Please describe.
# Context
In our current implementation to support fu…
-
Lambda@Edge has more limitation compare to classic AWS Lambda. AWS Lambda is more powerful, more tooling, etc.
Lambda@Edge limit our Next.js api's to accept only 1MB of data.
Normal lambda is ch…
-
At the moment, we are using a Cloudfront origin to redirect traffic going /api/ to our API Gateway. We want to use Lambda@Edge for this functionality. This will be essential for when DR's API goes pub…
-
Hey, shuyo! the 351 line in crf.py :features.add_feature_edge( lambda y_, y: 0 ) , is there a problem? THX!!!
goog updated
12 years ago
-
> The function cannot have environment variables. Function: arn:aws:lambda:us-east-1:xxxx:function:xxxx:1 (Service: AmazonCloudFront; Status Code:
> 400; Error Code: InvalidLambdaFunctionAssociation…
-
Currently `sst start` sets the websocket endpoint as environment variables for the stub Lambda functions. Lambda@Edge functions do not support environment variables. Need to use other ways to pass the…
-
### Issue Summary
I've tried building Lambda@Edge using the [latest Next.js v12.1.0 release](https://github.com/vercel/next.js/releases/tag/v12.1.0) with `"type": "module"` setting in `package.json`,…
-
Our organisation are using cdk-nextjs and for our security requirements, it would be beneficial to have OAC implemented between Cloudfront and the Lambdas vs the current edge solution. Now that OAC i…
-
As seen in OP report, the "squared" bases has some stray edges that the "functional" basis does not have.
Presumably due to wrong Lambdas.
![image](https://github.com/ApolloResearch/rib/assets/1…
-
### Gloo Edge Product
Enterprise
### Gloo Edge Version
1.16.7
### Is your feature request related to a problem? Please describe.
Lambda authorizer generates headers and puts them in the authorize…