ForAllValues:StringEqualsIfExists

Warning:

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

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

ForAllValues: StringEqualsIfExists

ForAllValues: StringEqualsIfExists compares a list of strings in a request to a list of strings in your policy. The comparision is case sensitive.

To match a request, the context key can be absent, but if it is present, all of the strings in the request must match at least one of the strings in your policy.

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

ForAllValues: StringEqualsIfExists in an Allow Statement

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

Given the Policy Condition:

"ForAllValues:StringEqualsIfExists": {
  "aws:TagKeys": [
    "DataClass",
    "Owner"
  ]
}

When the Request Context has:

aws:TagKeys: null

Then the result is:

Allowed Assuming no explicit Deny elsewhere

Given the Policy Condition:

"ForAllValues:StringEqualsIfExists": {
  "aws:TagKeys": [
    "DataClass",
    "Owner"
  ]
}

When the Request Context has:

aws:TagKeys: 
 - Dept
 - SIC

Then the result is:

Not Allowed Statement does not apply

Given the Policy Condition:

"ForAllValues:StringEqualsIfExists": {
  "aws:TagKeys": [
    "DataClass",
    "Owner"
  ]
}

When the Request Context has:

aws:TagKeys: 
 - DataClass
 - Dept

Then the result is:

Not Allowed Statement does not apply

Given the Policy Condition:

"ForAllValues:StringEqualsIfExists": {
  "aws:TagKeys": [
    "DataClass",
    "Owner"
  ]
}

When the Request Context has:

aws:TagKeys: 
 - DataClass

Then the result is:

Allowed Assuming no explicit Deny elsewhere

Given the Policy Condition:

"ForAllValues:StringEqualsIfExists": {
  "aws:TagKeys": [
    "DataClass",
    "Owner"
  ]
}

When the Request Context has:

aws:TagKeys: 
 - DataClass
 - Owner

Then the result is:

Allowed Assuming no explicit Deny elsewhere

Given the Policy Condition:

"ForAllValues:StringEqualsIfExists": {
  "aws:TagKeys": [
    "DataClass",
    "Owner"
  ]
}

When the Request Context has:

aws:TagKeys: 
 - DataClass
 - Owner
 - Dept

Then the result is:

Not Allowed Statement does not apply

ForAllValues: StringEqualsIfExists in a Deny Statement

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

Given the Policy Condition:

"ForAllValues:StringEqualsIfExists": {
  "aws:TagKeys": [
    "DataClass",
    "Owner"
  ]
}

When the Request Context has:

aws:TagKeys: null

Then the result is:

Denied

Given the Policy Condition:

"ForAllValues:StringEqualsIfExists": {
  "aws:TagKeys": [
    "DataClass",
    "Owner"
  ]
}

When the Request Context has:

aws:TagKeys: 
 - Dept
 - SIC

Then the result is:

Not Denied May be allowed by another statement

Given the Policy Condition:

"ForAllValues:StringEqualsIfExists": {
  "aws:TagKeys": [
    "DataClass",
    "Owner"
  ]
}

When the Request Context has:

aws:TagKeys: 
 - DataClass
 - Dept

Then the result is:

Not Denied May be allowed by another statement

Given the Policy Condition:

"ForAllValues:StringEqualsIfExists": {
  "aws:TagKeys": [
    "DataClass",
    "Owner"
  ]
}

When the Request Context has:

aws:TagKeys: 
 - DataClass

Then the result is:

Denied

Given the Policy Condition:

"ForAllValues:StringEqualsIfExists": {
  "aws:TagKeys": [
    "DataClass",
    "Owner"
  ]
}

When the Request Context has:

aws:TagKeys: 
 - DataClass
 - Owner

Then the result is:

Denied

Given the Policy Condition:

"ForAllValues:StringEqualsIfExists": {
  "aws:TagKeys": [
    "DataClass",
    "Owner"
  ]
}

When the Request Context has:

aws:TagKeys: 
 - DataClass
 - Owner
 - Dept

Then the result is:

Not Denied May be allowed by another statement