{"action":"closed","issue":{"url":"https://api.github.com/repos/rslifka/elasticity/issues/81","labels_url":"https://api.github.com/repos/rslifka/elasticity/issues/81/labels{/name}","comments_url":"https://api.github.com/repos/rslifka/elasticity/issues/81/comments","events_url":"https://api.github.com/repos/rslifka/elasticity/issues/81/events","html_url":"https://github.com/rslifka/elasticity/issues/81","id":67185479,"number":81,"title":"Add support for service_role","user":{"login":"alexanderdean","id":200511,"avatar_url":"https://avatars.githubusercontent.com/u/200511?v=3","gravatar_id":"","url":"https://api.github.com/users/alexanderdean","html_url":"https://github.com/alexanderdean","followers_url":"https://api.github.com/users/alexanderdean/followers","following_url":"https://api.github.com/users/alexanderdean/following{/other_user}","gists_url":"https://api.github.com/users/alexanderdean/gists{/gist_id}","starred_url":"https://api.github.com/users/alexanderdean/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/alexanderdean/subscriptions","organizations_url":"https://api.github.com/users/alexanderdean/orgs","repos_url":"https://api.github.com/users/alexanderdean/repos","events_url":"https://api.github.com/users/alexanderdean/events{/privacy}","received_events_url":"https://api.github.com/users/alexanderdean/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":3,"created_at":"2015-04-08T18:04:33Z","updated_at":"2015-04-13T04:02:20Z","closed_at":"2015-04-13T04:02:20Z","body":"As per boto: https://github.com/boto/boto/blob/develop/boto/emr/connection.py#L577\r\n\r\nDriving reason for this is that on 6th April [AWS changed](http://docs.aws.amazon.com/ElasticMapReduce/latest/DeveloperGuide/emr-iam-roles-creatingroles.html) how EMR jobflows need to be authenticated:\r\n\r\n> If you created your first cluster before April 6, 2015, IAM roles are not mandatory. However, we \r\n> recommend that you specify IAM roles for your cluster as a best practice.\r\n\r\nHere's my understanding of support currently:\r\n\r\n| aws cli        | boto & API        | elasticity    | defaults* |\r\n|----------------|-------------|---------------|---------------|\r\n| `--ec2-attributes InstanceProfile=x`             | `JobFlowRole` | `job_flow_role` | `\"EMR_EC2_DefaultRole\"` |\r\n| `--service-role=x` | `ServiceRole` | #81           | `\"EMR_DefaultRole\"` |\r\n\r\n\\* Created using `$ aws emr create-default-roles`"}}