automotive-sdv

Use an MQTT client like Eclipse Paho to publish telemetry to topics such as vehicles/{vin}/telemetry/{type} with QoS levels per data criticality. The Skill provides a complete Python client with TLS, automatic reconnection, and SQLite offline buffering for connectivity loss.

The reference architecture uses AWS IoT Core for device messaging, DynamoDB for vehicle state, Timestream for time-series telemetry, SNS for alerts, and IoT topic rules to route messages. Terraform configurations for all of these resources are included.

Buffer messages locally in a SQLite database when the MQTT broker is unreachable, then flush the buffer in order once the connection is restored. This prevents data loss during coverage gaps without blocking the CAN monitoring loop.

Yes, container runtimes like Docker, Podman, and containerd can run vehicle applications with defined resource limits and inter-container communication. The Skill covers manifest formats and automotive-specific constraints for containerized workloads.

Use X.509 certificate-based device authentication, TLS 1.2+ transport encryption, fine-grained per-VIN authorization policies, and audit logging of all remote commands. Certificates should be securely provisioned during vehicle manufacturing.