Skip to content
By using AWS re:Post, you agree to the AWS re:Post Terms of Use
AWS re:Postre:Post
About re:Post

mplify Git-based builds fail with “Unable to assume specified IAM Role” – Missing Service-Linked Role template

0

Issue Summary:

Manual Amplify Hosting deploy works.

Git-based Amplify build fails immediately with: Unable to assume specified IAM Role.

AWSServiceRoleForAmplify does not exist.

Attempting to create service-linked role via: aws iam create-service-linked-role --aws-service-name amplify.amazonaws.com returns: Cannot find Service Linked Role template for amplify.amazonaws.com

IAM user has admin privileges.

No SCP or Organizations in use.

Issue persists after deleting and recreating Amplify app.

Conclusion: Amplify Git build path cannot initialize its required service-linked role in this account.

Topics
Front-End Web & MobileSecurity, Identity, & Compliance
Tags
AWS Identity and Access ManagementAWS Amplify
Language
English
asked 3 months ago57 views
1 Answer
0

Git-based builds in AWS Amplify require the service-linked role AWSServiceRoleForAmplify. If this role is not present, Amplify is unable to assume the necessary IAM permissions, resulting in the error “Unable to assume specified IAM Role.” Under normal circumstances, the role is created automatically when Amplify Hosting is first configured. If the service-linked role template is unavailable, it typically indicates that Amplify Hosting is not supported in the account or region, or that the role creation process has failed.

https://docs.aws.amazon.com/amplify/latest/userguide/amplify-service-role.html

https://docs.aws.amazon.com/singlesignon/latest/userguide/slrconcept.html

EXPERT
answered 2 months 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.

Relevant content