> For the complete documentation index, see [llms.txt](https://aws-gcr-wwso-security.gitbook.io/an-quan-zui-jia-shi-jian/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://aws-gcr-wwso-security.gitbook.io/an-quan-zui-jia-shi-jian/1.-iam-shen-fen-shi-bie-yu-fang-wen-kong-zhi/xin-shou-qi-bu/ru-he-xie-condition/yun-xu-mou-ge-qing-qiu-zhe-cao-zuo-arnlikearnlikeifexists.md).

# 允许某个请求者操作 - ArnLike/ArnLikeIfExists

### ArnLike

`ArnLike` compares an ARN in a request to a list of ARN patterns in your policy. The policy values can include asterisks (\*) to match multiple characters and question marks (?) to match a single character within an ARN segement. Wildcards cannot be used to span ARN segment, so the partition, service, region, account, and resource must all be present in your policy value, even if they are all wildcards. The comparision is case sensitive.

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

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

#### ArnLike in an <mark style="color:green;">Allow</mark> Statement

<table data-full-width="true"><thead><tr><th width="408">Policy Condition</th><th>Request Context</th><th>Result</th></tr></thead><tbody><tr><td><pre><code>"ArnLike": {
  "aws:PrincipalArn": [
    "arn:aws:iam::*:role/*",
    "arn:aws:ec2:*:*:instance/i-?????"
  ]
}
</code></pre></td><td><code>aws:PrincipalArn: null</code></td><td><img src="https://iam.cloudcopilot.io/_astro/unknown.4jslFilM_ZFyvUV.svg" alt="Not Allowed"> Not AllowedStatement does not apply</td></tr><tr><td><pre><code>"ArnLike": {
  "aws:PrincipalArn": [
    "arn:aws:iam::*:role/*",
    "arn:aws:ec2:*:*:instance/i-?????"
  ]
}
</code></pre></td><td><code>aws:PrincipalArn:</code><br>   <code>arn:aws:iam::123456789012:role/AdminRole</code></td><td><img src="https://iam.cloudcopilot.io/_astro/allow.BKwnWDMp_Z2m9B7U.svg" alt="Allowed"> AllowedAssuming no explicit Deny elsewhere</td></tr><tr><td><pre><code>"ArnLike": {
  "aws:PrincipalArn": [
    "arn:aws:iam::*:role/*",
    "arn:aws:ec2:*:*:instance/i-?????"
  ]
}
</code></pre></td><td><code>aws:PrincipalArn:</code><br>   <code>arn:aws:iam::123456789012:user/User</code></td><td><img src="https://iam.cloudcopilot.io/_astro/unknown.4jslFilM_ZFyvUV.svg" alt="Not Allowed"> Not AllowedStatement does not apply</td></tr></tbody></table>

### ArnLikeIfExists

`ArnLikeIfExists` compares an ARN in a request to a list of ARN patterns in your policy. The policy values can include asterisks (\*) to match multiple characters and question marks (?) to match a single character within an ARN segement. Wildcards cannot be used to span ARN segment, so the partition, service, region, account, and resource must all be present in your policy value, even if they are all wildcards. The comparision is case sensitive.

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

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

#### ArnLikeIfExists in an Allow Statement

<table><thead><tr><th>Policy Condition</th><th>Request Context</th><th>Result</th></tr></thead><tbody><tr><td><pre><code>"ArnLikeIfExists": {
  "aws:PrincipalArn": [
    "arn:aws:iam::*:role/*",
    "arn:aws:ec2:*:*:instance/i-?????"
  ]
}
</code></pre></td><td><code>aws:PrincipalArn: null</code></td><td><img src="https://iam.cloudcopilot.io/_astro/allow.BKwnWDMp_Z2m9B7U.svg" alt="Allowed"> AllowedAssuming no explicit Deny elsewhere</td></tr><tr><td><pre><code>"ArnLikeIfExists": {
  "aws:PrincipalArn": [
    "arn:aws:iam::*:role/*",
    "arn:aws:ec2:*:*:instance/i-?????"
  ]
}
</code></pre></td><td><code>aws:PrincipalArn:</code><br>   <code>arn:aws:iam::123456789012:role/AdminRole</code></td><td><img src="https://iam.cloudcopilot.io/_astro/allow.BKwnWDMp_Z2m9B7U.svg" alt="Allowed"> AllowedAssuming no explicit Deny elsewhere</td></tr><tr><td><pre><code>"ArnLikeIfExists": {
  "aws:PrincipalArn": [
    "arn:aws:iam::*:role/*",
    "arn:aws:ec2:*:*:instance/i-?????"
  ]
}
</code></pre></td><td><code>aws:PrincipalArn:</code><br>   <code>arn:aws:iam::123456789012:user/User</code></td><td><img src="https://iam.cloudcopilot.io/_astro/unknown.4jslFilM_ZFyvUV.svg" alt="Not Allowed"> Not AllowedStatement does not apply</td></tr></tbody></table>

<br>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://aws-gcr-wwso-security.gitbook.io/an-quan-zui-jia-shi-jian/1.-iam-shen-fen-shi-bie-yu-fang-wen-kong-zhi/xin-shou-qi-bu/ru-he-xie-condition/yun-xu-mou-ge-qing-qiu-zhe-cao-zuo-arnlikearnlikeifexists.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.