service linked role creation permission required to increase limit

0

I am increasing the elastic ip limit using the console and when I try to submit the request, I get an error "Service-linked role creation access denied.". The funny thing is that for one account it succeeds, and another account it does give the error. Both roles I am using to create the limit request have the same policy for iam:<> and servicequotas:<>

AWS
已提問 3 個月前檢視次數 72 次
1 個回答
0

Hello.

A similar issue was reported in the GitHub issue below.
The current workaround seems to be to create a service linked role yourself.
https://github.com/org-formation/aws-resource-providers/issues/75

As a workaround, I have been able to create the service-linked role myself through the CLI beforehand: aws iam create-service-linked-role --aws-service-name servicequotas.amazonaws.com.

It is unclear why it is not created automatically, but if you search for "CreateServiceLinkedRole" in the CloudTrail event history, you may be able to find the cause of the problem.
https://docs.aws.amazon.com/awscloudtrail/latest/userguide/tutorial-event-history.html

profile picture
專家
已回答 3 個月前
profile picture
專家
已審閱 3 個月前

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

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

回答問題指南