Alec Zebrick
Alec Zebrick
I found a workaround for my use case. I break it apart into two resources and simply change the annotation of the existing eks default storage class (allowed without --force)...
Had same issue on my end with: Received response status [FAILED] from custom resource. Message returned: No changes needed for the logging config provided Logs I deployed it with: `...
Trying to remove logging via CDK like this: Results in this change plan: Resulting in 1:49:09 PM | UPDATE_FAILED | Custom::AWSCDK-EKS-Cluster | EksClusterFAB68BDB Received response status [FAILED] from custom resource....