Skip to content

eksctl cluster throws error #8175

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
abhibaluias opened this issue Jan 31, 2025 · 4 comments
Closed

eksctl cluster throws error #8175

abhibaluias opened this issue Jan 31, 2025 · 4 comments
Labels
kind/help Request for help stale

Comments

@abhibaluias
Copy link

Thanks to all,

eksctl create cluster --name app-cluster --region us-east-1
Error: checking AWS STS access ΓÇô cannot get role ARN for current session: operation error STS: GetCallerIdentity, https response error StatusCode: 0, RequestID: , request send failed, Post "https://sts.us-east-1.amazonaws.com/": net/http: invalid header field value for "Authorization"

I have enabled authenticator for mfa Access. then the cluster not getting created.

aws sts get-caller-identity --profile default

Unable to parse response (no element found: line 1, column 0), invalid XML received. Further retries may succeed:
b''

pls help me resolve this issue

What help do you need?

@abhibaluias abhibaluias added the kind/help Request for help label Jan 31, 2025
Copy link
Contributor

Hello abhibaluias 👋 Thank you for opening an issue in eksctl project. The team will review the issue and aim to respond within 1-5 business days. Meanwhile, please read about the Contribution and Code of Conduct guidelines here. You can find out more information about eksctl on our website

@dims
Copy link
Contributor

dims commented Feb 21, 2025

does some AWS CLI general commands work? please try them first, for example

aws sts get-caller-identity
aws s3 ls

Copy link
Contributor

github-actions bot commented Apr 2, 2025

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

@github-actions github-actions bot added the stale label Apr 2, 2025
Copy link
Contributor

This issue was closed because it has been stalled for 5 days with no activity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Apr 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/help Request for help stale
Projects
None yet
Development

No branches or pull requests

2 participants