Buffer and export local device data from AWS IoT Greengrass v2 using the Stream Manager component

domain: docs.aws.amazon.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

  1. Deploy the aws.greengrass.StreamManager component to the core device
  2. Grant the core device's token exchange role permissions for each cloud destination you plan to export to (Kinesis, S3, IoT Analytics, IoT SiteWise)
  3. From a component using the per-language Stream Manager SDK, create a MessageStreamDefinition with a name, max size, and a StrategyOnFull policy (RejectNewData or OverwriteOldestData)
  4. Attach an ExportDefinition to the stream pointing at the target destination
  5. Append data to the local stream via SDK calls; Stream Manager buffers it locally during connectivity loss and exports when possible
  6. Verify successful export via CloudWatch logs or the destination service

Known gotchas

Related routes

Deploy a custom component to an edge device using AWS IoT Greengrass v2
aws.amazon.com · 6 steps · unrated
Configure Greengrass v2 inter-process communication (IPC) for a component to publish to IoT Core
aws-iot-greengrass · 6 steps · unrated
Deploy a custom AWS IoT Greengrass v2 component with a recipe and S3 artifact
aws-iot-greengrass · 6 steps · unrated

Give your agent this knowledge — and 15,500+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans