EventBridge Scheduler
After full deployment, confirm the EventBridge Scheduler
AWS EventBridge Scheduler — triggers ingest-sync Lambda on a recurring UTC schedule (default: hourly). that triggers automated RINEX
Receiver Independent Exchange Format — standard GNSS observation file format synced from GeoNet and calibrated by the processor. ingest is present and named correctly.
Check scheduler exists
Section titled “Check scheduler exists”From the demo repo root:
aws scheduler list-schedules --query "Schedules[?contains(Name, 'ingest-sync')]"Expect at least one schedule whose name contains ingest-sync.
Expected configuration
Section titled “Expected configuration”| Setting | Default | Terraform variable |
|---|---|---|
| Schedule | Every 1 hour |
|
| Target | Ingest_Sync_Lambda Ingest-sync Lambda (`services/ingest-sync/`) — polls GeoNet on schedule and copies recent RINEX into the data lake (workaround for no source-bucket event subscription). |
|
| Time zone | UTC | EventBridge Scheduler default |
The scheduler was enabled during Staged Apply stage 2 (-target=module.ingest_scheduler).
Verify target Lambda
Section titled “Verify target Lambda”aws lambda get-function-configuration --function-name ingest-sync \ --query '{State:State,LastUpdateStatus:LastUpdateStatus}'State should be Active with LastUpdateStatus of Successful.
What happens on fire
Section titled “What happens on fire”Each schedule invocation:
- Ingest_Sync_Lambda computes a rolling window from LOOKBACK_HOURS
Ingest configuration — UTC rolling window (default 1 hour) defining how far back ingest-sync scans for new RINEX files. (default 1) - Lists GeoNet objects under
gnss/rinexhourly/ - Copies new files to
raw/rinexhourly/{year}/{doy}/{filename}
Next steps
Section titled “Next steps”- Optionally trigger ingest immediately: Manual Ingest
- After files land, verify queues: SQS Queues