How to allocate consistent IP ranges for AWS MediaLive channels for whitelisting purposes?

Hi Darshan,

AWS MediaLive does not natively provide a way to assign fixed or consistent IP addresses or ranges for their channels directly. It dynamically allocates IPs from the AWS pool when you start a channel. You can work around this limitation by utilizing Elastic IPs or NAT Gateways to allocate static IP addresses for MediaLive to access external resources (such as pulling HLS streams).

If you're unable to implement the NAT Gateway solution, you could consider regularly retrieving the AWS Global IP ranges that MediaLive might use. AWS publishes the IP ranges it uses in JSON format at the following URL: https://ip-ranges.amazonaws.com/ip-ranges.json

There are no fixed elastic IPs for MediaLive Inputs, only for outputs delivering into a VPC.

One alternative is to implement an HTTPS proxy in your VPC , running on EC2 instance which can have fixed, known assigned elastic IP addresses. Your MediaLive inputs can then point to the proxy's output address.

You can automate the creation of the proxy instances & correlating channels with Lambda or CloudFormation.

MediaLive allows you to create push inputs in advance. When you create an input it will get fixed public IP that will be associated with it until you didn't delete it.

But MediaLive charges for each push input that is not in use. Only push inputs (for example, RTP PUSH, RTMP PUSH, MediaConnect, and AWS Elemental Link devices) incur a cost when idle. Pulled inputs (for example, HLS PULL and RTMP PULL) do not incur an idle resource cost. The pricing for idle resources is:

$0.01 per hour on a pro rata basis for each push input not associated with a running channel