aws-amplify / aws-amplify/amplify-hosting

Build getting failed with single service role

Open
#2,059 4 comments 0 reactions 0 assignees View on GitHub
backend-builds bug pending-prioritization
Dominant language
Dockerfile
Stars
481
Forks
123
PR merge metrics
No merged PRs in 30d

Description

### Before opening, please confirm:

- [X] I have checked to see if my question is addressed in the [FAQ](https://github.com/aws-amplify/amplify-console/blob/master/FAQ.md).
- [X] I have [searched for duplicate or closed issues](https://github.com/aws-amplify/amplify-console/issues?q=is%3Aissue+).
- [X] I have read the guide for [submitting bug reports](https://github.com/aws-amplify/amplify-console/blob/master/CONTRIBUTING.md).
- [X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

### App Id

d1pnvqfdyg8r0c

### Region

us-east-1

### Amplify Console feature

Backend builds, Build settings, Custom builds

### Describe the bug

We are hosting the static website in AWS Amplify which is in AWS CodeCommit. So while we are creating the application the build is getting failed why because the application is not creating new service role and it is taking existing service role.

It works if it creates new service role for each and every application we are creating in AWS Amplify so please fix this bug from your side.

Test Case : We have created more than one service role manually and the application is started deploying it and created the new service role.

### Expected behavior

Instead of creating service roles manually, The application should create new service role automatically while creating the application.

### Reproduction steps

1. We could see the application build is failing if we have one service role related to AWS Amplify
2. Suppose if we created the more than one service role manually, the application build is getting success.
3. Please try to resolve the issue even if it is single service role.

### Build Settings

_No response_

### Additional information

_No response_

Contributor guide

Open the contributing guide

Research direction

No source file or test is named. Start by reviewing FAQ.md and CONTRIBUTING.md, then reproduce the failure for app d1pnvqfdyg8r0c in us-east-1 with one Amplify service role. Done means a new application can build successfully without manually creating additional service roles.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws
Domain
ci-cd, cloud, devops
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.