Pahud Hsieh

Yes I can't deploy even this to `cn-north-1` ```ts import { App, Stack, StackProps, aws_eks as eks, aws_ec2 as ec2, } from 'aws-cdk-lib'; import { KubectlV25Layer as KubectlLayer } from...

@Bruce-Lu674 I created https://github.com/aws/aws-cdk/issues/24743 for the missing `AmazonElasticContainerRegistryPublicReadOnly` bug FYR.

@Bruce-Lu674 The relevant team is working on it but I don't have ETA at this moment but I will update here when I see the issue is fixed(hopefully very soon)....

Hi @Bruce-Lu674 Are you able to deploy the cluster AND a nodegroup with cdk v2.65.0 in cn-north-1 like this? ```ts const cluster = new eks.Cluster(this, 'Cluster', { vpc, version: eks.KubernetesVersion.V1_24,...

@Bruce-Lu674 Unfortunately I can't even successfully deploy the cluster. I'll keep diving deep for the root cause. btw, do you have account on cdk.dev slack? Can you ping me on...

@ItielOlenick >Looks like the EKS is expecting ec2 service principal name as ec2.amazonaws.com.cn but CDK is giving ec2.amazonaws.com. I am still working on this to get it sorted with internal...

I can confirm we can successfully deploy EKS cluster in China regions with [escape hatches](https://docs.aws.amazon.com/cdk/v2/guide/cfn_layer.html) as below: ```ts import { KubectlV26Layer as KubectlLayer } from '@aws-cdk/lambda-layer-kubectl-v26'; const cluster = new...

@justin007755 This bug should have been fixed in https://github.com/aws/aws-cdk/pull/25215 Please install the latest AWS CDK and let me know if it works for you.

I am able to deploy this to `cn-north-1` with the nodegroup up and running. Hence resolving this issue. ```ts import * as cdk from 'aws-cdk-lib/core'; import * as eks from...

confirmed aws-eks-v2-alpha deploys in cn-north-1 as well.