Skip to content

Commit 316c60a

Browse files
Update understanding-pricing.md
Pulling WAF pricing references out of AGC documentation per leadership decision to re-think pricing approach.
1 parent b22c948 commit 316c60a

File tree

1 file changed

+0
-53
lines changed

1 file changed

+0
-53
lines changed

articles/application-gateway/for-containers/understanding-pricing.md

Lines changed: 0 additions & 53 deletions
Original file line numberDiff line numberDiff line change
@@ -32,14 +32,6 @@ Application Gateway for Containers consists of four billable items:
3232
- Association resource
3333
- Capacity units
3434

35-
When Web Application Firewall is enabled two more billable items are added:
36-
37-
- Web Application Firewall resource
38-
- Requests processed by WAF
39-
40-
>[!Note]
41-
>The Web Application Firewall resource is only billed once per Application Gateway for Containers resource. For example, if you have five Web Application Firewall Policies assigned to five Application Gateway for Containers' security policies, only one Web Application Firewall resource will be metered.
42-
4335
#### Application Gateway for Containers hour
4436

4537
An Application Gateway for Containers hour corresponds to the amount of time each Application Gateway for Containers parent resource is deployed. The Application Gateway for Containers resource is responsible for processing and coordinating configuration of your deployment.
@@ -180,51 +172,6 @@ Pricing calculation:
180172
* 3 Capacity Units x $0.008 x 730 hours = $17.52
181173
* Total = $124.83
182174

183-
### Example 6 - Web Application Firewall
184-
185-
This example assumes Application Gateway for Containers has load raising the number of capacity units and has a Web Application Firewall (WAF) policy reference to an Application Gateway for Containers' security policy. The WAF policy is configured with both DRS 2.1 and bot manager rulesets. This WAF policy also has four custom rules enabled which do not incur any additional charges
186-
187-
* 1 Application Gateway for Containers resource
188-
* 1 frontend resource
189-
* 1 association resource
190-
* 1 security policy resources (non-billable)
191-
* 8 capacity units
192-
* 1 WAF policy running a default ruleset and a bot manager ruleset
193-
* 4 WAF custom rules
194-
* 10 million requests processed by WAF
195-
196-
Pricing calculation:
197-
198-
* 1 Application Gateway for Containers x $0.017 x 730 hours = $12.41
199-
* 1 Frontend x $0.01 x 730 hours = $7.30
200-
* 1 Association x $0.12 x 730 hours = $87.60
201-
* 8 Capacity Units x $0.008 x 730 hours = $46.72
202-
* WAF enablement x $0.068 x 730 hours = $49.64
203-
* 10 one million requests (10) x $0.75 x 2 WAF rulesets (DRS 2.1 and Bot Manager) = $15
204-
* Total = $218.67
205-
206-
### Example 7 - Web Application Firewall - Multiple Policies
207-
208-
This example assumes Application Gateway for Containers has load raising the number of capacity units and has three Web Application Firewall (WAF) policy reference to three corresponding Application Gateway for Containers' security policies. One policy is configured with both DRS 2.1, bot manager rulesets and 3 custom rules, the other two policies only have DRS 2.1 ruleset and no custom rules.
209-
210-
* 1 Application Gateway for Containers resource
211-
* 1 frontend resource
212-
* 1 association resource
213-
* 3 security policy resources (non-billable)
214-
* 8 Capacity Units
215-
* 1 WAF policy running a default ruleset, a bot manager ruleset and three custom rules
216-
* 10 million requests processed by WAF
217-
218-
Pricing calculation:
219-
220-
* 1 Application Gateway for Containers x $0.017 x 730 hours = $12.41
221-
* 1 Frontend x $0.01 x 730 hours = $7.30
222-
* 1 Association x $0.12 x 730 hours = $87.60
223-
* 8 Capacity Units x $0.008 x 730 hours = $46.72
224-
* WAF enablement x $0.068 x 730 hours = $49.64
225-
* 10 million requests (10) x $0.75 x 2 WAF rulesets (DRS 2.1 and Bot Manager) = $15
226-
* Total = $218.67
227-
228175
## Next steps
229176

230177
See the following articles to learn more about how pricing works in Application Gateway for Containers by visiting the Application Gateway pricing pages:

0 commit comments

Comments
 (0)