DateEquals

DateEquals

DateEquals compares a datetime in a request to a list of datetimes in your policy. Datetime comparisons compare down to the second; so for DateEquals to match, the time must match exactly.

To match a request, the context key must exist in the request and must match at least one of the datetimes in your policy.

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

DateEquals in an Allow Statement

Given the Policy Condition:
"DateEquals": {
  "aws:CurrentTime": [
    "2011-05-03T00:00:00Z",
    "2012-10-17T00:00:00Z"
  ]
}
When the Request Context has:
aws:CurrentTime: null
Then the result is:
Not Allowed Not Allowed Statement does not apply
Given the Policy Condition:
"DateEquals": {
  "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:
Allowed Allowed Assuming no explicit Deny elsewhere
Given the Policy Condition:
"DateEquals": {
  "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:
Not Allowed Not Allowed Statement does not apply

DateEquals in a Deny Statement

Given the Policy Condition:
"DateEquals": {
  "aws:CurrentTime": [
    "2011-05-03T00:00:00Z",
    "2012-10-17T00:00:00Z"
  ]
}
When the Request Context has:
aws:CurrentTime: null
Then the result is:
Not Denied Not Denied May be allowed by another statement
Given the Policy Condition:
"DateEquals": {
  "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:
Denied Denied
Given the Policy Condition:
"DateEquals": {
  "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:
Not Denied Not Denied May be allowed by another statement