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

CLI: Unable to resolve AWS account to use with cdk deploy --profile #33422

Closed
1 task done
briggsge opened this issue Feb 12, 2025 · 2 comments
Closed
1 task done

CLI: Unable to resolve AWS account to use with cdk deploy --profile #33422

briggsge opened this issue Feb 12, 2025 · 2 comments
Labels
bug This issue is a bug. closed-for-staleness This issue was automatically closed because it hadn't received any attention in a while. p3 package/tools Related to AWS CDK Tools or CLI potential-regression Marking this issue as a potential regression to be checked by team member response-requested Waiting on additional info and feedback. Will move to "closing-soon" in 7 days.

Comments

@briggsge
Copy link

Describe the bug

Having similar issue as of newest update related to previously-closed issue: #24744 (comment)

Regression Issue

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

Last Known Working CDK Version

v2.1691.0

Expected Behavior

I should be able to run cdk deploy --profile my_profile without issues regarding unknown accounts

Current Behavior

I receive the error "Unable to resolve AWS account to use. It must be either configured when you define your CDK Stack, or through the environment" and my stack cannot deploy.

Reproduction Steps

Run cdk deploy --profile my_profile.

Possible Solution

No response

Additional Information/Context

No response

CDK CLI Version

2.177.0

Framework Version

No response

Node.js Version

v22.13.1

OS

Mac, M-series processor

Language

TypeScript

Language Version

No response

Other information

No response

@briggsge briggsge added bug This issue is a bug. needs-triage This issue or PR still needs to be triaged. labels Feb 12, 2025
@github-actions github-actions bot added package/tools Related to AWS CDK Tools or CLI potential-regression Marking this issue as a potential regression to be checked by team member labels Feb 12, 2025
@pahud pahud self-assigned this Feb 12, 2025
@pahud
Copy link
Contributor

pahud commented Feb 12, 2025

  1. are you able to run aws --profile my_profile sts get-caller-identity?
  2. can you check the output of cdk deploy -vvv --profile my_profile and did you see any errors there?
  3. Was it previously working in any previous version but not working in 2.177.0 ?
  4. Can you share your ~/.aws/config ? (make sure you mask the account info)

@pahud pahud added response-requested Waiting on additional info and feedback. Will move to "closing-soon" in 7 days. p3 and removed needs-triage This issue or PR still needs to be triaged. labels Feb 12, 2025
@pahud pahud removed their assignment Feb 12, 2025
@pahud pahud changed the title (module name): (short issue description) CLI: Unable to resolve AWS account to use with cdk deploy --profile Feb 12, 2025
Copy link

This issue has not received a response in a while. If you want to keep this issue open, please leave a comment below and auto-close will be canceled.

@github-actions github-actions bot added closing-soon This issue will automatically close in 4 days unless further comments are made. closed-for-staleness This issue was automatically closed because it hadn't received any attention in a while. and removed closing-soon This issue will automatically close in 4 days unless further comments are made. labels Feb 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug This issue is a bug. closed-for-staleness This issue was automatically closed because it hadn't received any attention in a while. p3 package/tools Related to AWS CDK Tools or CLI potential-regression Marking this issue as a potential regression to be checked by team member response-requested Waiting on additional info and feedback. Will move to "closing-soon" in 7 days.
Projects
None yet
Development

No branches or pull requests

2 participants