# Live streaming architecture on AWS

**URL:** <https://community.wowza.com/t/live-streaming-architecture-on-aws/47195>\
**Category:** Wowza Streaming Engine\
**Created:** [June 22, 2016, 8:43am UTC](https://community.wowza.com/t/live-streaming-architecture-on-aws/47195 "2016-06-22T08:43:38Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jorge\_Barrios](https://avatars.discourse-cdn.com/v4/letter/j/9fc348/32.png) [@Jorge\_Barrios](https://community.wowza.com/u/Jorge_Barrios)\
**Post date:** [June 22, 2016, 8:43am UTC](https://community.wowza.com/t/live-streaming-architecture-on-aws/47195/1 "2016-06-22T08:43:38Z")

</div>

Hi, we are looking to replace our existing streaming system with Wowza Streaming Media servers and would love some help figuring out how to do it.

Requirements:

- Dynamically created streams

- HLS adaptive bit rate playlists

- Scalable stream sources

- Scalable stream targets

---

<div class="post-metadata">

**Author:** ![SiggDev](https://avatars.discourse-cdn.com/v4/letter/s/dec6dc/32.png) [@SiggDev](https://community.wowza.com/u/SiggDev)\
**Post date:** [July 4, 2016, 3:53pm UTC](https://community.wowza.com/t/live-streaming-architecture-on-aws/47195/2 "2016-07-04T15:53:07Z")

</div>

Why not extend the push publish module to copy the files to the CDN origin at the same time when push publishing?

---

<div class="post-metadata">

**Author:** ![Andy\_Engberson](https://sea2.discourse-cdn.com/flex002/user_avatar/community.wowza.com/andy_engberson/32/392_2.png) [@Andy\_Engberson](https://community.wowza.com/u/Andy_Engberson)\
**Post date:** [August 9, 2016, 11:05pm UTC](https://community.wowza.com/t/live-streaming-architecture-on-aws/47195/3 "2016-08-09T23:05:27Z")

</div>

Hello,

We recently changed the PushPublish API to allow pushing HLS to any HTTP endpoint that allows it.

See the example pushpublish hls [here](https://github.com/WowzaMediaSystems/wse-example-pushpublish-hls)

Regards,

Andy\_E