aws-amplify / aws-amplify/amplify-cli

Assets are not uploaded to S3 in auth category for Cognito Triggers

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

Description

### How did you install the Amplify CLI?

_No response_

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

_No response_

### Amplify CLI Version

10.5.2

### What operating system are you using?

MacOS

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

No manual changes made

### Reproduction steps

1. In the default Auth CLI workflow select `Add User to Group`

```
amplify update auth
$ Do you want to enable any of the following capabilities?
◯ Add Google reCaptcha Challenge
❯ ◯ Email Verification Link with Redirect
◯ Add User to Group
◯ Email Domain Filtering (deny list)
◯ Email Domain Filtering (allow list)
◯ Custom Auth Challenge Flow (basic scaffolding - not for production)
◯ Override ID Token Claims
```

2. Go to the s3 bucket that Amplify created (`XXXXXverificationbucket-dev`), you'll find it's empty.

Contributor guide

Open the contributing guide

Research direction

Reproduce the default Auth CLI workflow with Amplify CLI 10.5.2, selecting “Add User to Group,” then inspect the generated S3 verification bucket. Compare the expected Cognito Trigger assets with the bucket contents; done means the required assets are uploaded to the created bucket.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, typescript
Domain
authentication, cli, cloud
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.