Bxdty

I am trying to create an IAM user for the AWS Console with permission to list and perform action on only 1 instance.

So I have a total of 6 Instances and I tried hiding 5 of them via IAM Policies by adding the below policy:

Breakdown

1. First took all the permissions away

2. Added permission to only one instance

    {

    "Statement": [

        {

            "Effect": "Deny",

            "Action": "*",

            "Resource": "*",

            "Condition": {

                "condition": {}

            }

        },

        {

            "Effect": "Allow",

            "Action": "*",

            "Resource": "arn:aws:ec2:us-east-1:123456789012:instance/i-0123456789abcdef",

            "Condition": {

                "condition": {}

            }

        }

    ]

}

This works for the 1st part only ie Denying to all Instances.
The 2nd part doesn't seem to work.

Don't the permissions work like that? Any help would be appreciated.

Your current policy would work in the AWS-CLI, e.g. aws ec2 stop-instance should work.

However to actually use the web console you need a few more read-only permissions because the console tries to list and describe all the instances to build the list.

You may need at least ec2:DescribeInstances to get a basic half-broken list.

If you only care about preventing that IAM user from modifying other instances you can give him a read-only access with ec2:Describe* - that should make the console usable while preventing him from modifying any non-permitted instances.

I'm not aware of a way to restrict the listing of instances only to the one he can work with, he will probably see them all but can only manage that single one.

Hope that helps :)

You have to deny all, but in your condition, use ArnNotEquals "arn:aws:ec2:us-east-1:123456789012:instance/i-0123456789abcdef"

This will basically deny all other instance that does not have the same ARN as the instance that you want to be allowed.

See https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_elements_condition_operators.html#Conditions_ARN for more information

Thank you MLu and Sharuzzaman Ahmat Raslan!

Your inputs really helped me to get this done.
I am adding the summary of what I did below for others in case:

1. First, need to make sure the right policy is attached to the user
   group or in my case, the right policy is detached. The user had no
   EC2 access.


2. 
   

   Next, I used the Inline Policy to add access. I added the below policy which, as mentioned by MLu would allow not stop listing the instances but will not allow updating of the other instances

   
   
   

   {
   "Version": "2012-10-17",
   "Statement": [
   {
   "Effect": "Allow",
   "Action": "ec2:Describe*",
   "Resource": ""
   },
   {
   "Effect": "Allow",
   "Action": "",
   "Resource": "arn:aws:ec2:us-east-1:1234567890123:instance/i-xxxxxxxxxxxxxxxxx"
   }
   ]
   }

   
   

Hope this helps someone stuck to save some time.