General rules considerations

When setting up rules for Cloudlets, keep the following in mind:

CategoryConsideration
Rule evaluation
  • Cloudlets rules are evaluated from first to last, and the first match wins.

  • As a best practice, order your rules so that the ones that will exclude the most incoming requests are towards the top of the list.

  • If an incoming request doesn't trigger a rule, then the Cloudlet does not execute. The request is then evaluated against the property rules.

  • Cloudlets policies do not have child rules.

  • You can add 5000 rules to a Cloudlets policy.

  • Note: If your rules aren't working as expected before the 5000 limit, try running the Policy Analysis Tool first. Contact support if you can't resolve the issue. You may have hit a cost limit.
    Match rules
  • All match types support negation.

  • If you have multiple match criteria in a rule, the criteria are all part of a single logical AND operator.

  • ELSE statements aren't supported.
  • Versioning
  • When you create a new policy, the system automatically creates version 1 of the policy. This version is empty: it has no description or rules.

  • When cloning a policy, version 1 of the new policy includes rules from the most recent version of the cloned policy.
  • Character limitationsYou can't use these characters with Cloudlets rules:

    < > @ " \ [ ] ^ ` { | } { | } ยก ยข ยฃ ยค

    ยฅ ยฆ ยง ยจ ยฉ ยช ยซ ยฌ ' ยฎ ยฏ ยฐ ยฑ ยฒ ยณ ยด ยต ยถ ยท

    ยธ ยน ยน ยฐ " ยผ ยฝ ยพ ยฟ ร€ ร ร‚ รƒ ร„ ร… ร† ร‡ รˆ ร‰

    รŠ ร‹ รŒ ร รŽ ร ร ร‘ ร’ ร“ ร” ร• ร– ร— ร˜ ร™ รš ร› รœ

    ร รž รŸ ร  รก รข รฃ รค รฅ รฆ รง รจ รฉ รช รซ รฌ รญ รฎ รฏ

    รฐ รฑ รฒ รณ รด รต รถ รท รธ รน รบ รป รผ รฝ รพ รฟ