amplify auth update makes "Email Verification Link with Redirect" not working

[yaquawa]

Describe the bug
I was able to sign up a user with the following code

import { Auth } from 'aws-amplify'

Auth.signUp({
  username: email,
  password: password,
  attributes: {
    email: email,
  },
})

The email has been sent correctly but,

1. the email body is not the same as what I have configured.
2. the link is 404 not found

here is the email body(a dot + URL):

. http://verificationbucket-develop.s3-website-ap-northeast-1.amazonaws.com/?data=eyJ1c2VyTmFtZSI6ImEyZTU1NWVhLTVkZTctNGRiOC04ODg3LTAxN2NlMWYzMGQyNiIsInJlZGlyZWN0VXJsIjoiLz91c2VybmFtZT1hMmU1NTVlYS01ZGU3LTRkYjgtODg4Ny0wMTdjZTFmMzBkMjYiLCJyZWdpb24iOiJhcC1ub3J0aGVhc3QtMSIsImNsaWVudElkIjoiN25tYXQ4bDZodWcyaWcyMGFtaWpjY20wNzQifQ==&code=407755

I couldn't find any information about the "Email Verification Link with Redirect".
Have I missed something else?
What I want to achieve is that after user clicked on the link in the email, the user authenticated automatically and redirect to the "You are authenticated!" page on my site.

Amplify CLI Version
4.31.1

To Reproduce

amplify auth update
...
...
 Do you want to enable any of the following capabilities? (Press <space> to select, <a> to toggle all, <i> to invert selection)
 ◯ Add Google reCaptcha Challenge
❯ ● Email Verification Link with Redirect
 ◯ Add User to Group
 ◯ Email Domain Filtering (blacklist)
 ◯ Email Domain Filtering (whitelist)
 ◯ Custom Auth Challenge Flow (basic scaffolding - not for production)

amplify auth push

[UnleashedMind]

This is an known issue for Cognito, people have figured out a bunch of workarounds, for example:

https://medium.com/@moedano.t/redirect-to-your-website-after-confirm-registration-using-aws-cognito-and-cloud-formation-5c50ff15ff56
https://medium.com/@jacobjoy/redirect-user-using-amazon-cognito-confirmation-url-d8ccb11bac75

Hope that helps.

[yaquawa]

@UnleashedMind Thanks for the links.
But that's not what I want to know about. I understand I can do the same thing with out Amplify, here I'm asking is the "Amplify way" to do it. That is to do it with the "Email Verification Link with Redirect" option, which set the trigger by Amplify(infrastructure as code). But I'm meeting the issue what I have described here, that's why I opened this issue.

[yaquawa]

Hi Amplify team,
I want to know if it's possible to make "Email Verification Link with Redirect" option work.
I have to make a decision for this. If this is a bug and won't be fixed soon, I'll do it manually.
Thanks.

[UnleashedMind]

@yaquawa
This is a dependency issue on Cognito, we won't be able to fix it on the Amplify CLI side. You will need to use some of the workarounds that I listed in the above response.

[yaquawa]

@UnleashedMind
The links you given me has nothing to do with the option "Email Verification Link with Redirect".
Even the docs doesn't has any information for this. Is this option a dead feature?
Could you give me more info on this option? Thanks.

[yaquawa]

Any update on this?

[yaquawa]

I think I found the issue now.
I found the Environment variables for the lambda function generated by this option was set to blank, how to fix this?

• EMAILMESSAGE
• EMAILSUBJECT
• REDIRECTURL
• RESOURCENAME

[yaquawa]

I tried editing this file:
amplify/backend/function/myproject2713aa05CustomMessage/function-parameters.json

The original content of this file was:
(notice that the triggerEnvs is a string but not an array.)

{
  "trigger": true,
  "modules": [
    "verification-link"
  ],
  "parentResource": "minaoshi2713aa05",
  "functionName": "minaoshi2713aa05CustomMessage",
  "resourceName": "minaoshi2713aa05CustomMessage",
  "parentStack": "auth",
  "triggerEnvs": "[\n  {\n    \"key\": \"RESOURCENAME\",\n    \"value\": \"resourceName\"\n  }\n]",
  "triggerDir": "/Users/wang/.npm-global/lib/node_modules/@aws-amplify/cli/node_modules/amplify-category-auth/provider-utils/awscloudformation/triggers/CustomMessage",
  "triggerTemplate": "CustomMessage.json.ejs",
  "roleName": "minaoshi2713aa05CustomMessage",
  "skipEdit": true,
  "REDIRECTURL": "https://3naoshi.com/",
  "EMAILSUBJECT": "account confirm",
  "EMAILMESSAGE": "click the follwoing links",
  "RESOURCENAME": "resourceName",
  "enableCors": false,
  "triggerEventPath": "CustomMessage.event.json"
}

I just changed the triggerEnvs to

"triggerEnvs": [
        {
            "key": "RESOURCENAME",
            "value": "resourceName"
        }
    ],

then the issue gone.

I noticed that if I run a amplify update auth, the amplify/backend/function/myproject2713aa05CustomMessage/function-parameters.json goes back to the stringified version again... This must be a bug.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale]

This issue has been automatically closed because of inactivity. Please open a new issue if you are still encountering problems.

[yaquawa]

Still hit the same issue... will this be fixed someday?

[github-actions]

This issue has been automatically locked since there hasn't been any recent activity after it was closed. Please open a new issue for related bugs.

Looking for a help forum? We recommend joining the Amplify Community Discord server *-help channels for those types of questions.