Skip to content

Commit 98c4281

Browse files
authored
Merge pull request #196615 from AbdullahBell/DDoSProtectionArchitecture
Updated DDoS Protection Reference Architectures.
2 parents 4bd168c + de8ed2d commit 98c4281

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

articles/ddos-protection/ddos-protection-reference-architectures.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ author: aletheatoh
66
ms.service: ddos-protection
77
ms.topic: article
88
ms.workload: infrastructure-services
9-
ms.date: 01/19/2022
9+
ms.date: 04/29/2022
1010
ms.author: yitoh
1111
ms.custom: fasttrack-edit
1212
---
@@ -16,7 +16,7 @@ ms.custom: fasttrack-edit
1616
DDoS Protection Standard is designed [for services that are deployed in a virtual network](../virtual-network/virtual-network-for-azure-services.md). The following reference architectures are arranged by scenarios, with architecture patterns grouped together.
1717

1818
> [!NOTE]
19-
> Protected resources include public IPs attached to an IaaS VM, Load Balancer (Classic & Standard Load Balancers), Application Gateway (including WAF) cluster, Firewall, Bastion, VPN Gateway, Service Fabric or an IaaS based Network Virtual Appliance (NVA). Protection also covers public IP ranges brought to Azure via Custom IP Prefixes (BYOIPs). PaaS services (multitenant), which includes Azure App Service Environment for Power Apps or API management in a virtual network with a public IP, are not supported at present.
19+
> Protected resources include public IPs attached to an IaaS VM (except for single VM running behind a public IP), Load Balancer (Classic & Standard Load Balancers), Application Gateway (including WAF) cluster, Firewall, Bastion, VPN Gateway, Service Fabric or an IaaS based Network Virtual Appliance (NVA). Protection also covers public IP ranges brought to Azure via Custom IP Prefixes (BYOIPs). PaaS services (multi-tenant), which includes Azure App Service Environment for Power Apps or API management in a virtual network with a public IP, are not supported at present.
2020
2121
## Virtual machine (Windows/Linux) workloads
2222

@@ -38,10 +38,10 @@ There are many ways to implement an N-tier architecture. The following diagram s
3838
![Diagram of the reference architecture for an application running on Windows N-tier](./media/ddos-best-practices/image-10.png)
3939

4040
In this architecture, DDoS Protection Standard is enabled on the virtual network. All public IPs in the virtual network get DDoS protection for Layer 3 and 4. For Layer 7 protection, deploy Application Gateway in the WAF SKU. For more information on this reference architecture, see
41-
[this article](/azure/architecture/reference-architectures/virtual-machines-windows/n-tier).
41+
[Windows N-tier application on Azure](/azure/architecture/reference-architectures/virtual-machines-windows/n-tier).
4242

4343
> [!NOTE]
44-
> Scenarios in which a single VM is running behind a public IP are not supported.
44+
> Scenarios in which a single VM is running behind a public IP are not supported. DDoS mitigation may not initiate instantaneously when a DDoS attack is detected. As a result a single VM deployment that can’t scale out will go down in such cases.
4545
4646
### PaaS web application
4747

@@ -52,11 +52,11 @@ A standby region is set up for failover scenarios.
5252

5353
Azure Traffic Manager routes incoming requests to Application Gateway in one of the regions. During normal operations, it routes requests to Application Gateway in the active region. If that region becomes unavailable, Traffic Manager fails over to Application Gateway in the standby region.
5454

55-
All traffic from the internet destined to the web application is routed to the [Application Gateway public IP address](../application-gateway/configure-web-app.md) via Traffic Manager. In this scenario, the app service (web app) itself is not directly externally facing and is protected by Application Gateway.
55+
All traffic from the internet destined to the web application is routed to the [Application Gateway public IP address](../application-gateway/configure-web-app.md) via Traffic Manager. In this scenario, the app service (web app) itself is not directly externally facing and is protected by Application Gateway.
5656

5757
We recommend that you configure the Application Gateway WAF SKU (prevent mode) to help protect against Layer 7 (HTTP/HTTPS/WebSocket) attacks. Additionally, web apps are configured to [accept only traffic from the Application Gateway](https://azure.microsoft.com/blog/ip-and-domain-restrictions-for-windows-azure-web-sites/) IP address.
5858

59-
For more information about this reference architecture, see [this article](/azure/architecture/reference-architectures/app-service-web-app/multi-region).
59+
For more information about this reference architecture, see [Highly available multi-region web application](/azure/architecture/reference-architectures/app-service-web-app/multi-region).
6060

6161
## Mitigation for non-web PaaS services
6262

0 commit comments

Comments
 (0)