Skip to content
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

Error: Need to perform AWS calls for account ***, but no credentials have been configured #1201

Closed
1 task
wwhchung opened this issue Nov 14, 2024 · 4 comments
Closed
1 task
Labels
bug Something isn't working needs-triage This issue still needs to be triaged

Comments

@wwhchung
Copy link

Describe the bug

Within the last two hours, we are unable to use aws cdk deploy within a github action, with the error:
“ Need to perform AWS calls for account ***, but no credentials have been configured”

we have tried the runner action:
aws-actions/configure-aws-credentials@v2 v3 and v4

we have double checked that the following values are correct:
aws-access-key-id
‎aws-secret-access-key
aws-region

are you aware of any issues that may hav occurred within the last two hours (looking like Nov 14, 2024 00:00 GMT)

Regression Issue

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

Expected Behavior

CDK deploy works within a github action

Current Behavior

Receiving an error:
Need to perform AWS calls for account ***, but no credentials have been configured

Reproduction Steps

Configure to use credentials as per above.

Possible Solution

No response

Additional Information/Context

No response

@wwhchung wwhchung added bug Something isn't working needs-triage This issue still needs to be triaged labels Nov 14, 2024
@wwhchung
Copy link
Author

Update: I can confirm that the credentials are correct, because I can see via the IAM panel that the last service used was 'sts'. However, when I do cdk deploy --verbose, it gives the following error:
[03:21:38] Looking up default account ID from STS
[03:21:38] Unable to determine the default AWS account (InvalidClientTokenId): The security token included in the request is invalid

So, the credentials appear correct, as IAM shows it being used and accessing STS, but for some reason the default account id can't be determined.

@logg926
Copy link

logg926 commented Nov 14, 2024

+1

@wwhchung
Copy link
Author

We resolved this, [email protected] is broken.

Use [email protected]

Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working needs-triage This issue still needs to be triaged
Projects
None yet
Development

No branches or pull requests

2 participants