The aggregator lambda (SQSMain), now listens to an SQS queue populated by the ingestor-works SNS.
As mentioned when the Lambda was originally provisioned, it would be a good idea to separate the bulk, snapshot-driven lambda from the one-at-a-time event-driven lambda. This takes a step in that direction, by actively separating the code. It is not possible now to invoke a bulk-mode aggregation from SQS messages.
This PR does not provision the bulk version, on AWS, that can be follow-up work, because this has enough in it already.
https://github.com/wellcomecollection/concepts-pipeline/issues/54
The aggregator lambda (SQSMain), now listens to an SQS queue populated by the ingestor-works SNS.
As mentioned when the Lambda was originally provisioned, it would be a good idea to separate the bulk, snapshot-driven lambda from the one-at-a-time event-driven lambda. This takes a step in that direction, by actively separating the code. It is not possible now to invoke a bulk-mode aggregation from SQS messages.
This PR does not provision the bulk version, on AWS, that can be follow-up work, because this has enough in it already.