Virtual Private Cloud pricing
Virtual Private Cloud usage is rated by the pricing policy described in this section.
Note
Currency of Service rates (prices) depends on the company you made a contract with:
- Prices in US dollars are applicable to customers of Iron Hive doo Beograd (Serbia).
- Prices in Russian roubles are applicable to customers of Yandex.Cloud LLC.
What goes into the cost of using VPC
In VPC, you pay for the hourly use of public IP addresses.
The first 100 GB of outgoing traffic are provided free of charge every month.
After you've used up your free service amounts, you will be charged at the applicable rate. The unused balance of free services is reset at the end of the month.
VPC pricing
Public IP addresses
A public IP address can be in one of the following two states:
- Active: When a dynamic or static public IP address is linked to a running cloud resource.
- Inactive: When a static public IP address is not linked to a cloud resource or is linked to a stopped resource.
All prices are shown without VAT.
Service | Cost per hour |
---|---|
Public IP address | $0.001920 |
Reserving an inactive public static IP address | $0.002480 |
The cost of an inactive public static address is calculated by adding the cost of a public IP address to the cost of reserving an inactive public static IP address.
For example, the cost of an inactive public static address will be:
$0.001920 + $0.002480 = $0.004400
Total: $0.004400 per hour.
Where:
- $0.001920 is the cost of using a public IP address per hour.
- $0.002480 is the cost of reserving an inactive public static IP address for an hour.
NAT gateways
You will be charged per hour of NAT gateway usage and for outgoing traffic via the gateway. Charges will apply as soon as you add a gateway to a route table.
Resource category | Cost of 1 hour of usage per gateway (without VAT) |
---|---|
NAT gateway | $0.00288 |
Outgoing traffic via NAT gateways
Outgoing traffic via a NAT gateway exceeding 100 GB per month is billable.
Please note that traffic transmitted via a NAT gateway is charged separately from other outgoing traffic but according to the same pricing policy.
For example:
If you transmit 110 GB of outgoing traffic via a NAT gateway and 5 GB of outgoing traffic using other ways per month, you pay for 10 GB of the outgoing traffic sent via the NAT gateway.
If you transmit 110 GB of outgoing traffic via a NAT gateway and 105 GB of outgoing traffic using other ways per month, you pay for 10 GB of the outgoing traffic sent via the NAT gateway and 5 GB of the other outgoing traffic.
The first 100 GB of outgoing traffic via NAT gateway are provided free of charge every month.
The minimum billing unit is 1 MB.
Resource category | Cost of 1 GB |
---|---|
Outgoing traffic via NAT gateway, first 10 GB per month | Free |
Outgoing traffic via NAT gateway, over 10 GB per month | $0.012240 |
Using security groups
Security groups can be used free of charge.
Egress traffic
All prices are net of VAT.
Note
You are charged for outgoing traffic from public IPs, including when public IPs are used for internal Yandex Cloud traffic, except for accessing Yandex Object Storage, Yandex Cloud Backup, and Yandex Cloud CDN. To avoid paying for outgoing traffic within your cloud, use internal IPs.
When using the service, you pay for traffic from Yandex Cloud to the internet. Traffic between Yandex Cloud services and incoming internet traffic are free of charge.
The first 100 GB of outgoing traffic are provided free of charge every month.
The minimum billing unit is 1 MB.
Resource category | Cost of 1 GB |
---|---|
Outgoing traffic via NAT gateway, first 10 GB per month | Free |
Outgoing traffic via NAT gateway, over 10 GB per month | $0.012240 |
Yandex DDoS Protection pricing
All prices are shown without VAT.
Service | Rate for 1 GB of traffic after filtering |
---|---|
Filtering incoming traffic to a public IP address with DDoS protection | $0.019440 |
Filtered traffic is incoming traffic that the DDoS Protection filtering system passes to the user's cloud resources. Only filtered traffic is charged.
For example, let's assume a user's VM was subject to a typical 10 Gbps DDoS attack generating 75 GB of incoming traffic. During the attack, the user downloaded 2 GB of filtered files from the internet to the VM. When the attack ended, the user downloaded another 2 GB of useful files.
In this case, only 4 GB of filtered traffic are charged: 2 GB that DDoS Protection passed to cloud resources during the attack, and 2 GB downloaded after the attack. Malicious traffic is filtered out and not charged.