(aws_eks): Using the default cluster role triggers a cluster health issue

[Gum-Christopher-bah]

Describe the bug

Creating a new cluster with no user created role passed triggers a health event with the following message.

Hello,

Amazon EKS detected cluster health issues in your AWS account 1234567890.

The following is a list of affected clusters with their cluster arns, cluster health status and corresponding cluster health issues(s):
arn:aws:eks:us-east-1:1234567890:cluster/my-cluster : IMPAIRED : Your cluster is not using the Amazon EKS service-linked-role. We couldnt assume the role associated with your cluster to perform required Amazon EKS management operations. Check the role exists and has the required trust policy.

It seems like the role still works for normal operations, but the new observability checks do not play nicely with it.

Regression Issue

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

Last Known Working CDK Version

No response

Expected Behavior

Default role does not trigger the health event

Current Behavior

See Above

Reproduction Steps

Create a cluster

new eks.Cluster(this, 'hello-eks', {
  version: eks.KubernetesVersion.V1_31,
  kubectlLayer: new KubectlV31Layer(this, 'kubectl'),
});

Possible Solution

No response

Additional Information/Context

No response

CDK CLI Version

2.168.0

Framework Version

No response

Node.js Version

18.20.4

OS

Mac

Language

TypeScript

Language Version

No response

Other information

No response

[pahud]

Hi

Creating a new cluster with no user created role passed triggers a health event with the following message.

where did you see this event?

[pahud]

ref: V1587868095

[Gum-Christopher-bah]

If you go into the console, under ClusterHealth issues, it will take you to the dashboard showing the problem. It is very possible that this may have been a fluke, I haven't been able to reproduce the issue

[pahud]

@Gum-Christopher-bah

Thank you. Let me verify it on my end.

[pahud]

I didn't see that for now. Will keep watching it.

[pahud]

@Gum-Christopher-bah are you still seeing this warning in your console?

[Gum-Christopher-bah]

Hello @pahud
I have figured out how to recreate this issue. This pops up only when the cluster stack is deleting and the cluster itself is lagging behind for whatever reason, unable to be deleted. There is not an explicit dependsOn generated between the cluster resource and the role, so the role is deleted first, which causes this to fire. This issue can be closed, but it would be nice if the construct handled deletion in the proper order so this would not pop up. Thank you and apologies for not responding sooner