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 个月前73 查看次数
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 个月前

您未登录。 登录 发布回答。

一个好的回答可以清楚地解答问题和提供建设性反馈,并能促进提问者的职业发展。

回答问题的准则