Object Storage

Object Storage is the S3-compatible blob store the platform leans on for anything large and durable: signed firmware images and cold telemetry exports. It is a managed, third-party store — we own the objects we put in it, not the service itself.

Integration contract

Plain S3 semantics over HTTPS: PUT/GET by key, presigned URLs for delegated access, and lifecycle rules for tiering and expiry. No schema, no API of ours to model — just buckets and keys.

What we store

Signed firmware artifacts referenced by OTA campaigns.
Devices download via short-lived presigned URLs, never long-term keys.

Durability & failure handling

Objects are stored with high durability (designed for 11 nines).
Reads tolerate transient errors with retry; writes are idempotent on key.
An outage blocks new firmware downloads but never corrupts already-cached artifacts on the edge.

Where it sits in the flow

Firmware artifacts are pulled from object storage during an OTA rollout: