Resource handler returned message: "A condition block must be present for the Cognito provider

[meteordefect]

How did you install the Amplify CLI?

npm install -g @aws-amplify/cli

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

v16.20.2

Amplify CLI Version

12.10.1

What operating system are you using?

Mac/Linux

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

no

Describe the bug

We are trying to create a new env. I download the working code from gitlab for our running environment. i run amplify env add to create a new environment then amplify push. I got an error about node 14 being out of date so updated all references to that then I encounter this error below.

🛑 The following resources failed to deploy:
Resource Name: LambdaExecutionRole (AWS::IAM::Role)
Event Type: create
Reason: Resource handler returned message: "A condition block must be present for the Cognito provider (Service: Iam, Status Code: 400, Request ID: a7c1f84f-53f9-450b-ab6b-61c20a0b590a)" (RequestToken: 91410630-55e8-cdb6-fa49-00c9bc9ede63, HandlerErrorCode: InvalidRequest)

🛑 Resource is not in the state stackUpdateComplete
Name: LambdaExecutionRole (AWS::IAM::Role), Event Type: create, Reason: Resource handler returned message: "A condition block must be present for the Cognito provider (Service: Iam, Status Code: 400, Request ID: a7c1f84f-53f9-450b-ab6b-61c20a0b590a)" (RequestToken: 91410630-55e8-cdb6-fa49-00c9bc9ede63, HandlerErrorCode: InvalidRequest), IsCustomResource: false

Learn more at: https://docs.amplify.aws/cli/project/troubleshooting/

Session Identifier: 4a4f0ab6-d997-4acc-ba3e-e33b9162fe44

Expected behavior

Env should build or give the 25000 stack limit error

Reproduction steps

• pull working env code from gitlab
• amplify env add
• push new env, et error about the node version 14
• update all references

Project Identifier

hxtfpdyx21s0b8sg7x9lqkrc0000gn/T/assessorbackend/report-1712101812929.zip

Log output

# Put your logs below this line

Additional information

No response

Before submitting, please confirm:

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

[github-actions]

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.