AWS IAM: Restrict Console Access to only One Instance Announcing the arrival of Valued Associate #679: Cesar Manara Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern) Come Celebrate our 10 Year Anniversary!Amazon AWS IAM Policy for single VPC SubnetAmazon AWS IAM Policy based in time of dayHow can I chain AWS IAM AssumeRole API calls?How to restrict IAM policy to not allow stop/terminate an EC2 instance but can create new instances?AWS IAM role for use within a classroomHow to grant access to an SQS to a specific IAM userHow to grant IAM access to an already running EC2 intanceAmazon web service visibility restriction to instances under same accountAWS Force MFA Policy IssueAllow other AWS services to invoke Lambda using IAM

At the end of Thor: Ragnarok why don't the Asgardians turn and head for the Bifrost as per their original plan?

What does the word "veer" mean here?

How do I stop a creek from eroding my steep embankment?

Sci-Fi book where patients in a coma ward all live in a subconscious world linked together

Error "illegal generic type for instanceof" when using local classes

Why do people hide their license plates in the EU?

Can I cast Passwall to drop an enemy into a 20-foot pit?

Why do we bend a book to keep it straight?

Why was the term "discrete" used in discrete logarithm?

Extract all GPU name, model and GPU ram

What exactly is a "Meth" in Altered Carbon?

Overriding an object in memory with placement new

Why didn't this character "real die" when they blew their stack out in Altered Carbon?

List of Python versions

What does an IRS interview request entail when called in to verify expenses for a sole proprietor small business?

What causes the vertical darker bands in my photo?

How to react to hostile behavior from a senior developer?

Is it true that "carbohydrates are of no use for the basal metabolic need"?

How widely used is the term Treppenwitz? Is it something that most Germans know?

Are two submodules (where one is contained in the other) isomorphic if their quotientmodules are isomorphic?

Is pollution the main cause of Notre Dame Cathedral's deterioration?

Identifying polygons that intersect with another layer using QGIS?

If a contract sometimes uses the wrong name, is it still valid?

Should I discuss the type of campaign with my players?



AWS IAM: Restrict Console Access to only One Instance



Announcing the arrival of Valued Associate #679: Cesar Manara
Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern)
Come Celebrate our 10 Year Anniversary!Amazon AWS IAM Policy for single VPC SubnetAmazon AWS IAM Policy based in time of dayHow can I chain AWS IAM AssumeRole API calls?How to restrict IAM policy to not allow stop/terminate an EC2 instance but can create new instances?AWS IAM role for use within a classroomHow to grant access to an SQS to a specific IAM userHow to grant IAM access to an already running EC2 intanceAmazon web service visibility restriction to instances under same accountAWS Force MFA Policy IssueAllow other AWS services to invoke Lambda using IAM



.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;








2















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.

AWS Console with no permission to any instance data



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










