Open jhkennedy opened 1 week ago
This is likely because Synergize places the products in AWS and manages the SNS topics, but the STAC catalog is managed by Element84, so there is likely a delay between SNS message from Synergize and the item being indexed by Element84.
It might be worth setting up a SQS for Sentinel-2 separate from Landsat so that we can add a 15-minute delivery delay for Sentinel-2 messages. We could also allow separate visibility time-outs for Landsat (prev. was 5 min) and sentinel-2 instead of the uniform 8 hours we currently use.
:thinking: Element84 actually provides their own SNS topic for scenes ingested into the catalog, so maybe we should switch over to using that topic: https://github.com/Element84/earth-search?tab=readme-ov-file#sns-notifications-of-items
That should mean any scene broadcast is available in the STAC catalog.
The delivery delay may still be useful to provide some time for the scene to be available in Google Cloud before our first processing attempt.
I see lots of these messages in the cloudwatch logs: