By using AWS re:Post, you agree to the Terms of Use

is IVS trailing pathname is fixed?

0

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?

asked a year ago7 views
1 Answers
0

Currently, IVS supports the RTMPS protocol for ingest. Because of this, it is safe to build the ingest server by joining “rtmps://<IVS-ingest-server>: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://<IVS-ingest-server>:443/app/<IVS-stream-key>

More information on Encoder Settings can be found https://docs.aws.amazon.com/ivs/latest/userguide/encoder-config.html#encoder-config-settings

answered a year ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions