Error message not good enough in case only region is not defined
See original GitHub issueRepro:
- Clean up
~/.aws/config
,~/.aws/credentials
and any environment variables. - Run
aws configure
, supply access key and secret, but leave “region” toNone
.
Then, try to run cdk delpoy
. The error message is:
Stack hello-cdk does not define an environment, and AWS credentails could not be obtained from standard locations.
Also, there’s a typo “credentails” 😉
Issue Analytics
- State:
- Created 5 years ago
- Comments:14 (12 by maintainers)
Top Results From Across the Web
Understanding Success Criterion 3.3.1: Error Identification | WAI
the user fails to enter the proper abbreviation in to state, province, region, etc. field;; the user enters a state abbreviation that is...
Read more >Error handling in Step Functions - AWS Documentation
Step Functions identifies errors in the Amazon States Language using case-sensitive strings, known as error names. The Amazon States Language defines a set...
Read more >Python KeyError Exceptions and How to Handle Them
In this tutorial, you'll learn how to handle Python KeyError exceptions. They are often caused by a bad key lookup in a dictionary,...
Read more >How to correct a #VALUE! error - Microsoft Support
Excel shows the #VALUE! error when your formula includes cells that have different data types (text and numeric values). The #VALUE! error is...
Read more >VBA Error Handling - A Complete Guide - Excel Macro Mastery
Some runtime errors are not considered errors by VBA but only by the user. ... This behaviour is fine when you are writing...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Yes, this worked. Thanks!
#175 resolves this