Unable to create EKSCluster with Java SDK

[38leinaD]

Describe the bug

I am having trouble creating an EKS Cluster using the CDK with Java.
I now used the aws-cdk-examples and am getting the exact same error:

EksPrivateCluster: fail: Expected closing tag 'meta' (opened in line 7, col 1) instead of closing tag 'head'.:358:1 Deserialization error: to see the raw response, inspect the hidden field {error}.$response on this object. [12:42:19] Reading cached notices from /home/daniel/.cdk/cache/notices.json Failed to publish asset 8c06a7775210aa362ae87c34bb7f3fab5bd1261dcdc431975963ee6b55bdef88:current_account-current_region

cdk version:
2.1007.0 (build d3f6c3c)

Any suggestions how to troubleshoot this and if this is just an environment-specific problem for me, please let me know.

Expected Behavior

EKS cluster should be created without errors.

Current Behavior

EKS cluster creation failes.
Error is
EksPrivateCluster: fail: Expected closing tag 'meta' (opened in line 7, col 1) instead of closing tag 'head'.:358:1 Deserialization error: to see the raw response, inspect the hidden field {error}.$response on this object. [12:42:19] Reading cached notices from /home/daniel/.cdk/cache/notices.json Failed to publish asset 8c06a7775210aa362ae87c34bb7f3fab5bd1261dcdc431975963ee6b55bdef88:current_account-current_region

Reproduction Steps

cdk deploy on this: https://github.com/aws-samples/aws-cdk-examples/blob/main/java/eks/private-cluster/src/main/java/com/amazonaws/cdk/examples/EksPrivateClusterStack.java

Possible Solution

No response

Additional Information/Context

No response

CDK CLI Version

2.1007.0 (build d3f6c3c)

Framework Version

See examples project: 2.175.1; but also newer versions

Node.js Version

v18.17.1

OS

Centos Linux

Language

Java

Language Version

Java openjdk version "17.0.7" 2023-04-18

[Aastha22j02]

Hi @38leinaD 👋

Thanks for sharing the issue! I had a look at your error message and it seems like there might be an issue during deserialization—especially this part:

Expected closing tag 'meta' (opened in line 7, col 1) instead of closing tag 'head'

This usually indicates that some HTML content (possibly an error page) was returned instead of the expected JSON response from the AWS API. This often happens when:

1. AWS credentials or region is misconfigured, causing the CDK to hit an unexpected endpoint.
2. A network proxy or firewall is modifying the HTTP response (common in corporate environments).
3. The asset publishing failed, suggesting maybe there's an issue with permissions or asset bundling.

---

🔍 Suggestions to Troubleshoot:

1. Check if you are authenticated properly:

   • Run aws sts get-caller-identity to confirm credentials.
   • Ensure you are targeting the correct AWS account and region.

2. Delete CDK cache:

   rm -rf ~/.cdk/cache

3. Try deploying with verbose logging:

   cdk deploy --verbose

   This might help you find where it's failing exactly.

4. Ensure required IAM permissions:

   • The IAM role/user should have full EKS, IAM, and CloudFormation permissions.
   • Try running cdk bootstrap again if it’s a fresh account/region.

5. Check for proxy settings:
   If you're behind a corporate proxy, you might want to bypass or properly configure it to avoid corrupting API responses.

---

Let me know if you'd like me to try reproducing this error with the same aws-cdk-examples repo and share my findings. 😊

Hope this helps!

Thanks,
Aastha 🙌

[38leinaD]

Thanks! deleting ~/.cdk/cache actually solved.

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.