[Yandex Cloud documentation](../../index.md) > [Yandex Cloud CDN](../index.md) > [Concepts](index.md) > Dedicated IP addressing

# Dedicated IP addressing of CDN resources

{% note warning %}

The dedicated IP addressing service is subject to the [Yandex Cloud CDN pricing policy](../pricing.md). The number of allocated IP addresses is [limited](limits.md#cdn-limits).

{% endnote %}

By default, multiple customers may share a single public IP address.

On request, you can [get](../operations/resources/dedicated-ip-addressing.md) a dedicated public IP address that will be used exclusively for your [CDN resources](resource.md) in Yandex Cloud CDN. Content delivery will continue through all [points of presence](points-of-presence.md).

The dedicated IP address is associated with a folder. This means, within a single folder, dedicated IP addressing will apply to all CDN resources by default, and they will all have the same IP address.

For balancing CDN resources with dedicated IP addressing, there are [BGP Anycast](https://en.wikipedia.org/wiki/Anycast) and GSLB DNS-based methods. These approaches differ from standard balancing used for resources without dedicated IP addresses. With BGP Anycast, the same IP address is announced from all CDN points of presence. This enables the system to seamlessly serve the entire network of PoPs even with a single IP address.

You may need to use dedicated IP addressing of CDN resources to:

* Have your resources [whitelisted by the Russian Ministry of Digital Development](../../overview/concepts/info-for-federal-ip-whitelist.md).
* Enhance security.
* Isolate your resources from those of other CDN users, including when you need to access resources via [security group](../../vpc/concepts/security-groups.md) settings.


#### See also {#see-also}

* [Points of presence](points-of-presence.md)
* [Configuring dedicated IP addressing of CDN resources](../operations/resources/dedicated-ip-addressing.md)