> For the complete documentation index, see [llms.txt](https://resources.unizin.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://resources.unizin.org/products/data-and-analytics/unizin-data-platform/miscellaneous/canvas-live-events-from-sqs-to-https.md).

# Canvas Live Events: from SQS to HTTPS

Canvas offers two methods of delivering streaming data (Live Events): SQS and HTTPS. All Unizin members today use the SQS delivery method. We are asking our members to shift to using the HTTPS method.

To conduct the change, your Canvas Admin will:

1. Configure and activate an HTTPS data stream in Canvas that goes to the UDP
2. Deactivate their existing SQS data stream in Canvas

Ideally, both actions are conducted immediately after the other and outside of business hours so as to minimize the event overlap or loss.

## **Configure and activate an HTTPS data stream** <a href="#canvasliveevents-fromsqstohttps-configureandactivateanhttpsdatastream" id="canvasliveevents-fromsqstohttps-configureandactivateanhttpsdatastream"></a>

Broadly speaking, you will follow [Instructure’s instructions for setting up HTTPS](https://community.canvaslms.com/t5/Admin-Guide/How-do-I-configure-and-test-Canvas-Live-Events-using-HTTPS/ta-p/151). You will need to set the following variables:

<table><thead><tr><th width="256">Variable</th><th>Value</th></tr></thead><tbody><tr><td>Name</td><td><em>Whatever you wish</em>.</td></tr><tr><td>Active</td><td><em>Turned on</em>.</td></tr><tr><td>Delivery method</td><td>HTTPS</td></tr><tr><td>URL</td><td><p>PROD: https://caliper.<strong>&#x3C;shortcode></strong>.cloud.unizin.org/</p><p>SIT: https://caliper.<strong>&#x3C;shortcode></strong>.sit.cloud.unizin.org/</p></td></tr><tr><td>Sign Payload</td><td><em>Checked</em></td></tr><tr><td>Message type</td><td>Caliper 1.1</td></tr></tbody></table>

**Note:** the **\<shortcode>** value should be replaced with your institution’s primary domain name. For example,  Indiana University’s shortcode is `iu`, Colorado State University’s shortcode is `colostate`. Iowa’s shortcode is `uiowa`, etc. If in doubt, put the URL in the browser. You should see a response like this:

{% code title="Endpoint response" overflow="wrap" %}

```json
{"caliperSupportedVersions": ["http://purl.imsglobal.org/ctx/caliper/v1p2"], "caliperSupportedExtensions": {"endpointVersion": "1.0.43+pib"}}

```

{% endcode %}

Also, make sure that all message subscriptions are turned on.

## **Deactivate your SQS data stream** <a href="#canvasliveevents-fromsqstohttps-deactivateyoursqsdatastream" id="canvasliveevents-fromsqstohttps-deactivateyoursqsdatastream"></a>

In the Data services tool (under the Admin panel), identify your existing SQS-based datastream. Under the “`actions`” menu for the data stream, select “`deactivate`.”

![](https://lh5.googleusercontent.com/QUNNWc-FnnPW5GZJehI-clWR_gGO1_2VXCukmRn_GpjW8xJ917doN1XUsgCM2b6QzUfB2jpMWZnVikf6PCjL-fbkghgpbhr7kjplPbAxGiJAorWPskeV58BRbxsYExj9-Nj4960i)

That’s it, you’re done!


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://resources.unizin.org/products/data-and-analytics/unizin-data-platform/miscellaneous/canvas-live-events-from-sqs-to-https.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
