General rules considerations

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

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.

  • Conditions must be unique. Rules with duplicated conditions can give unexpected results.

  • 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:

    < > @ " \ [ ] ^ ` { | } { | } ¡ ¢ £ ¤

    ¥ ¦ § ¨ © ª « ¬ ' ® ¯ ° ± ² ³ ´ µ ¶ ·

    ¸ ¹ ¹ ° " ¼ ½ ¾ ¿ À Á Â Ã Ä Å Æ Ç È É

    Ê Ë Ì Í Î Ï Ð Ñ Ò Ó Ô Õ Ö × Ø Ù Ú Û Ü

    Ý Þ ß à á â ã ä å æ ç è é ê ë ì í î ï

    ð ñ ò ó ô õ ö ÷ ø ù ú û ü ý þ ÿ