SQS Message Schemas
The processor Lambda
Processor Lambda container — runs PyTECGg calibration per SQS message; adopted when a Batch on Fargate parallel-execution quota increase was rejected. Image from `ghcr.io/platformfuzz/tec-processor-image` mirrored to ECR. container consumes messages from two SQS
Amazon Simple Queue Service — buffers ingest and reprocess messages between S3/API and the processor Lambda. queues with separate concurrency limits. Message body shapes are the same structurally; routing differs by queue.
Queue routing
Section titled “Queue routing”| Queue | Accepts | Source |
|---|---|---|
| Reprocess_Queue SQS standard queue — buffers reprocessing job messages from the Reprocess API with lower concurrency than ingest. | Shape 1 only | Reprocess API |
| Process_Queue SQS standard queue — receives S3 ObjectCreated notifications for new raw RINEX files; triggers processor Lambda ingest path. | Shape 2 and Shape 3 | S3 |
Shape 1 — Reprocess API (direct payload)
Section titled “Shape 1 — Reprocess API (direct payload)”Sent by the Reprocess_API Lambda when a job is submitted:
{ "key": "raw/rinexhourly/2026/179/auck1790.26o", "job_id": "uuid-v4", "trace_id": "uuid-v4", "parameters": { "NAV_DAY_OFFSET": 2 }}| Field | Type | Required | Description |
|---|---|---|---|
key | String | Yes | Full S3 object key of the raw RINEX |
job_id | String | Yes | UUID v4 identifying the reprocessing job |
trace_id | String | Yes | UUID v4 for end-to-end correlation |
parameters | Object | No | Override processing parameters (see allowlist below) |
Shape 2 — S3 Event Notification (ingest-triggered)
Section titled “Shape 2 — S3 Event Notification (ingest-triggered)”Standard AWS S3 event notification forwarded from the data lake bucket to Process_Queue. The processor reads Records[0].s3 from the message body to extract bucket and key.
Shape 3 — SNS-Wrapped S3 Event
Section titled “Shape 3 — SNS-Wrapped S3 Event” SNS
Amazon Simple Notification Service — publishes CloudWatch alarm notifications; subscribe an email endpoint after deploy. notification wrapping a Shape 2 S3 event in a
Message field. The processor unwraps and processes as Shape 2.
Allowed parameters keys
Section titled “Allowed parameters keys”Only the following parameter names are accepted. Any other key is rejected by the Reprocess API before the message is enqueued.
| Parameter | Type | Default | Description |
|---|---|---|---|
NAV_DAY_OFFSET | Integer | 1 | Days before observation DOY |
SAVE_PARQUET | Boolean | true | Write Parquet |
SAVE_CSV | Boolean | true | Write CSV output |
SAVE_JSON | Boolean | true | Write JSON output |
SAVE_STATIC_PLOTS | Boolean | false | Generate static plot images (.png) |
SAVE_INTERACTIVE_PLOTS | Boolean | false | Generate interactive HTML plots |
Related pages
Section titled “Related pages”- DynamoDB Jobs Table — job status tracking
- Reprocess Workflow — end-to-end verification