Skip to content

Commit 4627a11

Browse files
Merge pull request #303974 from halkazwini/agc-pricing
AGC pricing
2 parents 5edef5e + 3bf3b1f commit 4627a11

File tree

1 file changed

+2
-52
lines changed

1 file changed

+2
-52
lines changed

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

Lines changed: 2 additions & 52 deletions
Original file line numberDiff line numberDiff line change
@@ -32,13 +32,8 @@ 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.
35+
> [!NOTE]
36+
> Currently, there's no additional charge to enable Web Application Firewall (WAF) on Application Gateway for Containers beyond the added capacity units required to process requests.
4237
4338
#### Application Gateway for Containers hour
4439

@@ -180,51 +175,6 @@ Pricing calculation:
180175
* 3 Capacity Units x $0.008 x 730 hours = $17.52
181176
* Total = $124.83
182177

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-
228178
## Next steps
229179

230180
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)