CloudFront function or Lambda@edge

0

I am attempting to validate a jwt. Should I used CloudFront function or Lambda@edge?

posta un anno fa769 visualizzazioni
3 Risposte
1
Risposta accettata

Using Lambda@Edge is preferred because it allows you to utilize libraries that may not be available on CloudFront Functions.

Here is a good article describing this in detail: https://medium.com/trackit/cloudfront-functions-vs-lambda-edge-which-one-should-you-choose-c88527647695

profile picture
con risposta un anno fa
profile pictureAWS
ESPERTO
verificato un anno fa
1

In terms of JWT validation, in my opinion you might want to consider CloudFront Functions as it provides the lowest possible latency with available free tier pricing.

Here's a quick comparison table in the document: https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/edge-functions.html#edge-functions-choosing

Meanwhile, here's example CloudFront Functions that validates a JWT in the query string of a request which might be of help: https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/example-function-validate-token.html

AWS
weidi
con risposta un anno fa
profile picture
ESPERTO
verificato 2 mesi fa
0

Another thing to consider is security. The CloudFront Function can't access KMS or Secrets Manager so you have to store the secret key in the source code. LambdaEdge will allow you to make use of purpose built secure storage to reduce the risk of key exposure. If you ever need to rotate the key, add a new key, etc. This is all a configuration change versus new code.

profile pictureAWS
con risposta un anno fa

Accesso non effettuato. Accedi per postare una risposta.

Una buona risposta soddisfa chiaramente la domanda, fornisce un feedback costruttivo e incoraggia la crescita professionale del richiedente.

Linee guida per rispondere alle domande