If applicable, what version of Node.js are you using?
v20.11.0
Amplify CLI Version
12.9.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 manual changes made
Describe the bug
Try to create a new amplify env and when you try to amplify push it fails with the following error
🛑 The following resources failed to deploy:
Resource Name: MFALambdaRole (AWS::IAM::Role)
Event Type: create
Reason: The policy chedar678aa9d9_sns_pass_role_policy already exists on the role chedar678aa9d9_totp_lambda_role-dev.
🛑 Resource is not in the state stackUpdateComplete
Name: MFALambdaRole (AWS::IAM::Role), Event Type: create, Reason: The policy chedar678aa9d9_sns_pass_role_policy already exists on the role chedar678aa9d9_totp_lambda_role-dev., IsCustomResource: false
Hey @DevTGhosh, thank you for reaching out. From the project identifier noticed the the cli.json present in the amplify folder sees to be missing some feature flags. Were these intentionally removed?
the feature flag useenabledmfas when set as false does add a MFALambdaRole. setting the flag to true and running through the update auth flow should remove the role from the cloudformation template.
This issue is now closed. Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.
How did you install the Amplify CLI?
npm
If applicable, what version of Node.js are you using?
v20.11.0
Amplify CLI Version
12.9.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 manual changes made
Describe the bug
Try to create a new amplify env and when you try to amplify push it fails with the following error
🛑 The following resources failed to deploy: Resource Name: MFALambdaRole (AWS::IAM::Role) Event Type: create Reason: The policy chedar678aa9d9_sns_pass_role_policy already exists on the role chedar678aa9d9_totp_lambda_role-dev.
🛑 Resource is not in the state stackUpdateComplete Name: MFALambdaRole (AWS::IAM::Role), Event Type: create, Reason: The policy chedar678aa9d9_sns_pass_role_policy already exists on the role chedar678aa9d9_totp_lambda_role-dev., IsCustomResource: false
Expected behavior
To be able to create a new amplify env.
Reproduction steps
Project Identifier
Project Identifier: c1df5805dc85b2b52388558184e19166
Log output
Additional information
My auth cloudformation template
Clap!
Thank you for signing up to your first scene
Bienvenue,
Votre compte Chedar a bien été créé.
Vous trouverez ci-dessous les accès à votre compte:- Lien:app.chedar.fr
- Nom d'utilisateur: {username}
- Mot de passe temporaire: {####}
Notre centre de formation est accessible ici:learn.chedar.io
Happy budgeting,
l'Equipe Chedar
Si vous avez des soucis à vous connectez, veuillez nous contacter à support@chedar.fr
Hey @DevTGhosh, thank you for reaching out. From the project identifier noticed the the
cli.json
present in the amplify folder sees to be missing some feature flags. Were these intentionally removed?the feature flag useenabledmfas when set as
false
does add aMFALambdaRole
. setting the flag to true and running through the update auth flow should remove the role from the cloudformation template.Closing the issue due to inactivity. Do reach out to us if you are still experiencing this issue
This issue is now closed. Comments on closed issues are hard for our team to see. If you need more assistance, please open a new issue that references this one.