Seth Geoghegan
11/02/2021, 9:57 PMAWS_CONFIG_FILE
parameter when running sst start
so I can specify a location of an alternative ~/.aws/config
fileSeth Geoghegan
11/02/2021, 9:58 PMpackage.json
as follows:
"scripts": {
"start": "AWS_CONFIG_FILE=/path/to/my/config AWS_PROFILE=staging AWS_SDK_LOAD_CONFIG=1 sst start --stage $(whoami)",
"remove": "AWS_CONFIG_FILE=/path/to/my/config AWS_PROFILE=staging AWS_SDK_LOAD_CONFIG=1 sst remove --stage $(whoami)",
}
Seth Geoghegan
11/02/2021, 10:00 PMAWS_CONFIG_FILE
You can't specify this value in a named profile setting or by using a command line parameter
Seth Geoghegan
11/02/2021, 10:00 PMSeth Geoghegan
11/02/2021, 10:01 PMyarn run start
will deploy to the same accountMichael Clifford
11/02/2021, 10:14 PMAWS_CONFIG_FILE
and AWS_PROFILE
settings may be at odds with each other, with AWS_PROFILE
taking precedence. In that shared config are you planning on having the aws_access_key_id
and aws_secret_access_key
stored? Because that is highly frowned upon, even in private repos.Michael Clifford
11/02/2021, 10:14 PMAWS_PROFILE
as something and then have users set that up locally with their own IAM creds (via aws configure --profile YOUR_PROFILE_NAME
)Seth Geoghegan
11/02/2021, 10:18 PMSeth Geoghegan
11/02/2021, 10:20 PMMichael Clifford
11/02/2021, 10:21 PMaws-sso-credentials
?Michael Clifford
11/02/2021, 10:22 PMSeth Geoghegan
11/03/2021, 2:18 AMSeth Geoghegan
11/03/2021, 2:19 AMSeth Geoghegan
11/03/2021, 2:19 AM