IAM Tools
Back to All Operators

ForAnyValue:StringNotEqualsIfExists

Warning:

ForAnyValue: StringNotEqualsIfExists is actively confusing. Any operator starting with ForAnyValue will ignore IfExists. IfExists is not evaluated against the entire array, it is only evaluated against a single value at a time, inside the ForAnyValue loop.

This is the kind of thing Jacob would do. Use ForAnyValue: StringNotEquals instead so your coworkers don't hate you.

ForAnyValue: StringNotEqualsIfExists

ForAnyValue: StringNotEqualsIfExists compares a list of strings in a request to a list of strings in your policy. The comparison is case sensitive.

To match a request, the context key must exist in the request and at least one string in the request must NOT match any of strings in your policy.

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

ForAnyValue: StringNotEqualsIfExists in an Allow Statement

Given the Policy Condition: 
"ForAnyValue:StringNotEqualsIfExists": {
  "aws:TagKeys": [
    "DataClass",
    "Owner"
  ]
}
When the Request Context has:
aws:TagKeys: null
Then the result is:
Not Allowed Not Allowed Statement does not apply
Given the Policy Condition: 
"ForAnyValue:StringNotEqualsIfExists": {
  "aws:TagKeys": [
    "DataClass",
    "Owner"
  ]
}
When the Request Context has:
aws:TagKeys:
 - DataClass
 - Owner
Then the result is:
Not Allowed Not Allowed Statement does not apply
Given the Policy Condition: 
"ForAnyValue:StringNotEqualsIfExists": {
  "aws:TagKeys": [
    "DataClass",
    "Owner"
  ]
}
When the Request Context has:
aws:TagKeys:
 - Dept
 - DataClass
Then the result is:
Allowed Allowed Assuming no explicit Deny elsewhere
Given the Policy Condition: 
"ForAnyValue:StringNotEqualsIfExists": {
  "aws:TagKeys": [
    "DataClass",
    "Owner"
  ]
}
When the Request Context has:
aws:TagKeys:
 - Dept
 - SIC
Then the result is:
Allowed Allowed Assuming no explicit Deny elsewhere
Given the Policy Condition: 
"ForAnyValue:StringNotEqualsIfExists": {
  "aws:TagKeys": [
    "DataClass",
    "Owner"
  ]
}
When the Request Context has:
aws:TagKeys:
 - Dept
 - SIC
 - DataClass
Then the result is:
Allowed Allowed Assuming no explicit Deny elsewhere

ForAnyValue: StringNotEqualsIfExists in a Deny Statement

Given the Policy Condition: 
"ForAnyValue:StringNotEqualsIfExists": {
  "aws:TagKeys": [
    "DataClass",
    "Owner"
  ]
}
When the Request Context has:
aws:TagKeys: null
Then the result is:
Not Denied Not Denied May be allowed by another statement
Given the Policy Condition: 
"ForAnyValue:StringNotEqualsIfExists": {
  "aws:TagKeys": [
    "DataClass",
    "Owner"
  ]
}
When the Request Context has:
aws:TagKeys:
 - DataClass
 - Owner
Then the result is:
Not Denied Not Denied May be allowed by another statement
Given the Policy Condition: 
"ForAnyValue:StringNotEqualsIfExists": {
  "aws:TagKeys": [
    "DataClass",
    "Owner"
  ]
}
When the Request Context has:
aws:TagKeys:
 - Dept
 - DataClass
Then the result is:
Denied Denied
Given the Policy Condition: 
"ForAnyValue:StringNotEqualsIfExists": {
  "aws:TagKeys": [
    "DataClass",
    "Owner"
  ]
}
When the Request Context has:
aws:TagKeys:
 - Dept
 - SIC
Then the result is:
Denied Denied
Given the Policy Condition: 
"ForAnyValue:StringNotEqualsIfExists": {
  "aws:TagKeys": [
    "DataClass",
    "Owner"
  ]
}
When the Request Context has:
aws:TagKeys:
 - Dept
 - SIC
 - DataClass
Then the result is:
Denied Denied