- Newest
- Most votes
- Most comments
Amazon IVS Real-Time Streaming added support for RTMP and RTMPS ingest in September 2024 as an alternative to using the IVS broadcast SDK. This allows publishing to IVS stages from RTMP sources like hardware encoders.
To publish to a stage using RTMPS, you need to:
- Create an ingest configuration and associate it with your stage
- Use the stream key from the ingest configuration and the RTMP endpoint from the stage
By default, the ingest configuration requires RTMPS (secure) and will reject RTMP connections. If you need to use RTMP, you must explicitly set the insecureIngest field to true in your configuration.
Since you mentioned that something changed about a month ago affecting your GoPro streaming, it's possible that:
- There might have been a security update that enforced RTMPS over RTMP
- The ingest configuration settings might have changed
- There could be compatibility issues between your GoPro encoder settings and IVS requirements
I'd recommend checking:
- Whether your ingest configuration is set to allow RTMP if that's what your GoPro uses
- If your GoPro's encoder settings match IVS requirements (H.264 codec, Baseline profile, proper IDR interval, etc.)
- That you're using the correct and current stream key and endpoint
Amazon recommends using the IVS broadcast SDK whenever possible, as they cannot guarantee the performance or compatibility of third-party solutions like hardware encoders with IVS.
Sources
IVS RTMP Publishing | Real-Time Streaming - Amazon IVS
IVS Stream Ingest | Real-Time Streaming - Amazon IVS
Amazon IVS Real-Time Streaming now supports RTMP ingest - AWS
IVS Release Notes | Real-Time Streaming - Amazon IVS
answered a year ago
Check resolution, codec and bitrate on your camera. If this is out of IVS spec your connection will be rejected: https://docs.aws.amazon.com/ivs/latest/RealTimeUserGuide/rt-stream-ingest.html
answered a year ago
Relevant content
asked a year ago
asked 2 years ago
