Connected Products Starter Kit

The kit is the canonical artifact I hand a new connected-product team on day one — a wireless decision rubric, an end-to-end reference architecture, and runnable code for the parts that always slow teams down (mTLS, topic rules, certificate provisioning).

→ github.com/drlukeangel/Connected-Products-Starter-Kit-Product-Management

Why this exists

Every PM and engineering manager I've worked with on connected hardware has run the same first 30 days: they Google "AWS IoT Core tutorial," follow a six-screen wizard, end up with a single device publishing MQTT with a hardcoded cert, and have no idea how to scale it to 10,000 units. I built this kit as the answer to that 30-day problem so the teams I lead don't have to re-discover it every time.

What's in the box

Stack: typescript (CDK + lambda + dashboard) · python (device sim) · rust (embedded) · aws iot core · aws lambda · dynamodb.

How teams use it

Different audiences read different parts:

• Engineering managers fork the whole repo as a starting template
• Product managers read rubric.md and stop there
• Architects read ARCHITECTURE.md and push back on the trade-offs
• Firmware engineers lift device/rust/ as a known-good MQTT + TLS starting point
• Cloud engineers lift cloud/cdk/ as the smallest production-shaped IoT-to-DDB stack

The arc