Need help in reading aws doc

Hello.

which stands for "", is AWS saying we can scope this action 2 ways or we have to include "AcceptAddressTransfer" action both on "elastic-ip" ARN with condition mentioned in condition block and with resource "*" for condition mention against it ?

If you set the ARN of "elastic-ip*" in the resource section, you can use "aws:RequestTag/${TagKey}" etc. listed in the "Condition keys" column.

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Effect": "Allow",
            "Action": "ec2:AcceptAddressTransfer",
            "Resource": "arn:${Partition}:ec2:${Region}:${Account}:elastic-ip/${AllocationId}",
            "Condition": {
                "StringEquals": {
                    "aws:RequestTag/test": "test"
                }
            }
        }
    ]
}

If the resource section is empty (that is, "*"), only "ec2:Region" can be set in "Condition keys".

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Effect": "Allow",
            "Action": "ec2:AcceptAddressTransfer",
            "Resource": "*",
            "Condition": {
                "StringEquals": {
                    "ec2:Region": "us-east-1"
                }
            }
        }
    ]
}

ok but when I am using aws:RequestTag with RunInstances, I am still getting access denied, here is my policy

       {
  "Version": "2012-10-17",
  "Statement": [
    {
      "Sid": "TheseActionsDontSupportResourceLevelPermissions",
      "Effect": "Allow",
      "Action": [
        "ec2:Describe*"
      ],
      "Resource": "*"
    },
    {
      "Sid": "ThisActionSupportsResourceLevelPermissionsWithInstancesButNotWithTags",
      "Effect": "Allow",
      "Action": [
        "ec2:RunInstances",
        "ec2:CreateSecurityGroup",
        "ec2:DeleteSecurityGroup",
        "ec2:AuthorizeSecurityGroup*",
        "ec2:RevokeSecurityGroup*"
      ],
      "Resource": [
        "arn:aws:ec2:us-east-1:ACCOUNT:key-pair/*",
        "arn:aws:ec2:us-east-1:ACCOUNT:security-group/*",
        "arn:aws:ec2:us-east-1:ACCOUNT:volume/*",
        "arn:aws:ec2:us-east-1::image/ami-*",
        "arn:aws:ec2:us-east-1:ACCOUNT:vpc/*"
      ]
    },
    {
      "Sid": "",
      "Effect": "Allow",
      "Action": [
        "ec2:RunInstances"
      ],
      "Resource": [
        "arn:aws:ec2:us-east-1:ACCOUNT:instance/*"
      ],
      "Condition": {
        "StringEquals": {
          "aws:RequestTag/Name": "*test*"
        }
      }
    },
    {
      "Sid": "TheseActionsSupportResourceLevelPermissionsWithInstancesAndTags",
      "Effect": "Allow",
      "Action": [
        "ec2:TerminateInstances",
        "ec2:StopInstances",
        "ec2:StartInstances"
      ],
      "Resource": "arn:aws:ec2:us-east-1:ACCOUNT:instance/*",
      "Condition": {
        "StringEquals": {
          "ec2:ResourceTag/Name": "*test*"
        }
      }
    },
    {
      "Effect": "Allow",
      "Action": [
        "sts:DecodeAuthorizationMessage",
        "cloudshell:*"
      ],
      "Resource": [
        "*"
      ]
    }
  ]
}

ok, so with elastic-ip ARN all the condition in the condition column are supported with all the condition mention in condition table against the elastic-ip ARN ? If that is the case then why RunInstance with instance ARN doesn't support condition even tho condition are mentioned in condition column ?

After removing the ec2:RunInstancesfrom statement one , I am still getting the same error.

Can someone please look into this ?