wami-condition 0.18.0

IAM policy condition key evaluation, as used by wami
Documentation

wami-condition

IAM policy condition key evaluation — the Condition block of a policy statement, decided against a request context.

crates.io docs.rs

Extracted from wami, which uses it to decide whether a statement applies. It is published separately because deciding a condition block is a self-contained problem: you can use it against your own policy documents without adopting an identity model.

[dependencies]
wami-condition = "0.16"

What it evaluates

A condition block maps an operator to the keys it constrains:

{
  "StringEquals":   { "aws:PrincipalAccount": "123456789012" },
  "Bool":           { "aws:SecureTransport": "true" },
  "DateLessThan":   { "aws:CurrentTime": "2026-12-31T23:59:59Z" }
}

evaluate_condition_block answers whether the whole block holds for a given ConditionContext. Every operator family from the AWS condition grammar is implemented — String*, Numeric*, Date*, Bool, IpAddress, Arn*, Binary* — each with its Not and IfExists variants, and ForAllValues / ForAnyValue set qualifiers over strings and ARNs. Their numeric, date and address forms are refused at parse: no key holds a list of numbers, dates or addresses (the one list key, aws:TagKeys, holds strings).

The part that is easy to get wrong

IfExists is not "optional". StringEqualsIfExists passes when the key is absent, and is only checked when the key is present — which means adding IfExists to a Deny can turn a rule that blocked something into one that permits it. The distinction is implemented, and tested.

Likewise an absent key under a plain operator makes the condition false, not true — as in AWS, a key the request does not carry is not met.

An unreadable condition is not a false one, and a type mismatch is never false. parse_condition_block refuses an operator nobody defined (StringEqualz); an operator that cannot compare its key's declared type (StringEquals on the Boolean aws:SecureTransport, a numeric operator on a key nobody declared — compared as a string); a value its operator cannot read (an IpAddress that is no address, a Bool that is neither true nor false, "NaN" where a number is read, a list where the operator reads one value, an empty list where it reads a list). Values are read through the evaluator's own parsers, so parse and evaluation cannot disagree. An evaluation that cannot be carried out — a request value of another type than the operator compares, an element of a request list it cannot read, whatever its position — is an Err from evaluate_condition_block, never a false. Answered as false, it made the statement carrying it vanish: for a Deny, the rule meant to block an action stopped applying.

An error names what the policy's author wrote and must fix — the operator, the key, an element's position — and the kind of a value, never the value itself, neither the policy's nor the request's.

Context keys

The aws: keys are recognised natively — PrincipalArn, PrincipalAccount, PrincipalType, CurrentTime, EpochTime, SecureTransport, MultiFactorAuthPresent, MultiFactorAuthAge, RequestedRegion, ResourceArn, ResourceAccount, Referer and more, each with its declared type (keys::key_type). Any key the table does not name falls through to ConditionContext::custom_values, so your own keys work by putting them there — no registration step; such a key is compared with string operators only, since nothing declares what it holds.

License

MIT. See LICENSE.