By using AWS re:Post, you agree to the AWS re:Post Terms of Use

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
asked a month ago45 views
1 Answer
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
EXPERT
answered a month ago
profile picture
EXPERT
reviewed a month ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions