Configure Greengrass v2 inter-process communication (IPC) for a component to publish to IoT Core

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

Steps

  1. In the component recipe, declare an IPC authorization policy under accessControl granting aws.greengrass.ipc.mqttproxy:aws.greengrass#PublishToIoTCore permission for the topic pattern the component will publish to.
  2. In component code, create a Greengrass IPC client using the AWS IoT Device SDK v2 Greengrass IPC library; establish the IPC socket connection (the SDK reads the socket path from the IPC_SERVER_SOCKET_PATH environment variable injected by the nucleus).
  3. Call PublishToIoTCore with the topic string, QoS level, and payload bytes; the nucleus proxies the publish to AWS IoT Core using the core device's certificate.
  4. For subscribing to topics, declare SubscribeToIoTCore authorization in the recipe and call SubscribeToIoTCore via IPC, processing messages in a callback or async handler.
  5. Use SubscribeToTopic for local pub/sub between components on the same device without routing through IoT Core; declare the local topic in the recipe's accessControl section separately.
  6. Test the IPC authorization by checking Greengrass nucleus logs at /greengrass/v2/logs/greengrass.log for AccessDenied errors if the component's publish requests are rejected.

Known gotchas

Related routes

Deploy a custom AWS IoT Greengrass v2 component with a recipe and S3 artifact
aws-iot-greengrass · 6 steps · unrated
Deploy a custom component to an edge device using AWS IoT Greengrass v2
aws.amazon.com · 6 steps · unrated
Buffer and export local device data from AWS IoT Greengrass v2 using the Stream Manager component
docs.aws.amazon.com · 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