CDK Deploy: Cannot invoke "String.contains(java.lang.CharSequence)" because "errorMsg" is null

[daveharig]

Describe the bug

After destroying a stack and re deploying it, IAM resource creations fail with internal error:

Resource handler returned message: "Cannot invoke "String.contains(java.lang.CharSequence)" because "errorMsg" is null" (RequestToken: 3578c1be-920b-222a-4c9e-0f3596bce26c, HandlerErrorCode: InternalFailure)

The issue suggests a low-level internal AWS CloudFormation or IAM glitch.

Regression Issue

• Select this option if this issue appears to be a regression.

Last Known Working CDK Version

No response

Expected Behavior

Deploy stack

Current Behavior

After destroying a stack and re deploying it, IAM resource creations fail with internal error:

Resource handler returned message: "Cannot invoke "String.contains(java.lang.CharSequence)" because "errorMsg" is null" (RequestToken: 3578c1be-920b-222a-4c9e-0f3596bce26c, HandlerErrorCode: InternalFailure)

The issue suggests a low-level internal AWS CloudFormation or IAM glitch.

Reproduction Steps

Destroy stack and re deploy it with AWS CDK 2.174.0

Possible Solution

No response

Additional Information/Context

No response

CDK CLI Version

2.174.0

Framework Version

2.174.0

Node.js Version

22.4.1

OS

MacOS 15.2

Language

TypeScript

Language Version

5.5.2

Other information

No response

[khushail]

Hi @daveharig , thanks for reaching out. I am not able to reproduce the issue on my side.

Here is what I did -

1. created and deployed a stack successfully -

2. Then I deleted it and then re-deployed it , which succeeded -

So I did not get any error message.

Could you please share more information on how to repro the error ?

[daveharig]

It’s a low level issue. Cleared up after 48 hours. Must have been some stuck/residual resources that did not get immediately removed by destroy command. Let me know if you want the CDK/CloudFormation logs.

…

Sent from my iPhone On Jan 6, 2025, at 4:00 PM, Shailja Khurana ***@***.***> wrote:  Hi @daveharig , thanks for reaching out. I am not able to reproduce the issue on my side. Here is what I did - 1. created and deployed a stack successfully - Screenshot.2025-01-06.at.1.54.25.PM.png (view on web) <https://github.com/user-attachments/assets/e6d23ebb-cfc7-4e2f-9aa3-73bd15e6008c> 1. Then I deleted it and then re-deployed it , which succeeded - Screenshot.2025-01-06.at.1.56.18.PM.png (view on web) <https://github.com/user-attachments/assets/651660a9-8e8c-4f8d-899f-448d35c6ffec> So I did not get any error message. Could you please share more information on how to repro the error ? — Reply to this email directly, view it on GitHub <#32741 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AWJSB6W65KWFP2J2LOHET3T2JL4JBAVCNFSM6AAAAABUTPUXWOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNZUGAYDENBZHE> . You are receiving this because you were mentioned. <https://github.com/notifications/beacon/AWJSB6QET232CSTIIC4AK2L2JL4JBA5CNFSM6AAAAABUTPUXWOWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTUZNQUUG.gif> Message ID: ***@***.***>

[khushail]

@daveharig yes, please. Logs would be helpful as the issue is not reproducible

[github-actions]

This issue has not received a response in a while. If you want to keep this issue open, please leave a comment below and auto-close will be canceled.