sam local start-api --profile option doesn't work with assumed role

My ~/.aws/config looks like:

[profile default]
region = us-east-1
output = json
[profile admin@other]
region = us-east-1
role_arn = arn:aws:iam::123456789012:role/admin
source_profile = default

Specifying --profile admin@other shows a warning in the logs:

2017/12/01 12:12:43 WARNING: No AWS credentials found. Missing credentials may lead to slow startup times as detailed in https://github.com/awslabs/aws-sam-local/issues/134

As a workaround I made a “dev” IAM user and access keys in the “other” account , and configured another awscli profile with those keys. Then --profile dev@other works fine.

[iph]

Interesting.

So, here’s my thought process so far:

Code where we initialize the session using options: https://github.com/awslabs/aws-sam-local/blob/develop/env.go#L128-L141 Godocs on session, search for: Shared Config Fields https://docs.aws.amazon.com/sdk-for-go/api/aws/session/

If the AWS_SDK_LOAD_CONFIG environment variable is set, or SharedConfigEnable option is used to create the Session the full shared config values will be loaded. This includes credentials, region, and support for assume role. In addition the Session will load its configuration from both the shared config file (~/.aws/config) and shared credentials file (~/.aws/credentials). Both files have the same format.

Maybe since we override with our own options, the value gets set to false by default and environment variables aren’t even attempted?

Gonna fiddle with that assumption a bit more.

[day2daychallenge]

How to solve this issue in windows?