share|improve this question




























    2















    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.

    AWS Console with no permission to any instance data



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










    share|improve this question
























      2












      2








      2








      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.

      AWS Console with no permission to any instance data



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










      share|improve this question














      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.

      AWS Console with no permission to any instance data



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







      amazon-web-services amazon-ec2 amazon-iam






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked yesterday









      ServerInsightsServerInsights

      2115




      2115




















          4 Answers
          4






          active

          oldest

          votes


















          3














          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 :)






          share|improve this answer






























            0














            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






            share|improve this answer






























              0














              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.






              share|improve this answer

























              • Where normally 4 leading spaces pre-format text/code in an itemized list you instead need to use 8 spaces

                – HBruijn
                yesterday











              • @HBruijn Thanks a lot!

                – ServerInsights
                yesterday


















              0














              Regarding hiding all instances but one from the user



              This cannot be done using IAM policies. The ec2:Describe* commands (including ec2:DescribeInstances) do not support resource-level permissions. So you can only allow or deny ec2:Describe* for everything (*). So your user can see all instances, or none.



              Regarding trying to deny all, then override an allow



              The order of the policy statements does not change the result of the policy. So don't try to write or interpret it "top down".



              Policies work like this:



              1. The policy starts implicitly denying everything (this is implied deny)

              2. Any "Allow" statements override any implied denies (this is an explicit allow)

              3. Any "Deny" statements override all allows (this is an explicit deny)

              So once you have a "Deny" statement, nothing can override that.



              To be able to "pigeon hole" an allow, like you're trying to do, you must do one of these:



              • Don't deny anything, allow only what you want to allow, or

              • Deny everything except what you want to allow (in a single statement)

              To accomplish what you want



              The closest you'll get is to allow your user to "see" everything, but operate only on the one EC2 instance. You'll need 2 statements:




              "Version": "2012-10-17",
              "Statement": [

              "Effect": "Allow",
              "Action": "ec2:Describe*",
              "Resource": "*"
              ,

              "Effect": "Allow",
              "Action": "*",
              "Resource": "arn:aws:ec2:us-east-1:1234567890123:instance/i-12345678"

              ]






              share|improve this answer























                Your Answer








                StackExchange.ready(function()
                var channelOptions =
                tags: "".split(" "),
                id: "2"
                ;
                initTagRenderer("".split(" "), "".split(" "), channelOptions);

                StackExchange.using("externalEditor", function()
                // Have to fire editor after snippets, if snippets enabled
                if (StackExchange.settings.snippets.snippetsEnabled)
                StackExchange.using("snippets", function()
                createEditor();
                );

                else
                createEditor();

                );

                function createEditor()
                StackExchange.prepareEditor(
                heartbeatType: 'answer',
                autoActivateHeartbeat: false,
                convertImagesToLinks: true,
                noModals: true,
                showLowRepImageUploadWarning: true,
                reputationToPostImages: 10,
                bindNavPrevention: true,
                postfix: "",
                imageUploader:
                brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
                contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
                allowUrls: true
                ,
                onDemand: true,
                discardSelector: ".discard-answer"
                ,immediatelyShowMarkdownHelp:true
                );



                );













                draft saved

                draft discarded


















                StackExchange.ready(
                function ()
                StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f963055%2faws-iam-restrict-console-access-to-only-one-instance%23new-answer', 'question_page');

                );

                Post as a guest















                Required, but never shown

























                4 Answers
                4






                active

                oldest

                votes








                4 Answers
                4






                active

                oldest

                votes









                active

                oldest

                votes






                active

                oldest

                votes









                3














                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 :)






                share|improve this answer



























                  3














                  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 :)






                  share|improve this answer

























                    3












                    3








                    3







                    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 :)






                    share|improve this answer













                    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 :)







                    share|improve this answer












                    share|improve this answer



                    share|improve this answer










                    answered yesterday









                    MLuMLu

                    9,87722445




                    9,87722445























                        0














                        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






                        share|improve this answer



























                          0














                          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






                          share|improve this answer

























                            0












                            0








                            0







                            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






                            share|improve this answer













                            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







                            share|improve this answer












                            share|improve this answer



                            share|improve this answer










                            answered yesterday









                            Sharuzzaman Ahmat RaslanSharuzzaman Ahmat Raslan

                            2631213




                            2631213





















                                0














                                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.






                                share|improve this answer

























                                • Where normally 4 leading spaces pre-format text/code in an itemized list you instead need to use 8 spaces

                                  – HBruijn
                                  yesterday











                                • @HBruijn Thanks a lot!

                                  – ServerInsights
                                  yesterday















                                0














                                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.






                                share|improve this answer

























                                • Where normally 4 leading spaces pre-format text/code in an itemized list you instead need to use 8 spaces

                                  – HBruijn
                                  yesterday











                                • @HBruijn Thanks a lot!

                                  – ServerInsights
                                  yesterday













                                0












                                0








                                0







                                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.






                                share|improve this answer















                                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.







                                share|improve this answer














                                share|improve this answer



                                share|improve this answer








                                edited yesterday









                                HBruijn

                                56.5k1190150




                                56.5k1190150










                                answered yesterday









                                ServerInsightsServerInsights

                                2115




                                2115












                                • Where normally 4 leading spaces pre-format text/code in an itemized list you instead need to use 8 spaces

                                  – HBruijn
                                  yesterday











                                • @HBruijn Thanks a lot!

                                  – ServerInsights
                                  yesterday

















                                • Where normally 4 leading spaces pre-format text/code in an itemized list you instead need to use 8 spaces

                                  – HBruijn
                                  yesterday











                                • @HBruijn Thanks a lot!

                                  – ServerInsights
                                  yesterday
















                                Where normally 4 leading spaces pre-format text/code in an itemized list you instead need to use 8 spaces

                                – HBruijn
                                yesterday





                                Where normally 4 leading spaces pre-format text/code in an itemized list you instead need to use 8 spaces

                                – HBruijn
                                yesterday













                                @HBruijn Thanks a lot!

                                – ServerInsights
                                yesterday





                                @HBruijn Thanks a lot!

                                – ServerInsights
                                yesterday











                                0














                                Regarding hiding all instances but one from the user



                                This cannot be done using IAM policies. The ec2:Describe* commands (including ec2:DescribeInstances) do not support resource-level permissions. So you can only allow or deny ec2:Describe* for everything (*). So your user can see all instances, or none.



                                Regarding trying to deny all, then override an allow



                                The order of the policy statements does not change the result of the policy. So don't try to write or interpret it "top down".



                                Policies work like this:



                                1. The policy starts implicitly denying everything (this is implied deny)

                                2. Any "Allow" statements override any implied denies (this is an explicit allow)

                                3. Any "Deny" statements override all allows (this is an explicit deny)

                                So once you have a "Deny" statement, nothing can override that.



                                To be able to "pigeon hole" an allow, like you're trying to do, you must do one of these:



                                • Don't deny anything, allow only what you want to allow, or

                                • Deny everything except what you want to allow (in a single statement)

                                To accomplish what you want



                                The closest you'll get is to allow your user to "see" everything, but operate only on the one EC2 instance. You'll need 2 statements:




                                "Version": "2012-10-17",
                                "Statement": [

                                "Effect": "Allow",
                                "Action": "ec2:Describe*",
                                "Resource": "*"
                                ,

                                "Effect": "Allow",
                                "Action": "*",
                                "Resource": "arn:aws:ec2:us-east-1:1234567890123:instance/i-12345678"

                                ]






                                share|improve this answer



























                                  0














                                  Regarding hiding all instances but one from the user



                                  This cannot be done using IAM policies. The ec2:Describe* commands (including ec2:DescribeInstances) do not support resource-level permissions. So you can only allow or deny ec2:Describe* for everything (*). So your user can see all instances, or none.



                                  Regarding trying to deny all, then override an allow



                                  The order of the policy statements does not change the result of the policy. So don't try to write or interpret it "top down".



                                  Policies work like this:



                                  1. The policy starts implicitly denying everything (this is implied deny)

                                  2. Any "Allow" statements override any implied denies (this is an explicit allow)

                                  3. Any "Deny" statements override all allows (this is an explicit deny)

                                  So once you have a "Deny" statement, nothing can override that.



                                  To be able to "pigeon hole" an allow, like you're trying to do, you must do one of these:



                                  • Don't deny anything, allow only what you want to allow, or

                                  • Deny everything except what you want to allow (in a single statement)

                                  To accomplish what you want



                                  The closest you'll get is to allow your user to "see" everything, but operate only on the one EC2 instance. You'll need 2 statements:




                                  "Version": "2012-10-17",
                                  "Statement": [

                                  "Effect": "Allow",
                                  "Action": "ec2:Describe*",
                                  "Resource": "*"
                                  ,

                                  "Effect": "Allow",
                                  "Action": "*",
                                  "Resource": "arn:aws:ec2:us-east-1:1234567890123:instance/i-12345678"

                                  ]






                                  share|improve this answer

























                                    0












                                    0








                                    0







                                    Regarding hiding all instances but one from the user



                                    This cannot be done using IAM policies. The ec2:Describe* commands (including ec2:DescribeInstances) do not support resource-level permissions. So you can only allow or deny ec2:Describe* for everything (*). So your user can see all instances, or none.



                                    Regarding trying to deny all, then override an allow



                                    The order of the policy statements does not change the result of the policy. So don't try to write or interpret it "top down".



                                    Policies work like this:



                                    1. The policy starts implicitly denying everything (this is implied deny)

                                    2. Any "Allow" statements override any implied denies (this is an explicit allow)

                                    3. Any "Deny" statements override all allows (this is an explicit deny)

                                    So once you have a "Deny" statement, nothing can override that.



                                    To be able to "pigeon hole" an allow, like you're trying to do, you must do one of these:



                                    • Don't deny anything, allow only what you want to allow, or

                                    • Deny everything except what you want to allow (in a single statement)

                                    To accomplish what you want



                                    The closest you'll get is to allow your user to "see" everything, but operate only on the one EC2 instance. You'll need 2 statements:




                                    "Version": "2012-10-17",
                                    "Statement": [

                                    "Effect": "Allow",
                                    "Action": "ec2:Describe*",
                                    "Resource": "*"
                                    ,

                                    "Effect": "Allow",
                                    "Action": "*",
                                    "Resource": "arn:aws:ec2:us-east-1:1234567890123:instance/i-12345678"

                                    ]






                                    share|improve this answer













                                    Regarding hiding all instances but one from the user



                                    This cannot be done using IAM policies. The ec2:Describe* commands (including ec2:DescribeInstances) do not support resource-level permissions. So you can only allow or deny ec2:Describe* for everything (*). So your user can see all instances, or none.



                                    Regarding trying to deny all, then override an allow



                                    The order of the policy statements does not change the result of the policy. So don't try to write or interpret it "top down".



                                    Policies work like this:



                                    1. The policy starts implicitly denying everything (this is implied deny)

                                    2. Any "Allow" statements override any implied denies (this is an explicit allow)

                                    3. Any "Deny" statements override all allows (this is an explicit deny)

                                    So once you have a "Deny" statement, nothing can override that.



                                    To be able to "pigeon hole" an allow, like you're trying to do, you must do one of these:



                                    • Don't deny anything, allow only what you want to allow, or

                                    • Deny everything except what you want to allow (in a single statement)

                                    To accomplish what you want



                                    The closest you'll get is to allow your user to "see" everything, but operate only on the one EC2 instance. You'll need 2 statements:




                                    "Version": "2012-10-17",
                                    "Statement": [

                                    "Effect": "Allow",
                                    "Action": "ec2:Describe*",
                                    "Resource": "*"
                                    ,

                                    "Effect": "Allow",
                                    "Action": "*",
                                    "Resource": "arn:aws:ec2:us-east-1:1234567890123:instance/i-12345678"

                                    ]







                                    share|improve this answer












                                    share|improve this answer



                                    share|improve this answer










                                    answered 11 hours ago









                                    Matt HouserMatt Houser

                                    7,8091518




                                    7,8091518



























                                        draft saved

                                        draft discarded
















































                                        Thanks for contributing an answer to Server Fault!


                                        • Please be sure to answer the question. Provide details and share your research!

                                        But avoid


                                        • Asking for help, clarification, or responding to other answers.

                                        • Making statements based on opinion; back them up with references or personal experience.

                                        To learn more, see our tips on writing great answers.




                                        draft saved


                                        draft discarded














                                        StackExchange.ready(
                                        function ()
                                        StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f963055%2faws-iam-restrict-console-access-to-only-one-instance%23new-answer', 'question_page');

                                        );

                                        Post as a guest















                                        Required, but never shown





















































                                        Required, but never shown














                                        Required, but never shown












                                        Required, but never shown







                                        Required, but never shown

































                                        Required, but never shown














                                        Required, but never shown












                                        Required, but never shown







                                        Required, but never shown







                                        Popular posts from this blog

                                        Grendel Contents Story Scholarship Depictions Notes References Navigation menu10.1093/notesj/gjn112Berserkeree

                                        Area configuration aggregation error after install Porto themeMagento 2.1 CE Installed but front/backend not loading/workingCSS not loading on page within Magento 2 pageCannot install module in Magento 2no commands defined in the “setup” namespace. in Magento2Magento 2: Static files are present but shows 404Why do i have to always run the commands to clean cache in Magento 2.1.8?Failure reason: 'Unable to unserialize value.'Error 500 after magento migrationIn production mode the site does not loadMagento 2 : Error 500 after installing

                                        Middle Expansion Olielle Resaix Definition: Uttering songs of triumph shouting with joy triumphant exulting Sejunction Journal 붙다 달 고급 품목 외출 The stretch trades the screeching tin. Definition: The act of speaking with a drawl a drawl Cough Sand Definition: An uproar a quarrel a noisy outbreak Shake Iron Publicize Horse House Baby 사과 Resaix Flaggy Jelly Temporary Unequaled Puppet A drop in the bucket Shrew 성격 회원 성질 미팅 The burn frames the tacky quality. Materialistic The smoke reduces the way. Yammoe Nondescript Cheek 얼굴 배 약하다 날리다 타다 The illegal country shows the iron. Help Rule Drearien Smoke Teaching Meaty Wasp Abraham Lincoln Jaws 진심 수리하다 Size Cork Idea Convert Think Lark John Lennon 거울 청소 군 추천하다 아이스크림