# Probleming AWS deploy 2.14.0 **URL:** \ **Category:** Issues with deployment\ **Tags:** v2\ **Created:** [May 15, 2020, 2:21pm UTC](https://openvidu.discourse.group/t/probleming-aws-deploy-2-14-0/801 "2020-05-15T14:21:42Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Rodrigo\_Alcantara](https://yyz2.discourse-cdn.com/free1/user_avatar/openvidu.discourse.group/rodrigo_alcantara/32/437_2.png) [@Rodrigo\_Alcantara](https://openvidu.discourse.group/u/Rodrigo_Alcantara)\ **Post date:** [May 15, 2020, 2:21pm UTC](https://openvidu.discourse.group/t/probleming-aws-deploy-2-14-0/801/1 "2020-05-15T14:21:42Z")
Good afternoon, we are using AWS Cloud Formartion as a server for our Openvidu PRO project, but we are experiencing many problems, which I will describe below: 1 - We tried to update to version 2.14.0, it shows roolback in all attempts. 2 - The template provided does not support more powerful instances, we want to use the instance C5.9xlarge for the openvidu Server and M5.xlarge for the Media Node. 3 - Some sessions are not ended, even without any user connected. We are using the project to transmit classes, we have a lot of scale, I believe that at the peak we will have hundreds of active sections simultaneously, each session has an average of 30 users with only 1 publisher, the rest are subscribers. We are using OPENVIDU CALL as the basis for the project, but we need to modify it to suit our business model. This project is aimed at students from the public education system in Brazil, at the moment I have my classes paralyzed. below follows my aws configuration: ## Parameters AWS AwsInstanceTypeKMS | m5.xlarge AwsInstanceTypeOV | c5.2xlarge FreeHTTPAccesToRecordingVideos | true KeyName | ConecttvStream KibanaPassword | \*\*\*\* KibanaUser | kibanaadmin LetsEncryptEmail | developer@tecXXXXXX MediaNodesStartNumber | 2 MyDomainName | openvidu.tecxxxxx.xxx OpenViduLicense | \*\*\*\* OpenViduRecordingTimeOut | 120 OpenViduSecret | \*\*\*\* OpenViduSubnet | subnet-6XXXXXXX OpenViduVPC | vpc-0e7XXXXX OpenViduWebhook | false OpenViduWebhookEndpoint | [http://my.endpoint.com](http://my.endpoint.com) OpenViduWebhookEvents|sessionCreated,sessionDestroyed,participantJoined,participantLeft,webrtcConnectionCreated,webrtcConnectionDestroyed,recordingStatusChanged,filterEventDispatched,mediaNodeStatusChanged OpenViduWebhookHeaders | - OpenviduCDREnable | false OpenviduClusterLoadStrategy | streams OpenviduRecordingNotification | publisher\_moderator OpenviduStreamsVideoMaxRecvBandwidth | 1000 OpenviduStreamsVideoMaxSendBandwidth | 1000 OpenviduStreamsVideoMinRecvBandwidth | 300 OpenviduStreamsVideoMinSendBandwidth | 300 OwnCertCRT | - | OwnCertKEY | - | PublicElasticIP | xx.xx.xx.xx WhichCert | letsencrypt ---
**Author:** ![micael.gallego](https://yyz2.discourse-cdn.com/free1/user_avatar/openvidu.discourse.group/micael.gallego/32/2_2.png) [@micael.gallego](https://openvidu.discourse.group/u/micael.gallego)\ **Post date:** [May 15, 2020, 2:41pm UTC](https://openvidu.discourse.group/t/probleming-aws-deploy-2-14-0/801/2 "2020-05-15T14:41:31Z")
Hello @Rodrigo_Alcantara, Let’s see first what happen with failed deployments and then we will see how to use more powerful machines. First, review if you have a default VPC in the region you try to deploy OpenVidu: [https://docs.openvidu.io/en/2.14.0/troubleshooting/#13-deploying-openvidu-in-aws-is-failing](https://docs.openvidu.io/en/2.14.0/troubleshooting/#13-deploying-openvidu-in-aws-is-failing) If you have one, can you follow the steps described here to see why the deployment is failing? [https://docs.openvidu.io/en/2.14.0/openvidu-pro/deployment/aws/#create\_failed-cloudformation-stack](https://docs.openvidu.io/en/2.14.0/openvidu-pro/deployment/aws/#create_failed-cloudformation-stack) ---
**Author:** ![Rodrigo\_Alcantara](https://yyz2.discourse-cdn.com/free1/user_avatar/openvidu.discourse.group/rodrigo_alcantara/32/437_2.png) [@Rodrigo\_Alcantara](https://openvidu.discourse.group/u/Rodrigo_Alcantara)\ **Post date:** [May 15, 2020, 4:32pm UTC](https://openvidu.discourse.group/t/probleming-aws-deploy-2-14-0/801/3 "2020-05-15T16:32:20Z")
Thanks for the speed in the response, We already have a default VPC, we did the operation ignoring the rollback, however, we are not being able to access via SSH to forward the log, we are using PUTTY, it requests login, but we were unable to access. ---
**Author:** ![micael.gallego](https://yyz2.discourse-cdn.com/free1/user_avatar/openvidu.discourse.group/micael.gallego/32/2_2.png) [@micael.gallego](https://openvidu.discourse.group/u/micael.gallego)\ **Post date:** [May 15, 2020, 5:34pm UTC](https://openvidu.discourse.group/t/probleming-aws-deploy-2-14-0/801/4 "2020-05-15T17:34:06Z")
Can you see the EC2 instance in AWS console? Do you select ssh keys when creating the machine? I you are not able to connect using Putty, maybe you can connect using EC2 Instance Connect (browser-based SSH connection): [https://medium.com/jerrynotes/ec2-instance-connect-browser-based-ssh-connection-on-aws-console-97813b417204](https://medium.com/jerrynotes/ec2-instance-connect-browser-based-ssh-connection-on-aws-console-97813b417204) Just use “ubuntu” instead of " root" in the “user name”. Regards. ---
**Author:** ![Rodrigo\_Alcantara](https://yyz2.discourse-cdn.com/free1/user_avatar/openvidu.discourse.group/rodrigo_alcantara/32/437_2.png) [@Rodrigo\_Alcantara](https://openvidu.discourse.group/u/Rodrigo_Alcantara)\ **Post date:** [May 15, 2020, 8:13pm UTC](https://openvidu.discourse.group/t/probleming-aws-deploy-2-14-0/801/5 "2020-05-15T20:13:29Z")
We send the log by email as requested. Atenciosamente, ---
**Author:** ![msalomon](https://yyz2.discourse-cdn.com/free1/user_avatar/openvidu.discourse.group/msalomon/32/484_2.png) [@msalomon](https://openvidu.discourse.group/u/msalomon)\ **Post date:** [June 26, 2020, 7:54pm UTC](https://openvidu.discourse.group/t/probleming-aws-deploy-2-14-0/801/6 "2020-06-26T19:54:20Z")
Hello Rodrigo, I have a similiar situation here in Chile and I build my app with the openvidu node.js example, so if you still needing help, I can help you. Personally I have a bad experience with 2.14, so I roll back to 2.12, but my app works in 2.14 too.