`~/.aws/config` not respected, config read only from `~/aws/credentials`
See original GitHub issueAfter running aws configure
and setting your region to us-east-2
, it will be put in ~/.aws/config
and will be returned by aws configure get region
. However, when attempting to run dotnet.exe lambda package-ci --output-template compiled.template
from a folder whose aws-lambda-tools-defaults.json
does not have a region set, you will still get the error message Missing required parameter: --region
.
This can be worked around by adding region=us-east-2
to the bottom of your ~/.aws/credentials
file.
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (4 by maintainers)
Top Results From Across the Web
Configuration and credential file settings - AWS Documentation
The following examples show a credentials and config file with two profiles, region, and output specified. The first [default] is used when you ......
Read more >AWS_PROFILE not respected with aws credentials as ...
The Issue When you have an aws config file setup with a profile, and the credentials are stored as environment variables, sops will...
Read more >Missing credentials in config, if using AWS_CONFIG_FILE, ...
When using credentials in plain text everything works good but when I am trying to use environment variables it's not working. Error message....
Read more >Configuring the AWS SDK for Go V2
When you initialize an aws.Config instance using config.LoadDefaultConfig , the SDK uses its default credential chain to find AWS credentials.
Read more >MATLAB Answers
when I store my AWS credentials in the file .aws/credentials. However, when I try to use .aws/config instead, I get the error message....
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
Looks like this was a bug in the SDK that was fixed back in fall 2019 but the version of the SDK used by Amazon.Lambda.Tools hasn’t been updated in quite awhile. I’m working on updating Amazon.Lambda.Tools to the latest version of the SDK which should fix the problem.
This issue should have been addressed