Atlas Cloud Connect

Atlas Cloud Connect provides distributed eventing and control system allowing real-time Cloud and on-premesis resource connectivity, without private network ingress.

Atlas Cloud Connect is a JSON based control protocol over MQTT with support for Websockets in-browser (or other clients where direct TCP connections cannot be established).

Cloud Connect allows for the Atlas Experience Manager to both control Node and receive updates from controlled devices, this includes:

• Remotely starting, stopping, restarting applications on a Node
• Real-time Node status updates and profiling
• Controlling AV devices through the Liminial AV bridge

Additionally, Cloud Connect may be used to build distributed applications, both on-premesis, in the Cloud or as hybrid experience. The Cloud Connect infrastrucutre is easily extended to support your own applications, topics and messages.

Cloud Connect Concepts

There are three core concepts behind Atlas Cloud Connect inherited from MQTT:

1. Clients: A software client connecting the Cloud Connect (MQTT) server
2. Client ID: A unique identifer for the connected User, typically the username plus random hash
3. Credentials: Username and Password tied to a specific Experience Manager User
4. Messages: A stringified JSON object (see: Message Protocol) sent/received via Topics
5. Permissions: Permissions assigned to a User defining what interaction they have with a specific Topic: Read, Write and Subscribe
6. Topics: A subscribable channel, with User specific permissions

Getting Started

To get started with Cloud Connect, see Get Connected. This will step you through how to obtain credentials and get connected.

Once you are connected, review both Topic Scheme and Message Protocol for information on how to use Cloud Connect.

Developing an application that needs real-time messaging, check out Custom Messaging Protocols.