Back to all operators

NotIpAddressIfExists

NotIpAddressIfExists

compares an IP address in a request to a list of CIDR strings in your policy.

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

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

So you know

NotIpAddressIfExists behaves exactly the same as NotIpAddress. "Negative" operators such as NotIpAddress 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.

NotIpAddressIfExists in an Allow Statement

Simulate in IAM Simulate
Policy ConditionRequest ContextResult
"NotIpAddressIfExists": {
  "aws:SourceIp": [
    "170.64.0.0/16",
    "2001:4860:4860::8888/32"
  ]
}
aws:SourceIp: null✓ Allowed Assuming no explicit Deny elsewhere
"NotIpAddressIfExists": {
  "aws:SourceIp": [
    "170.64.0.0/16",
    "2001:4860:4860::8888/32"
  ]
}
aws:SourceIp: 10.0.14.32✓ Allowed Assuming no explicit Deny elsewhere
"NotIpAddressIfExists": {
  "aws:SourceIp": [
    "170.64.0.0/16",
    "2001:4860:4860::8888/32"
  ]
}
aws:SourceIp:
   170.64.109.25		− Not Allowed Statement does not apply

NotIpAddressIfExists in a Deny Statement

Simulate in IAM Simulate
Policy ConditionRequest ContextResult
"NotIpAddressIfExists": {
  "aws:SourceIp": [
    "170.64.0.0/16",
    "2001:4860:4860::8888/32"
  ]
}
aws:SourceIp: null✕ Denied 
"NotIpAddressIfExists": {
  "aws:SourceIp": [
    "170.64.0.0/16",
    "2001:4860:4860::8888/32"
  ]
}
aws:SourceIp: 10.0.14.32✕ Denied 
"NotIpAddressIfExists": {
  "aws:SourceIp": [
    "170.64.0.0/16",
    "2001:4860:4860::8888/32"
  ]
}
aws:SourceIp:
   170.64.109.25		− Not Denied May be allowed by another statement

See Act in your environment

Watch how structural hardening works in practice.

Book a demo
Get a free assessment