# Licode on Amazon Web Services (AWS)

**URL:** <https://discourse.lynckia.com/t/licode-on-amazon-web-services-aws/219>\
**Category:** Uncategorized\
**Created:** [November 20, 2013, 2:22am UTC](https://discourse.lynckia.com/t/licode-on-amazon-web-services-aws/219 "2013-11-20T02:22:51Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Yeng](https://avatars.discourse-cdn.com/v4/letter/y/3da27b/32.png) [@Yeng](https://discourse.lynckia.com/u/Yeng)\
**Post date:** [November 20, 2013, 2:22am UTC](https://discourse.lynckia.com/t/licode-on-amazon-web-services-aws/219/1 "2013-11-20T02:22:51Z")

</div>

Good Day,

Thanks to the whole Licode Team for a very brilliant and impressive project.

I have implemented the Licode on our Amazon Web Services and after several  
attempts, it was working perfectly now.  
There were some issues that I encountered by I have done some fixes on it  
particularly on the erizoController.js. I just wanted to confirm if I am  
doing the “correct fix” on it.  
Just to describe our AWS setup, Our server has a public IP address of  
54.x.x.x and a Private IP of 10.x.x.x. During the page request, the  
"createToken" is using the correct publicIP but requesting to "socketio"  
uses the privateIP, so what I did was to hardwire the publicIP address to  
the erizoController.js.

publicIP = ‘54.x…’;

Is this the correct fix?

And also, when I use Ubuntu, The video stream is upside down? is this  
somewhere connected with Licode?

Thank you very much for your great work.

Lawrence

---

<div class="post-metadata">

**Author:** ![robomon1](https://avatars.discourse-cdn.com/v4/letter/r/7ab992/32.png) [@robomon1](https://discourse.lynckia.com/u/robomon1)\
**Post date:** [November 21, 2013, 7:57pm UTC](https://discourse.lynckia.com/t/licode-on-amazon-web-services-aws/219/2 "2013-11-21T19:57:38Z")

</div>

Hi Lawrence,

Make sure you first set the amazon properties in the the licode\_config.js.  
That is how licode gets the public ip address for the amazon instance.

config.cloudProvider.name = ‘amazon’;  
//In Amazon Ec2 instances you can specify the zone host. By default is  
‘[ec2.us-east-1a.amazonaws.com](http://ec2.us-east-1a.amazonaws.com)’  
config.cloudProvider.host = ‘[ec2.amazonaws.com](http://ec2.amazonaws.com)’;  
config.cloudProvider.accessKey = ‘’;  
config.cloudProvider.secretAccessKey = ‘’;

roboOn Tuesday, November 19, 2013 6:22:51 PM UTC-8, Yeng wrote:

> Good Day,
> 
> Thanks to the whole Licode Team for a very brilliant and impressive  
> project.
> 
> I have implemented the Licode on our Amazon Web Services and after several  
> attempts, it was working perfectly now.  
> There were some issues that I encountered by I have done some fixes on it  
> particularly on the erizoController.js. I just wanted to confirm if I am  
> doing the “correct fix” on it.  
> Just to describe our AWS setup, Our server has a public IP address of  
> 54.x.x.x and a Private IP of 10.x.x.x. During the page request, the  
> “createToken” is using the correct publicIP but requesting to “socketio”  
> uses the privateIP, so what I did was to hardwire the publicIP address to  
> the erizoController.js.
> 
> publicIP = ‘54.x…’;
> 
> Is this the correct fix?
> 
> And also, when I use Ubuntu, The video stream is upside down? is this  
> somewhere connected with Licode?
> 
> Thank you very much for your great work.
> 
> Lawrence