Electron-builder: [Feature Request] [electron-publisher-s3] Use ~/.aws/credentials file as alternative to env variables

Created on 2 Mar 2017  路  4Comments  路  Source: electron-userland/electron-builder

It would be great if one could also provide his AWS credentials by using a ~/.aws/credentials file like recommended in the aws-sdk documentation (see https://aws.amazon.com/sdk-for-node-js/?nc1=h_ls) instead of having to supply them via environment variables.

deployment feature

Most helpful comment

By default, the SDK checks the AWS_PROFILE environment variable to determine which profile to use. If the AWS_PROFILE variable is not set in your environment, the SDK uses the credentials for the [default] profile. To use one of the additional profiles, change the value of the AWS_PROFILE environment variable. In the previous example, to use the credentials from the work account, set AWS_PROFILE=work-account.

All 4 comments

It is supported, but our check requires env in any case. It is bug.

~/.aws/credentials allows for multiple named profiles. Ideally it would be nice if electron-publish also supported specifying a profile by name.

we ended up writing our own script for pushing to S3 for this very reason. Would love to see this not require ENV vars

By default, the SDK checks the AWS_PROFILE environment variable to determine which profile to use. If the AWS_PROFILE variable is not set in your environment, the SDK uses the credentials for the [default] profile. To use one of the additional profiles, change the value of the AWS_PROFILE environment variable. In the previous example, to use the credentials from the work account, set AWS_PROFILE=work-account.

Was this page helpful?
0 / 5 - 0 ratings