# Redundant entry points @ Wowza Streaming Engine on EC2
**URL:** https://community.wowza.com/t/redundant-entry-points-wowza-streaming-engine-on-ec2/39487
**Category:** Wowza Streaming Engine
**Created:** [October 11, 2016, 11:24am UTC](https://community.wowza.com/t/redundant-entry-points-wowza-streaming-engine-on-ec2/39487 "2016-10-11T11:24:18Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@Johan\_Niemi](https://community.wowza.com/u/Johan_Niemi)
#### Post date: [October 11, 2016, 11:24am UTC](https://community.wowza.com/t/redundant-entry-points-wowza-streaming-engine-on-ec2/39487/1 "2016-10-11T11:24:18Z")
I’m looking for the best way to set up primary and backup entry points for two encoders live streaming the same content, just like the way it is set up with [Wowza Streaming Cloud](https://www.wowza.com/docs/how-to-build-a-redundant-workflow-by-using-a-stream-source) or Youtube Live.
Our Wowza Streaming Engine server is running on Amazon EC2.
How do we best set this up and ensure an uninterrupted experience for those wathcing a live stream when one of the encoders fails?
---
### Author:  [@Johan\_Niemi](https://community.wowza.com/u/Johan_Niemi)
#### Post date: [October 27, 2016, 10:39am UTC](https://community.wowza.com/t/redundant-entry-points-wowza-streaming-engine-on-ec2/39487/2 "2016-10-27T10:39:36Z")
Anyone knows how to set this up? I’m thinking of doing it one of these ways depending on the importance of the event:
**Redundant encoder workflow**
Two encoders streaming. Both to the same Wowza Streaming Engine server.
**Redundant encoder and server workflow**
Four encoders streaming. Two to server **a**. Two to server **b**.
---
### Author:  [@Johan\_Niemi](https://community.wowza.com/u/Johan_Niemi)
#### Post date: [November 10, 2016, 10:43am UTC](https://community.wowza.com/t/redundant-entry-points-wowza-streaming-engine-on-ec2/39487/3 "2016-11-10T10:43:59Z")
To break the silence let’s focus on one thing then:
**Encoder redundancy** by having two live encoders streaming to the same Wowza Streaming Engine server, to the same application and to the same stream name:
Live encoder 1:
Server URL: rtmp://50.50.50.50/live
Stream name: **[enc1]**\_myStream
Live encoder 2:
Server URL: rtmp://50.50.50.50/live
Stream name: **[enc2]**\_myStream
Public streaming URL would then be:
[http://50.50.50.50/live/myStream/playlist.m3u8](http://50.50.50.50/live/myStream/playlist.m3u8)
It would be prioritizing the primary incoming stream from encoder 1:
rtmp://50.50.50.50/live/**[enc1]**\_myStream
If encoder 1 disconnects, the secondary stream takes over:
rtmp://50.50.50.50/live/**[enc2]**\_myStream
Is it it possible to achieve encoder redundancy like this, without adding additional Wowza Streaming Engine servers into the equation?
---
### Author:  [@SiggDev](https://community.wowza.com/u/SiggDev)
#### Post date: [November 11, 2016, 7:24pm UTC](https://community.wowza.com/t/redundant-entry-points-wowza-streaming-engine-on-ec2/39487/4 "2016-11-11T19:24:14Z")
My first idea would be to have two origin servers accepting streams from different encoders and have edge servers set up with primary and backup origin servers. But if you want to use only a single origin server, you could achieve the same thing using different vhosts. Maybe even simply using different applications in the same vhost, but I haven’t tried this.
However, if you’re trying to achieve redundancy for encoders themselves, I’m not sure this will work. If I remember well, origin failover works only if the origin server (application) itself is not operational, not sure if the failover would happen if only the stream is not available on the primary origin, but the origin itself is still operational (worth checking out, though).
In your last example, I’m not sure how the switchover would happen? If it happens on the web-application level, then it’s clear, but I’m not sure if there is any way to do it in Wowza itself.