AMI /etc/hosts, hostname

[ett]

Successfully! Thank you very much!

# iptables -I INPUT 14 -p tcp --dport 8084 -j ACCEPT (# iptables -F INPUT is same result)
This must be done on every server which origins and edges, right?

By the way, is Web Call Server 5 AMI the cause?

 

[Max]

Yes, on every server. The port is specified in security group rules for the currently published AMI.

 

[ett]

I see. I basically want to control using security groups, so I decided to do this.

# CloudFormation
    Type: AWS::EC2::Instance
    Properties:
        UserData:
          Fn::Base64: |
            /sbin/iptables --flush
            /sbin/service iptables save
            /sbin/service iptables restart
            /sbin/service webcallserver update 597 yes

I appreciate your continuous support.

 

[ett]

I'm sorry, there was one obscure point left in this thread.
About this.

# Origin EU ( = o-eu1.flashponer.com :: The cdn_point_of_entry on the other five servers references this.)

In https://flashphoner.com/dynamic-cdn-for-low-latency-webrtc-streaming/

https://flashphoner.com/wp-content/uploads/2019/11/Dynamic_CDN_Low_Latency_WebRTC_Streaming_eu_us_scheme.png

Edge 1 US
1 cdn_enabled=true
2 cdn_ip=e-us1.flashphoner.com
3 cdn_point_of_entry=o-eu1.flashponer.com
4 cdn_nodes_resolve_ip=false
5 cdn_role=edge

Is it correct that the value of the Edge 1 US's cdn_point_of_entry is o-eu1.flashponer.com instead of o-us1.flashponer.com?
I haven't tried it, but I don't think it will look like the figure.
This is the last question in this thread. Thank you.

 

[Max]

Is it correct that the value of the Edge 1 US's cdn_point_of_entry is o-eu1.flashponer.com instead of o-us1.flashponer.com?

Yes, this is correct. Origin 1 EU is CDN entry point for all the CDN nodes in this example. We mentioned above that this means the first node used to connect a new (or restarted) server to CDN.

 

[ett]

Thank you again for your clear response.

(Responding requires attention to SPOF)
I found that to keep the application config immutable, I only had to register one DNS record for the entire CDN.
All other servers can be retrieved via the REST API.