Serverless can't deploy when using a linked profile with mfa_serial

Hi all,

I’m having an issue where I can’t deploy to AWS with serverless when using linked profiles. My config and credentials files look like this:

(deploying to the application account)

config

[profile master]
output = json
region = eu-central-1

[profile application]
output = json
region = eu-central-1
source_profile = master

credentials

[master]
aws_access_key_id = AAAA12345678...
aws_secret_access_key = abcd12345...
mfa_serial = arn:aws:iam::123456789012:mfa/a.guy.called.luke

[application]
role_arn = arn:aws:iam::098765432109:role/Deployment
source_profile = master
mfa_serial = arn:aws:iam::123456789012:mfa/a.guy.called.luke

It seems like this issue is caused by the way that serverless parses the config file. It doesn’t handle the case where there is an mfa_serial entry in the credentials file.

Might I suggest using the credentials resolver that comes built into the AWS SDK? It handles all this kind of stuff automatically.

Thanks 😃

[HyperBrain]

@pmuens @eahefnawy I think the real problem here is, that only the credentials are loaded from the profile if present, but not the region see here. The correct fix should be, that the getRegion() method would query the profile (if present) and use the region from that too in its evaluation (using the impl class).

Nevertheless the region overwrite in validate should be changed to use getRegion() to set the options property. It ensures that options is set correctly. With that change the system would be consistent and support for profile regions would be implicit.

[pmuens]

Closing since this issue is quite stale and we’ve published newer versions with fixes for this in the past. Feel free to re-open if this is still an issue.