Yandex DDoS Protection in Virtual Private Cloud
Yandex DDoS Protection is a VPC component that safeguards cloud resources from DDoS attacks. DDoS Protection is provided in partnership with Curator.
Activating Yandex DDoS Protection for VM instances or network load balancers allows you to efficiently respond to attacks aiming to overwhelm the channel capacity and computing resources of your VM instances. Such attacks utilize broad bandwidth and produce a large number of packets per second. They are relatively easy to set up: attackers typically send a flood of TCP SYN packets (SYN Flood) or traffic of UDP-based application protocols, such as DNS, NTP, SSDP, CLDAP, and many more.
To prevent such attacks, DDoS Protection:
- Constantly analyzes all incoming traffic.
- Detects the above issues in the network and transport layers.
- Automatically diverts unwanted traffic when its intensity threatens the health of your service in Yandex Cloud.
DDoS protection is available for public IP addresses of VMs, network load balancers, and database hosts. You can only enable it when creating a cloud resource or reserving a static IP address. However, there are no restrictions on working with protected IP addresses: you can convert them to static and reserve them. If you stop a virtual machine with a protected dynamic address, the address will change once you restart it, but the DDoS protection will remain.
The bandwidth for malicious and legitimate traffic is not restricted. You pay for every gigabyte of the incoming legitimate traffic.
When enabling DDoS Protection, you may want to reduce MTU and TCP MSS.
Note that DDoS Protection is not designed to protect websites and mobile apps against higher-level DDoS attacks which:
- Use valid TCP connections.
- Use HTTP and HTTPS requests.
- Exploit bottlenecks in the apps under attack.
When enabling basic protection (Yandex DDoS Protection), you must configure a trigger threshold for the L3-L4 protection mechanisms. This threshold is aligned with the amount of legitimate traffic to the protected resource. To configure the threshold, contact support.
You can request protection at the application level by contacting our tech support.
Advanced protection
Advanced protection is available at OSI layers 3, 4, and 7. You can also track load and attack metrics and enable Soundwall WAF in your Curator account.
When enabling advanced protection (Advanced Yandex DDoS Protection), you should disable basic protection (Yandex DDoS Protection). After you disable the protection, the VM's public IP address will change.
To enable advanced protection, contact support or fill out this form. In your request, specify the details of the service and legitimate traffic:
Service details:
- Number of resources (websites, domains, and services) to protect.
- Whether you need to enable a web application firewall (WAF).
- Whether you need to protect encrypted resources (SSL/TLS/HTTPS) and expose the encryption protocol.
- Business-critical downtime.
Legitimate traffic details:
- Maximum incoming and outgoing application traffic.
- Maximum packet rate (PPS).
- Maximum request rate (RPS).
It will be helpful if you also attach:
- Network infrastructure chart with site locations, uplinks, and internal architecture from the boundary router to the application.
- Example traffic stats (chart images) for a 24-hour period.