The origin sites protection can prevent your origin against light-traffic HTTP flood and Web attacks, but cannot defend against heavy traffic DDoS attacks. In addition, it does not prevent DDoS attacks directly targeting the origin through traffic that bypasses Anti-DDoS Pro, which may even throw the origin IP address into the black hole.
This document describes methods and principles for different scenarios to protect your origin sites under Anti-DDoS Pro.
Select and apply the method best suitable to your architecture.
Under this architecture, visitors’ source IP addresses that send requests to ECS and non-Alibaba cloud origins are converted to Anti-DDoS Pro back-to-source IP addresses.
You can use the origin’s security software (such as iptables and firewall), to only allow Anti-DDoS Pro back-to-source IP addresses, and block all other IP addresses.
Under this architecture, the IP address that sends requests to ECS becomes SLB’s IP address.
We recommend that you use SLB’s whitelist to only allow Anti-DDoS Pro to access SLB. For more information about whitelist settings, see Configure a whitelist.
Under this architecture, the IP address that sends requests to ECS becomes WAF or Alibaba Cloud CDN’s IP address.
Whenever possible, we recommend that you configure relevant policies on WAF and Alibaba Cloud CDN, and configure origin policies based on the back-to-source IP addresses of WAF or Alibaba Cloud CDN.
Origin sites protection is not necessary for layer-4 forwarding. Because the attackers can always bypass Anti-DDoS Pro and directly attack the origin, which may bring congestion or trigger the back hole. Origin protection does not work in this case.
Follow these steps to set up the security group for an ECS origin:
Log on to the ECS console, and go to Network & Security > Security Group.
Select the target region (a security group can only be applied to ECS instances within the same region), and click Create Security Group.
Specify Security Group Name, Description, and Network Type, and then click OK.
Click Configure Rules under the Actions column of the newly added security group, and then click Add Security Group Rules.
Assume that the Anti-DDoS Pro IP segment is
220.127.116.11/24, you can add the security group rules as shown in the following figure.
- You can only add one IP address or IP segment in the Authorization Object field at one time. If you have more than one IP address or IP segment, you must add a corresponding rule for each of them.
- When the same authorization object matches multiple rules, the rule with the highest Priority overrides the rest of the rules.
Follow Step 4 to 5 to add security group rules for all Anti-DDoS Pro back-to-source IP segments to allow access from Anti-DDoS Pro.
Add a security group rule to reject access from all IP addresses, and assign a lower priority (less than 10 in this example) to this rule.
When the security group rules are configured, assign this security group to the ECS instance that needs to allow access from the Anti-DDoS Pro back-to-source IP addresses. You can click Manage Instances under the Actions column of the security group, and then click Add an ECS Instance to add this ECS instance to the security group.