Empresas
Empregos
  • Sobre nós
  • Soluções
    • Publicação de vagas
      Publique sua vaga e receba candidatos qualificados em 48h.
    • Avaliações de candidatos
      Mais de 500 testes técnicos e psicológicos, mais anti-fraude.
    • Headhunting
      Busca executiva personalizada do início ao fim.
    • Folha de Pagamento + EOR
      Dispersão de folha e EOR em mais de 15 países da LATAM.
  • Preços
  • Empregos

0

202
Visualizações
How to monitor if all aws lambda functions executions finish correctly

There is a list of tables that are copied from Aurora to a S3 bucket in csv format.

For every S3 PUT event a lambda function is triggered, which processes the corresponding csv file.

If I have 50 csv files, how could I track that all of them have been successfully processed?

The conceptual solution would be having a list of the 50 csv files, each of them associated with a lambda execution id, and when every function finishes it updates the corresponding entry in that file.

When all files are processed correctly a trigger is fired and sends an SNS message.

But I don't really know which tools or what would be the best way to implement a solution like this.

Thanks for your time.

over 4 years ago · Santiago Trujillo
1 Respostas
Responde à pergunta

0

There are few ways of doing this. One way would involve a second lambda (called L2) and a SQS.

In this solution, your first lambda (L1) would be triggered by the S3 events and process the csv files. The L1 would also publish a message to an SQS queue upon complication of csv processing with the metadata of the process file.

The SQS queue would trigger the L2. The only job of L2 would be to check if all the files have been processed, and if yes, send an SNS notification to you.

Exact details of "check if all the files have been processed" are application specific and depend how you mark each csv file as process. You could store the csv complication metadata in DynamoDB, or in S3 as you may be doing now.

To eliminate concurrency issues of L2, you could limit it concurrency to 1, so the SQS messages are processed by only one function (not several L2 functions in parallel).

You could extend the above solution by second SQS, so called dead letter queue (DLQ), which would hold information about failed csv processes. This way your L2 would also be able to determine if something has failed, based on the DLQ.

Extra links:

  • Using AWS Lambda with Amazon SQS
  • Amazon SQS dead-letter queues
over 4 years ago · Santiago Trujillo Relatório
Responde à pergunta
Encontrar trabalhos remotos

Descubra a nova forma de encontrar um emprego!

melhores empregos
Principais categorias de trabalho
Empresas
Postar vaga Preços Comercial
Jurídico
Termos e Condições Política de privacidade
© 2026 PeakU Inc. All Rights Reserved.
Andres GPT
Recomende algumas ofertas para mim
Preciso de ajuda