Pahud Hsieh

Yes we could have a PR for that. But I am wondering why you opt in `addAutoScalingGroupCapacity` rather than [addNodeGroupCapacity](https://github.com/aws/aws-cdk/blob/c949076863719eea273bffa3ab45242b79caa99c/packages/aws-cdk-lib/aws-eks/lib/cluster.ts#L1820)? Is there any feature not supported in the managed nodegroups?

@isker Is it because Nodegroup currently does not support tagging ASG? This would be a huge tradeoff. In CDK, you still can create a managed nodegroup and a custom resource...

> Same issue here. if AL2 does not support EKS 1.33, why is the default image parameter amazon-linux-2 attached to it? Would it make our life easier if cdk uses...

@talalong I would say anyone of us can submit a PR to move this path forward. The idea of writing up a PR is not just about fix the code...

## Current vs Expected Behavior **Current Behavior:** ```bash npx ampx sandbox --profile= --identifier=mySandbox --debug # Output shows sandbox initialization Amplify Sandbox Identifier: my-profile Stack: amplify-myApp-myProfile-sandbox-xxxxxxxx Region: us-xxxxx # Then crashes...

The cluster would share the same SG with the managed nodegroups and if you check that SG, it essentially allows ingress from the same SG as the source so I...

If you create the eks.Cluster like this: ```ts const cluster = new eks.Cluster(scope, 'EksCluster', { version: eks.KubernetesVersion.V1_30, kubectlLayer: new KubectlLayer(scope, 'KubectlLayer'), mastersRole, vpc: ec2.Vpc.fromLookup(scope, 'Vpc', { isDefault: true }), defaultCapacity:...

@hakenmt It should be. Can you verify and let us know if it isn't?

Thanks for the report. Actually every Cluster comes with a built-in AwsAuth and you don't need to create a new one, instead, you should update the existing one like this...

@jfly Totally agreed with you. Yes, it sounds good to have a PR as the guardrail. Feel free to submit your PR for that. Thanks.