aws-amplify / aws-amplify/amplify-cli

`AuthTriggerCustomLambdaStack` error in Amplify Hosting using Amplify CLI 10.6.2

Open
#11,714 18 comments 0 reactions 0 assignees View on GitHub
auth bug p2
Dominant language
TypeScript
Stars
2.9k
Forks
825
Avg merge
11d 23h
Merged PRs (30d)
2

Description

### How did you install the Amplify CLI?

npm

### If applicable, what version of Node.js are you using?

19.0.1

### Amplify CLI Version

10.6.0

### What operating system are you using?

Mac

### Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.

no changes to backend

### Describe the bug

made changes to frontend on dev and qa. dev deploys just fine, qa fails on backend build

### Expected behavior

both environments should deploy without issue

### Reproduction steps

amplify env checkout
git checkout
push code and wait to deploy

### Project Identifier

5940205a-065b-4669-a951-5a8e4b54757a

### Log output

```
# Put your logs below this line

```

### Additional information

_No response_

### Before submitting, please confirm:

- [X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
- [X] I have removed any sensitive information from my code snippets and submission.

Contributor guide

Open the contributing guide

Research direction

Reproduce the failure with the listed Amplify environment checkout and deployment steps, then inspect the backend build log for the AuthTriggerCustomLambdaStack error. Compare the working dev environment with the failing qa environment; done means both environments deploy successfully without backend-build errors.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, typescript
Domain
authentication, cli, cloud
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.