-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
Cannot run cdk synth without specifying AWS credentials/region #2697
Closed
boyangfu opened this issue
May 30, 2019
· 3 comments
· Fixed by #2721 or MechanicalRock/tech-radar#14 · May be fixed by MechanicalRock/cdk-constructs#5, MechanicalRock/cdk-constructs#6 or MechanicalRock/cdk-constructs#7
Closed
Cannot run cdk synth without specifying AWS credentials/region #2697
boyangfu opened this issue
May 30, 2019
· 3 comments
· Fixed by #2721 or MechanicalRock/tech-radar#14 · May be fixed by MechanicalRock/cdk-constructs#5, MechanicalRock/cdk-constructs#6 or MechanicalRock/cdk-constructs#7
Labels
feature-request
A feature should be added or improved.
Comments
rix0rrr
added a commit
that referenced
this issue
Jun 3, 2019
No longer fail if an AWS Region cannot be determined anymore from current AWS config. Fixes #2697.
rix0rrr
added a commit
that referenced
this issue
Jun 3, 2019
No longer fail if an AWS Region cannot be determined anymore from current AWS config. Fixes #2697.
Why was this closed? Not requiring a region isn't the same as not requiring a profile |
To clarify, I'd like to run CDK synth without using the default profile, or specifying any profile, keys, or region |
This was referenced Aug 22, 2019
This was referenced Dec 12, 2019
We'd also like to do this, why was this closed with no comment? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm using another system to deploy my CF templates and there's no easy way right now for me to run CDK synth to generate the CF templates without specifying a profile. Seems like there should be a way to do this.
The text was updated successfully, but these errors were encountered: