ForAnyValue:StringNotEqualsIgnoreCaseIfExists

Warning:

ForAnyValue: StringNotEqualsIgnoreCaseIfExists 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: StringNotEqualsIgnoreCase instead so your coworkers don't hate you.

ForAnyValue: StringNotEqualsIgnoreCaseIfExists

ForAnyValue: StringNotEqualsIgnoreCaseIfExists compares a list of strings in a request to a list of strings in your policy. The comparision is case insensitive.

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: StringNotEqualsIgnoreCaseIfExists in an Allow Statement

Click into any of these polices and change them test how they change the result.

Given the Policy Condition:

"ForAnyValue:StringNotEqualsIgnoreCaseIfExists": {
  "aws:TagKeys": [
    "DataClass",
    "Owner"
  ]
}

When the Request Context has:

aws:TagKeys: null

Then the result is:

Not Allowed Statement does not apply

Given the Policy Condition:

"ForAnyValue:StringNotEqualsIgnoreCaseIfExists": {
  "aws:TagKeys": [
    "DataClass",
    "Owner"
  ]
}

When the Request Context has:

aws:TagKeys: 
 - dAtAcLaSs
 - Owner

Then the result is:

Not Allowed Statement does not apply

Given the Policy Condition:

"ForAnyValue:StringNotEqualsIgnoreCaseIfExists": {
  "aws:TagKeys": [
    "DataClass",
    "Owner"
  ]
}

When the Request Context has:

aws:TagKeys: 
 - Dept
 - dAtAcLaSs

Then the result is:

Allowed Assuming no explicit Deny elsewhere

Given the Policy Condition:

"ForAnyValue:StringNotEqualsIgnoreCaseIfExists": {
  "aws:TagKeys": [
    "DataClass",
    "Owner"
  ]
}

When the Request Context has:

aws:TagKeys: 
 - Dept
 - SIC

Then the result is:

Allowed Assuming no explicit Deny elsewhere

Given the Policy Condition:

"ForAnyValue:StringNotEqualsIgnoreCaseIfExists": {
  "aws:TagKeys": [
    "DataClass",
    "Owner"
  ]
}

When the Request Context has:

aws:TagKeys: 
 - Dept
 - SIC
 - dAtAcLaSs

Then the result is:

Allowed Assuming no explicit Deny elsewhere

ForAnyValue: StringNotEqualsIgnoreCaseIfExists in a Deny Statement

Click into any of these polices and change them test how they change the result.

Given the Policy Condition:

"ForAnyValue:StringNotEqualsIgnoreCaseIfExists": {
  "aws:TagKeys": [
    "DataClass",
    "Owner"
  ]
}

When the Request Context has:

aws:TagKeys: null

Then the result is:

Not Denied May be allowed by another statement

Given the Policy Condition:

"ForAnyValue:StringNotEqualsIgnoreCaseIfExists": {
  "aws:TagKeys": [
    "DataClass",
    "Owner"
  ]
}

When the Request Context has:

aws:TagKeys: 
 - dAtAcLaSs
 - Owner

Then the result is:

Not Denied May be allowed by another statement

Given the Policy Condition:

"ForAnyValue:StringNotEqualsIgnoreCaseIfExists": {
  "aws:TagKeys": [
    "DataClass",
    "Owner"
  ]
}

When the Request Context has:

aws:TagKeys: 
 - Dept
 - dAtAcLaSs

Then the result is:

Denied

Given the Policy Condition:

"ForAnyValue:StringNotEqualsIgnoreCaseIfExists": {
  "aws:TagKeys": [
    "DataClass",
    "Owner"
  ]
}

When the Request Context has:

aws:TagKeys: 
 - Dept
 - SIC

Then the result is:

Denied

Given the Policy Condition:

"ForAnyValue:StringNotEqualsIgnoreCaseIfExists": {
  "aws:TagKeys": [
    "DataClass",
    "Owner"
  ]
}

When the Request Context has:

aws:TagKeys: 
 - Dept
 - SIC
 - dAtAcLaSs

Then the result is:

Denied