Edge IP Binding (EIPB) lets you deliver traffic from a small, static set of IP addresses in a scalable manner. You can add EIPB to accomplish the following:
Support zero-rated billing. Are you looking to offer specific traffic at no cost to end users, or prevent specific delivery from counting against a data cap? More on this below.
Identify content provider traffic based on the source IP. This helps when you can't perform a deep packet inspection.
Provide a single or a limited number of source IP addresses. This would help if your infrastructure systems are too complex and need a single or very limited number of source IPs.
Eliminate frequent updates to IP address ranges. This applies if your business support or operations support systems can't handle frequent updates.
Provide simplicity and scale. This can help remove the need for additional domains or additional IPs.
In addition to "EIPB," Edge IP Binding is also sometimes referred to as "EIP" or "EIPBinding."
You add EIPB in Property Manager by enabling it in a property hostname to edge hostname association in your Download Delivery property. However, there are other considerations and requirements, all of which are covered in the Edge IP Binding documentation.
You also have access to the Use Case-based Edge Mapping feature when setting up these associations. You can't apply it and Edge IP Binding in the same property hostname.
Updated about 1 year ago