EMR clusters not running

0

Hi! I had several workflows that are running on AWS EMR with spark. Since a yesterday the cluster creation step is failing.

On the events of the cluster I see a VALIDATION_ERROR with no details. On the termination message I see EMR_DefaultRole has insufficient EC2 permissions

I've recheck my roles, recreate them, and also give them the admin policy and even with all of this the cluster does not start. Also I thought it could be some aws bug deployed so I've tried different combinations of instance type, emr versions, creating new default roles, etc. Nothing worked. On cloud trail I always see that the role is not authorized on ec2, even with the full admin policy.

Has someone experience something similar? how did you fix it? Thanks in advance!

Hector
已提問 1 年前檢視次數 313 次
1 個回答
0
已接受的答案

Check to see if you have a policy or SCP in place that requires the Instance Metadata Service V2 that is being applied to the account you are running in. This can prevent starting any instances that are not at IMDS v2. This shows as a permissions error and is really hard to link back to a policy issue/change. https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/configuring-instance-metadata-service.html

profile pictureAWS
已回答 1 年前
AWS
支援工程師
已審閱 2 個月前
  • Thanks! I found it was a restriction with the SCP that did not allow starting instances on subnets with public IPs. Changing it to private ones solved the issue

您尚未登入。 登入 去張貼答案。

一個好的回答可以清楚地回答問題並提供建設性的意見回饋,同時有助於提問者的專業成長。

回答問題指南