Plugin picks `default` aws credentials rather than `profile` specified in the serverless.yml

[vishwasnavadak]

We have a profile created for serverless deployments that has required permission to get the SSM parameters. But when I have this plugin, it threw the error that it did not have access to get the parameters.

After inspection, I realized that the plugin was picking the [default] credentials from ~/.aws/credentials instead of the supplied profile.

Is it expected behavior? I feel this is confusing for the users who does not have the default profile setup as the one which is set as deployment profile on serverless.yml

[allenmadsen]

As a work-around I set the AWS_PROFILE environment variable before running the serverless deploy.

[vishwasnavadak]

Let me try that out.

[klimentina-djeparoska]

I have the same problem

[tarnauceanu-andrei]

Same here

[afr5]

Same here