One of the limitations of Amazon AWS’s EC2 IAMs is the instance role MUST be assigned at “launch” time. \u00a0This is distinct from the “Start” action on an instance that was running as has been stopped. \u00a0In order to associate a current instance with a new or existing IAM profile, you must create a new instance. \u00a0This can be done by creating an image from the current instance and launching that.<\/p>\n
Once an IAM role has been assigned, you may alter it. \u00a0This suggests that best practice is to always launch an instance with SOME IAM role.<\/p>\n
Are the command line tools related to IAM roles? \u00a0YES, although it’s not specified, AWS\u00a0command line \u00a0tools will find the role of the instance it’s on, \u00a0even if it’s not AWS Linux.<\/p>\n
Assuming a role<\/p>\n
http:\/\/docs.aws.amazon.com\/cli\/latest\/userguide\/cli-roles.html<\/p>\n","protected":false},"excerpt":{"rendered":"
One of the limitations of Amazon AWS’s EC2 IAMs is the instance role MUST be assigned at “launch” time. \u00a0This is distinct from the “Start” action on an instance that was running as has been stopped. \u00a0In order to associate a current instance with a new or existing IAM profile, you must create a new…<\/p>\n