1 Answer
- Newest
- Most votes
- Most comments
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
Relevant content
- asked a year ago
- asked a month ago
- asked 20 days ago
- AWS OFFICIALUpdated 4 months ago
- AWS OFFICIALUpdated 2 months ago
- AWS OFFICIALUpdated 2 months ago
- AWS OFFICIALUpdated 5 months ago