is IVS trailing pathname is fixed?

Question

I see the Ingest Server introduction:   
_An ingest server identifies a specific Amazon IVS component that receives the stream, along with an ingestion protocol (for example, RTMPS). The ingest server URL is composed of the protocol (RTMPS)_  
_rtmps://_  
_the ingestEndpoint_  
_J39sdv872cca.contribute.live-video.net_  
_the port_  
_:443_  
_and a trailing pathname._  
_/app/_  
When I create an ivs channel, I can get the ingestEndpoint. What I wonder is if the port is always 443 when I use RTMPS and the trailing pathname is "/app/"? If it's true, I can build the ingest server url by joining "rtmps://"_ingestEndpoint_":443/app/". If it's false, how can we build the ingest server url?

Answer

Currently, IVS supports the RTMPS protocol for ingest. Because of this, it is safe to build the ingest server by joining “rtmps://:443/app/” as the protocol and port number are supported. In addition to the ingest server URL, the stream key may also need to be added to the end of the URL (depending on the encoder) to form a URL with the pattern “rtmps://:443/app/”   
  
More information on Encoder Settings can be found https://docs.aws.amazon.com/ivs/latest/userguide/encoder-config.html#encoder-config-settings

is IVS trailing pathname is fixed?

Relevant content