ForAnyValue:DateNotEqualsIfExists
Warning:
As far as we know ForAnyValue:
DateNotEqualsIfExists
can never be used because there are no
context keys available that are an array of datetimes. This is here as an example of
how it could work, but if you see this in the wild, it's probably a mistake.
It's totally possible this is a mistake on our part, if you think we got this wrong please send an email to wroooong
at cloudcopilot.io
and we'll get it fixed up.
ForAnyValue: DateNotEqualsIfExists
ForAnyValue:
DateNotEqualsIfExists
compares a list of datetimes 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 must exist in the request and at least one datetime in the request must NOT match any of datetimes in your policy.
You can NOT use policy variables in the value of this operator.
ForAnyValue: DateNotEqualsIfExists in an Allow Statement
Click into any of these polices and change them test how they change the result.
Given the Policy Condition: |
"ForAnyValue:DateNotEqualsIfExists": { "aws:NonExistent": [ "2011-05-03T00:00:00Z", "2012-10-17T00:00:00Z" ] } |
When the Request Context has: |
aws:NonExistent: null |
Then the result is: |
Not Allowed Statement does not apply |
Given the Policy Condition: |
"ForAnyValue:DateNotEqualsIfExists": { "aws:NonExistent": [ "2011-05-03T00:00:00Z", "2012-10-17T00:00:00Z" ] } |
When the Request Context has: |
aws:NonExistent: |
Then the result is: |
Not Allowed Statement does not apply |
Given the Policy Condition: |
"ForAnyValue:DateNotEqualsIfExists": { "aws:NonExistent": [ "2011-05-03T00:00:00Z", "2012-10-17T00:00:00Z" ] } |
When the Request Context has: |
aws:NonExistent: |
Then the result is: |
Allowed Assuming no explicit Deny elsewhere |
Given the Policy Condition: |
"ForAnyValue:DateNotEqualsIfExists": { "aws:NonExistent": [ "2011-05-03T00:00:00Z", "2012-10-17T00:00:00Z" ] } |
When the Request Context has: |
aws:NonExistent: |
Then the result is: |
Allowed Assuming no explicit Deny elsewhere |
Given the Policy Condition: |
"ForAnyValue:DateNotEqualsIfExists": { "aws:NonExistent": [ "2011-05-03T00:00:00Z", "2012-10-17T00:00:00Z" ] } |
When the Request Context has: |
aws:NonExistent: |
Then the result is: |
Allowed Assuming no explicit Deny elsewhere |
ForAnyValue: DateNotEqualsIfExists in a Deny Statement
Click into any of these polices and change them test how they change the result.
Given the Policy Condition: |
"ForAnyValue:DateNotEqualsIfExists": { "aws:NonExistent": [ "2011-05-03T00:00:00Z", "2012-10-17T00:00:00Z" ] } |
When the Request Context has: |
aws:NonExistent: null |
Then the result is: |
Not Denied May be allowed by another statement |
Given the Policy Condition: |
"ForAnyValue:DateNotEqualsIfExists": { "aws:NonExistent": [ "2011-05-03T00:00:00Z", "2012-10-17T00:00:00Z" ] } |
When the Request Context has: |
aws:NonExistent: |
Then the result is: |
Not Denied May be allowed by another statement |
Given the Policy Condition: |
"ForAnyValue:DateNotEqualsIfExists": { "aws:NonExistent": [ "2011-05-03T00:00:00Z", "2012-10-17T00:00:00Z" ] } |
When the Request Context has: |
aws:NonExistent: |
Then the result is: |
Denied |
Given the Policy Condition: |
"ForAnyValue:DateNotEqualsIfExists": { "aws:NonExistent": [ "2011-05-03T00:00:00Z", "2012-10-17T00:00:00Z" ] } |
When the Request Context has: |
aws:NonExistent: |
Then the result is: |
Denied |
Given the Policy Condition: |
"ForAnyValue:DateNotEqualsIfExists": { "aws:NonExistent": [ "2011-05-03T00:00:00Z", "2012-10-17T00:00:00Z" ] } |
When the Request Context has: |
aws:NonExistent: |
Then the result is: |
Denied |