yacloud/acme.sh
1
0
Fork 0
mirror of https://github.com/acmesh-official/acme.sh.git synced 2025-04-30 07:22:44 +00:00
Code Issues Packages Projects Releases Wiki Activity

Basic support for AWS creds in ~/.aws/credentials

Browse Source 
Adds code to attempt to get AWS creds from ~/.aws/credentials, if it exists, and the creds aren't already set.
It's pretty simplistic, it just grabs the first values from the file, it does not honour [sections] in the ini formatted credentials file.
This commit is contained in:
obeliskm 2019-06-27 18:07:48 +12:00 committed by GitHub
parent 8e36695bc4
commit e2f7072209
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 14 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
dnsapi/dns_aws.sh
View File

@ -26,6 +26,20 @@ dns_aws_add() {
_use_container_role || _use_instance_role _use_container_role || _use_instance_role
fi fi
# if not already set, attempt to get AWS creds from a local creds file.
# this is naive, it just grabs the first values from .aws/credentials
# it does not honour [sections] in the ini formatted credentials file.
if [ -z "$AWS_ACCESS_KEY_ID" ] || [ -z "$AWS_SECRET_ACCESS_KEY" ]; then
CREDFILE="${HOME}/.aws/credentials"
if [ -e "$CREDFILE" ]; then
AWS_ACCESS_KEY_ID=$(grep -m 1 -i AWS_ACCESS_KEY_ID "$CREDFILE" | cut -f 2 -d"=" | tr -d ' ')
AWS_SECRET_ACCESS_KEY=$(grep -m 1 -i AWS_SECRET_ACCESS_KEY "$CREDFILE" | cut -f 2 -d"=" | tr -d ' ')
fi
# todo: if the key is found in the creds file, then if we can assume it'll be there in the future,
# then there's likely no point saving it in the account config, so we should do what needs to be done
# to disable saving the AWS creds in the acme.sh config.
fi
if [ -z "$AWS_ACCESS_KEY_ID" ] || [ -z "$AWS_SECRET_ACCESS_KEY" ]; then if [ -z "$AWS_ACCESS_KEY_ID" ] || [ -z "$AWS_SECRET_ACCESS_KEY" ]; then
AWS_ACCESS_KEY_ID="" AWS_ACCESS_KEY_ID=""
AWS_SECRET_ACCESS_KEY="" AWS_SECRET_ACCESS_KEY=""