1 Answer
- Newest
- Most votes
- Most comments
1
Hi duwan, It's more of a timing thing than anything else. After you create a role it might take several seconds for the permissions to propagate. Check out the following link and search for "several seconds for the permissions to propagate" to get to the relevant section... https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/iam-roles-for-amazon-ec2.html
Also look at the following link where the similar problem was encountered... https://github.com/hashicorp/terraform/issues/1885
There are two ways to solve the problem :-
- try creating the cluster again as it's a timing thing and you likely won't encounter the problem again.
- Create the default roles before you create the EMR cluster... https://awscli.amazonaws.com/v2/documentation/api/latest/reference/emr/create-default-roles.html
answered 2 years ago
Relevant content
- asked 4 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
Thank you very much. I have already tried a lot of times and always the same error. Need I delete the created role before I try again?
When I use aws-cli to create EMR roles, it says "is not authorized to perform: iam:GetInstanceProfile". So I think it's because I do not have this permission.
@duwan, I would delete the created roles and re-create them. And looks like you don't have appropriate permissions ("iam:GetInstanceProfile").