IAM Tools
Back to All Operators

DateNotEqualsIfExists

DateNotEqualsIfExists

DateNotEqualsIfExists compares a datetime in a request to a list of datetimes in your policy. Datetime comparisons compare down to the second; so for everything except the precise second specified in your policy will match the condition.

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

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

So you know:

DateNotEqualsIfExists behaves exactly the same as DateNotEquals. "Negative" operators such as DateNotEquals already match requests if the key is not present so the IfExists suffix has no effect.

There is no harm in adding IfExists to DateNotEquals; it probably makes the intent more clear. We know you already knew this, but put this message in for everyone else. 😉

DateNotEqualsIfExists in an Allow Statement

Given the Policy Condition: 
"DateNotEqualsIfExists": {
  "aws:CurrentTime": [
    "2011-05-03T00:00:00Z",
    "2012-10-17T00:00:00Z"
  ]
}
When the Request Context has:
aws:CurrentTime: null
Then the result is:
Allowed Allowed Assuming no explicit Deny elsewhere
Given the Policy Condition: 
"DateNotEqualsIfExists": {
  "aws:CurrentTime": [
    "2011-05-03T00:00:00Z",
    "2012-10-17T00:00:00Z"
  ]
}
When the Request Context has:
aws:CurrentTime:
   2021-07-05T00:00:00Z
Then the result is:
Allowed Allowed Assuming no explicit Deny elsewhere
Given the Policy Condition: 
"DateNotEqualsIfExists": {
  "aws:CurrentTime": [
    "2011-05-03T00:00:00Z",
    "2012-10-17T00:00:00Z"
  ]
}
When the Request Context has:
aws:CurrentTime:
   2011-05-03T00:00:00Z
Then the result is:
Not Allowed Not Allowed Statement does not apply

DateNotEqualsIfExists in a Deny Statement

Given the Policy Condition: 
"DateNotEqualsIfExists": {
  "aws:CurrentTime": [
    "2011-05-03T00:00:00Z",
    "2012-10-17T00:00:00Z"
  ]
}
When the Request Context has:
aws:CurrentTime: null
Then the result is:
Denied Denied
Given the Policy Condition: 
"DateNotEqualsIfExists": {
  "aws:CurrentTime": [
    "2011-05-03T00:00:00Z",
    "2012-10-17T00:00:00Z"
  ]
}
When the Request Context has:
aws:CurrentTime:
   2021-07-05T00:00:00Z
Then the result is:
Denied Denied
Given the Policy Condition: 
"DateNotEqualsIfExists": {
  "aws:CurrentTime": [
    "2011-05-03T00:00:00Z",
    "2012-10-17T00:00:00Z"
  ]
}
When the Request Context has:
aws:CurrentTime:
   2011-05-03T00:00:00Z
Then the result is:
Not Denied Not Denied May be allowed by another statement