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:<>

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ヶ月前

ログインしていません。 ログイン 回答を投稿する。

優れた回答とは、質問に明確に答え、建設的なフィードバックを提供し、質問者の専門分野におけるスキルの向上を促すものです。

質問に答えるためのガイドライン

関連するコンテンツ