aws-eks: aws-auth creation failure takes 1 hour

[taku-hatano]

Describe the bug

In creation cluster stack, aws-auth creation step was failed and it took 1 hour for fail parent stack.
Error message is below,

CloudFormation did not receive a response from your Custom Resource. Please check your logs for requestId [ca31f6eb-af1b-412e-8a06-f312c8affcc7]. If you are using the Python cfn-response module, you may need to update your Lambda function code so that CloudFormation can attach the updated version.

(There is no error in Lambda handler log, so I think the aws-auth creation was successful.)

Expected Behavior

If aws-auth creation fails, the parent Stack will also fail immediately.

Current Behavior

If aws-auth creation fails, the parent Stack fail after 1 hour.

Reproduction Steps

I use https://aws-quickstart.github.io/cdk-eks-blueprints/

const cluster = new blueprints.GenericClusterProvider({
  fargateProfiles: {
	  "fp-default": {
		  selectors: [{ namespace: "default", labels: { worker: "fargate" } }],
	  },
  },
});
blueprints.EksBlueprint.builder()
  .clusterProvider(cluster)
  .resourceProvider(
    blueprints.GlobalResources.Vpc,
    new blueprints.DirectVpcProvider(args.vpc),
  )
  .build(app, stackName, props)

Possible Solution

I read deployed Lambda handler code, but I cannot find cfn response.
ref. here

Where is cfn response for Python custom resource handlers?

Additional Information/Context

No response

CDK CLI Version

2.137.0 (build bb90b4c)

Framework Version

No response

Node.js Version

v20.14.0

OS

AmazonLinux 2023.3.20240312

Language

TypeScript

Language Version

5.4.3

Other information

No response

[pahud]

cdk-blue-prints is not maintained by AWS CDK team. Please report your issue to https://github.com/aws-quickstart/cdk-eks-blueprints/issues

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.

[aws-cdk-automation]

Comments on closed issues and PRs are hard for our team to see. If you need help, please open a new issue that references this one.