NumericNotEqualsIfExists

compares a number in a request to a list of numbers in your policy.

To match a request, the context key can be absent, but if present it must NOT match any of the numbers in your policy.

You can NOT use policy variables in the value of this operator.

So you know

NumericNotEqualsIfExists behaves exactly the same as NumericNotEquals. "Negative" operators such as NumericNotEquals already match requests when the key is not present, so the IfExists suffix has no effect. There is no harm in adding IfExists — it arguably makes the intent clearer.

NumericNotEqualsIfExists in an Allow Statement

Simulate in IAM Simulate

Policy Condition	Request Context	Result
"NumericNotEqualsIfExists": { "s3:max-keys": [ "10", "100" ] }	`s3:max-keys: null`	✓ Allowed Assuming no explicit Deny elsewhere
"NumericNotEqualsIfExists": { "s3:max-keys": [ "10", "100" ] }	`s3:max-keys: 15`	✓ Allowed Assuming no explicit Deny elsewhere
"NumericNotEqualsIfExists": { "s3:max-keys": [ "10", "100" ] }	`s3:max-keys: 10`	− Not Allowed Statement does not apply

NumericNotEqualsIfExists in a Deny Statement

Simulate in IAM Simulate

Policy Condition	Request Context	Result
"NumericNotEqualsIfExists": { "s3:max-keys": [ "10", "100" ] }	`s3:max-keys: null`	✕ Denied
"NumericNotEqualsIfExists": { "s3:max-keys": [ "10", "100" ] }	`s3:max-keys: 15`	✕ Denied
"NumericNotEqualsIfExists": { "s3:max-keys": [ "10", "100" ] }	`s3:max-keys: 10`	− Not Denied May be allowed by another statement

NumericNotEqualsIfExists

NumericNotEqualsIfExists in an Allow Statement

NumericNotEqualsIfExists in a Deny Statement

See Act in your environment