I received this error launching OpenVidu Pro using the default CF template from the marketplace:

You must specify an allocation id when mapping an address to a VPC instance 
(Service: AmazonEC2; Status Code: 400; 
Error Code: InvalidParameterCombination; 
Request ID: de9904e6-850f-477a-b675-6832ae509738)

When configured with a VPC, the following resource config fails with the above error in Cloudformation:

  MyEIP:
    Type: AWS::EC2::EIPAssociation
    Condition: NoSelfSigned
    Properties:
      InstanceId: !Ref OpenViduServer
      EIP: !Ref PublicElasticIP

According to the CF docs, EIP is only used for EC2-Classic. For VPC, AllocationID must be specified. _[1]

_{[1] https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-ec2-eip-association.html}

I worked around the issue by customizing the template to use AllocationID instead of the EIP property.

Good afternoon,
We are using AWS Cloud Formartion as a server for our Openvidu PRO project, but we are experiencing some problems, I will describe below:

1 - We only managed to have 3 Media Nodes installed (I can't create more instances).

2 - Many sections are not finished, they are keeping the sections open at all times, even without active users in the rooms.

We are using the project to transmit classes, this requires many connected students, so we are checking the Kibana graphics and the usage is not over 60% and 20% memory, even so, in some moments, I need to restart the server to clean the stuck sections

Below my configuration.

AwsInstanceTypeKMS m5.2xlarge
AwsInstanceTypeOV m5.2xlarge
FreeHTTPAccesToRecordingVideos true
KeyName conecttv
KibanaPassword ****
KibanaUser *****
LetsEncryptEmail support @…
MediaNodesStartNumber 1
MyDomainName openvidu ……
OpenViduLicense ****
OpenViduRecordingTimeOut 120
OpenViduSecret ****
OpenViduSubnet subnet-*****
OpenViduVPC vpc-2f503657
OpenViduWebhook false
OpenViduWebhookEndpoint http://my.endpoint.com
OpenViduWebhookEvents sessionCreated, sessionDestroyed, participantJoined, participantLeft, webrtcConnectionCreated, webrtcConnectionDestroyed, recordingStatusChanged, filterEventDispatched, mediaNodeStatusChanged
OpenViduWebhookHeaders -
OpenviduCDREnable false
OpenviduClusterLoadStrategy streams
OpenviduRecordingNotification all
OpenviduStreamsVideoMaxRecvBandwidth 1000
OpenviduStreamsVideoMaxSendBandwidth 1000
OpenviduStreamsVideoMinRecvBandwidth 300
OpenviduStreamsVideoMinSendBandwidth 300
OwnCertCRT -
OwnCertKEY -
PublicElasticIP 35.xxx.xxx.xx
WhichCert letsencrypt

Please help me,

Rodrigo Alcantara

The userdata script that runs on the OpenVidu node can fail if the secret has certain characters. Here's a portion of the output in /var/log/cloud-init-output.log

+ sed -i s/DOMAIN_NAME/mydomain.example.com/ group_vars/all
+ sed -i s/LETSENCRYPT_EMAIL// group_vars/all
+ sed -i s/MY_SECRET/tXfG5L+k80B19xV9lEXs3WaqqEF// group_vars/all
sed: -e expression #1, char 41: unknown option to `s'
+ echo '[Openvidu] Parameters incorrect/insufficient'
[Openvidu] Parameters incorrect/insufficient
+ exit 1

I had generated a secret with the following beforehand:

$ openssl rand -base64 21
tXfG5L+k80B19xV9lEXs3WaqqEF/

I'll choose another to workaround this issue, but I thought it was worth reporting.