Pahud Hsieh

@elamaran11 Thank you for clarification. This seems to be a limitation on CFN side that CDK would probably not be able to work around. I would suggest open an issue...

This is interesting. Can you share more details about how to inject the context ID for the managed nodegroup? Is it a Tag or label? Can you share more tech...

Hi @fossamagna, Thank you for the detailed report and for providing a working workaround! This appears to be a valid concern regarding the accessibility of JavaScript resolvers through the `cfnResources.cfnResolvers`...

Thank you for the report. I guess we probably need to update this file. https://github.com/aws/aws-cdk/blob/f3d74bb78189ec6b76cfa85c97d993c1b26c1cac/packages/aws-cdk-lib/aws-eks/lib/addons/neuron-device-plugin.yaml Are you interested to submit a PR for that?

Hi @HarshitSrivastava007, Thanks for reporting this issue! I can see you're experiencing problems with dynamic routes in your Next.js 14 Pages Router app on Amplify Hosting. First, I want to...

Are you requesting a feature to allow CDK to do `helm push` to private ECR repo? This is interesting. Can you share how would you implement this feature and what...

Yes this sounds very promising! Please help us prioritize with 👍 . We welcome all pull requests from the community as well. For more information, refer to the [CDK Developer...

Hi, Let me clarify this first. 1. Does it happen only when you update your EKS deployment by removing your custom [nodeRole](https://docs.aws.amazon.com/cdk/api/v1/docs/@aws-cdk_aws-eks.NodegroupOptions.html#noderole)? 2. Are you having this error in `cn-north-1`

I found the root cause here: https://github.com/aws/aws-cdk/blob/3b7431b6ac27f8557c22a8959ae1ce431f6d2167/packages/%40aws-cdk/aws-eks/lib/managed-nodegroup.ts#L380 In China, this should be `ec2.amazonaws.com.cn` instead.

OK I guess https://github.com/aws/aws-cdk/pull/22589 broke this. This has been removed in https://github.com/aws/aws-cdk/pull/22589 but actually required for AWS China region.