Amazon Sumerian能否直接响应Amazon SNS事件？是否仅需通过IoT实现？

Hey there! As someone who’s worked with Sumerian and AWS services, let’s break down your questions clearly and practically:

Can Amazon Sumerian directly respond to Amazon SNS events? #

Short answer: No, Sumerian doesn’t have native, direct support for receiving SNS events out of the box. Here’s why: Sumerian scenes run as client-side environments (in browsers or embedded apps), while SNS is a server-side notification service that sends messages to endpoints like email, Lambda, or HTTP/S endpoints. There’s no built-in way for a Sumerian scene to "listen" directly to an SNS topic.

Can this be done with scripts, or do I need to use IoT Shadows? #

Great news—you have two solid, working options here, depending on your needs:

Option 1: Middleware service + custom Sumerian scripts #

You can build a simple middle layer to bridge SNS and your Sumerian scene, then handle event responses with custom scripts. Here’s a typical workflow:

1. Configure your SNS topic to trigger an AWS Lambda function (subscribe the Lambda to the SNS topic).
2. The Lambda forwards the SNS message to a real-time endpoint your Sumerian scene can connect to—like an API Gateway WebSocket API or a lightweight WebSocket server on EC2.
3. In your Sumerian scene, write a script that connects to this WebSocket endpoint, listens for incoming messages, and triggers scene actions (e.g., moving an entity, playing an animation, updating text).

Here’s a simplified snippet of what that Sumerian script might look like:

// Attach this script to a Sumerian entity
const ws = new WebSocket('wss://your-api-gateway-endpoint');

ws.onmessage = function(event) {
  const message = JSON.parse(event.data);
  // Trigger action based on SNS message content
  if (message.eventType === 'start_demo') {
    this.entity.playAnimation('welcome_sequence');
  }
};

Option 2: AWS IoT Shadows (native Sumerian integration) #

Sumerian has built-in support for AWS IoT Core, including IoT Shadows—this is often the faster path if you want to avoid building custom middleware:

1. Set up an IoT Rule that subscribes to your SNS topic. The rule will take incoming SNS messages and update the state of an IoT Thing Shadow.
2. In your Sumerian scene, configure the AWS IoT integration (under "Services" in the editor) to connect to your IoT Thing Shadow.
3. Write a Sumerian script that listens for changes to the shadow’s state and reacts accordingly. For example, if the shadow’s desired state updates with a light_on flag, your script can toggle a light entity in the scene.

This leverages Sumerian’s native AWS service support, so you don’t have to handle WebSocket connections from scratch.

Which should you choose? #

• Go with the middleware + script approach if you need full control over message processing, or if you want to integrate with non-IoT services alongside SNS.
• Use the IoT Shadow approach if you want a simpler, low-code integration that leans on Sumerian’s existing AWS tooling.

内容的提问来源于stack exchange，提问作者NedryContainmentSolns