Add rules by Cloudlet type
As each Cloudlet helps solve a specific business need, the rules for each Cloudlet are unique. Each Cloudlet takes a different set of actions when a request meets match criteria.
When adding Cloudlets rules, make sure you know the parts of a Cloudlets rule and how rules work in general.
Rules number limit
You can add up to 5,000 rules to a Cloudlets policy. To exceed this limit, set up multiple policies in Cloudlets Policy Manager. You'll then need to:
- Set up multiple behaviors for your Cloudlets in Property Manager
- Set up the rules for these behaviors so that they're mutually exclusive.
If your rules aren't working as expected before the 5000 limit, contact support. You may have hit a cost limit.
How to
-
Go to ☰ > CDN > Edge logic Cloudlets.
-
If not selected already, click the Manage Cloudlets Policies menu.
-
On the Cloudlet Policies screen, click the name of the policy you want to add rules to.
-
On the Policy Details screen, click the version you want to update or click Create New Version.
-
On the Version Details screen, click Add Rule.
-
Complete the fields on the Create a Rule screen:
| Field | Action |
|---|---|
| General | |
| Rule Name | Name this rule. |
| Always On | Select if the rule is always applied. |
| Start Date/Time | Enter the start date and time for the rule. |
| End Date/Time | Enter the end date and time for the rule. |
| Match definition (IF section) | |
| Match Type | Select the match type to use for this rule. Enter any operators or match criteria needed for the match type you choose. See Cloudlets match types for more information. |
| Action (THEN section) | |
| Action items available | While the General and IF sections are common for all cloudlets, the THEN sections differ. To learn about the available action items for a specific cloudlet, see the following rule tables. You can scroll down or navigate via the table of contents on the right. |
-
If you want to add another rule, click + in the match section.
-
Click Save Rule. The new rule displays first on the Version Details screen.
Cloudlets Policy Manager evaluates rules from top to bottom with the first match winning.
THEN section for each Cloudlet
Browse this section to learn about the available Action items for your cloudlet.
Application Load Balancer rules
| Field | Action |
|---|---|
| Load Balancing ID | Select the load balancing configuration you want to use when the rule is true. Once you select the ID, activation information for the selected configuration also displays. |
If using an IP address or CIDR list match, review the list of invalid IP addresses and CIDR lists.
API Prioritization rules
| Field | Action |
|---|---|
| Serve Alternate Response | Enable to send the alternate response to all requests. Enabling this option overrides the Likelihood to Origin field. Note: You configure the location of the alternate response in the API Prioritization behavior in Property Manager. |
| Likelihood to Origin | Set the likelihood, or probability, that a new request is sent to the origin, and does not receive the alternate response. Setting the slider to 0% prevents new visitors from accessing the origin, but provides origin access to existing priority users. |
You configure the location of the alternate response in the API Prioritization behavior in Property Manager.
Audience Segmentation rules
| Field | Action |
|---|---|
| Cloudlets Origin ID | Select the Conditional Origin to use when the incoming request meets the match criteria. You can either let the property decide which origin to use or choose a Conditional Origin that's already been configured and saved for the associated property. Only Conditional Origins defined within activated properties display. If a network displays in red, the property will determine the origin. One or more properties on the network do not have the selected origin defined. If no origin list is available for this field, there is no property associated with this Cloudlets policy. You can associate a Cloudlets policy with a property in the Cloudlets Policy Manager during policy activation. |
| Path and Query String | Enter the path and/or query string of the origin object to serve for the request. Type a forward slash (/) first. |
| Copy Query String | Select to include all query parameters in the rewritten URL. |
Edge Redirector rules
| Field | Action |
|---|---|
| Redirect fields | |
| Source URL | If you're not using advanced match criteria, enter the full web address for the redirect, including the protocol. Use URL encoded values for special characters, like umlauts and spaces. |
| Redirect URL | Enter the full web address to redirect the source URL to, including the protocol. Use URL encoded values for special characters, like umlauts and spaces. |
| Redirect Type | Select whether the redirect is permanent or temporary. |
| Copy Query String | Select to include all query parameters from the source URL when forming the redirect URL. |
| Relative Redirect Options | If desired, select one of the following redirect options:
|
Rules not working before the 5000 limit
You can add up to 5000 rules to a Cloudlets policy. If your rules aren't working as expected before the 5000 limit, try running the Policy Analysis Tool first. Then, contact support if you can't resolve the issue. You may have hit a cost limit.
Forward Rewrite rules
| Field | Action |
|---|---|
| Cloudlets Origin ID | Select the Conditional Origin to use for the incoming request. You can either let the property decide which origin to use or choose a Conditional Origin that's already been configured and saved for the associated property. Only Conditional Origins defined within activated properties display. If a network displays in red, the property will determine the origin. One or more properties on the network do not have the selected origin defined. If no origin list is available for this field, there is no property associated with this Cloudlets policy. You can associate a Cloudlets policy with a property in the Cloudlets Policy Manager during policy activation. |
| Path and Query String | Enter the path and/or query string of the origin object to serve for the request. Type a forward slash (/) first. |
| Copy Query String | Select to include all query parameters from the source URL. |
Phased Release rules
| Field | Action |
|---|---|
| Cloudlets Origin ID | Select the Conditional Origin to use for the incoming request. You can either let the property decide which origin to use or choose a Conditional Origin that's already been configured and saved for the associated property. Only Conditional Origins defined within activated properties display. If a network displays in red, the property will determine the origin. One or more properties on the network do not have the selected origin defined. If no origin list is available for this field, there is no property associated with this Cloudlets policy. You can associate a Cloudlets policy with a property in the Cloudlets Policy Manager during policy activation. |
| Percentage of Traffic | Select the percentage of traffic that will be sent to the Conditional Origin. |
Request Control rules
| Field | Action |
|---|---|
| Allow/Deny | Select to either allow or deny access to the website or application. Select Branded Response if you want to use a branded 403 page when denying access. |
Visitor Prioritization rules
| Field | Action |
|---|---|
| Send All to Waiting Room | Enable to send all traffic to the waiting room, regardless of the user's Allowed User Cookie status. Enabling this option overrides the Likelihood to Origin field. If you have previously used the Shopper Prioritization application, this field is equivalent to the probability = -1 setting. |
| Likelihood to Origin | Set the likelihood, or probability, that a new request is sent to origin, not the waiting room. Setting the slider to 0% prevents new visitors from accessing the site, but provides origin access to existing users who have a valid Allowed User Cookie. |
Allowed User Cookie
You set the Allowed User Cookie in Property Manager. It's part of the Visitor Prioritization behavior. It bypasses Visitor Prioritization for subsequent requests once a user has been allowed through to the site.
Updated 7 months ago