amazon web services - AWS Neptune access from Lambda - Error 429 "Too Many Requests"

Question

I am working on an app that uses AWS Lambda which eventually updates Neptune. I noticed, that in some cases I get a 429 Error from Neptune: Too Many Requests. Well, as descriptive as it might sound, I would love to hear an advice on how to deal with it. What would be the best way to handle that?

Although I am using a dead letter queue, I'd rather have it not going this road at the first place.

Btw the lambda is triggered by a SQS (standard) queue.

Any suggestions?

question from:https://stackoverflow.com/questions/65833647/aws-neptune-access-from-lambda-error-429-too-many-requests

Answer 1

Waitting for answers