#### Version 2.9.89 > The **Streaming Engine** is compatible with **AWS**. This works with both **SRT Caller** mode and **RTSP Push** into **Amazon AWS**. This was the method used to provide full end-to-end solution. ![[z_img/bd23dc82ca0491e2a1e3b7d2395eb7b4_MD5.jpeg]] `HLS` is used in **AWS** for this. From the channel preview in **AWS** to the actual “Live” timestamp in the **HLS player** there is about `45s` difference. From the point of view of our **Streaming Engine** and **Milestone XProtect**, when **AWS** starts the `MediaLive channel` and opens the stream from our **Streaming Engine** in `SRT` called mode, that is when the stream is initiated and sent over to **AWS**. Also, our **Streaming Engine** has an `API` and it can accept callbacks to start and stop the streams on demand as well if this is not done via the **Milestone XProtect** administration interface.. For this **On-Demand SRT Caller mode**, a TCP port must be opened on the external firewall for each separate stream, but all secured within the **SRT protocol**. Otherwise, we can push **RTMP** out but that is not encrypted.