Publishing Scenes in the Amazon Sumerian Editor - Amazon Sumerian

Publishing Scenes in the Amazon Sumerian Editor

Publish your Amazon Sumerian scene to share it with users on the internet. When you publish a scene, Sumerian creates a static website with your scene and hosts it on Amazon CloudFront. You can link users directly to the scene, or embed it in a frame in your website.

You can also deploy a scene for use with AWS Amplify. When you choose a private deployment, Sumerian generates a configuration file that you can load into your web app to embed a scene that can only be accessed with credentials from Amazon Cognito.

To publish a scene

When you create a scene and are ready to share it, you need to publish the scene in order for it to be accessible to your end users.

  1. Open your scene in the Sumerian editor.

  2. Choose Publish.

    
          The Sumerian publish button
  3. Choose Create public link or Host privately.

    
          The Sumerian publish options
  4. Choose Publish.

For a public scene, open the URL to view it. This URL is publicly hosted with Amazon CloudFront and can be viewed by anyone.

To republish a scene

When you modify a scene that has already been published, you need to republish the scene for your changes to take effect in the published version. Republishing also allows you to capture release updates in the Sumerian engine.

  1. Open your scene in the Sumerian editor.

  2. Choose Publish.

  3. Choose Republish.

    
          The Sumerian re-publish

Your existing url will now reflect the latest scene changes and engine updates.

To unpublish a scene

  1. Open your scene in the Sumerian editor.

  2. Choose Publish.

  3. Choose Unpublish.

    
          The Sumerian re-publish
  4. Choose Unpublish again.

For a private scene, load the configuration file into your Amplify app with the XR module. For more information, see AWS Amplify.

With Amplify, access to your scene is granted to users who log in with Amazon Cognito. For details about adding permissions to your app's identity pool, see Restricting Access to a Published Scene.