Feature Request - accept equivalent of aws CLI --profile in mos aws-iot-setup

[EldritchJS]

It would be great if the mos tool would allow for using the equivalent of aws cli's --profile when using aws-iot-setup.

Looks like at least the following would be necessary:

1. Accept a --profile <PROFILE_NAME> arg when mos aws-iot-setup is called

2. If a profile arg was provided, add --profile <PROFILE_ARG> to

   mos-tool/mos/aws/aws.go

   Line 80 in e5f7d54

   output, err := ourutil.GetCommandOutput("aws", "configure", "get", "region")

   for the region acquisition

3. Use the same approach for getting aws_access_key_id and aws_secret_access_key as is used currently for getting the default AWS region (i.e. calling getCommandOutput()) and then assigning those results to the appropriate members of the cfg.Credentials object. All with the same potential use of --profile <PROFILE_ARG> as in point 2 above

[KyleVest]

We use a QA and PRODUCTION AWS environment so being able to specify the profile name would be very nice.

[gadget-man]

This would be useful for me - I'm having to change between Prod and Dev environments.

[stevefister]

@rojer I see you committed the change for --aws-profile. It doesn't seem to be working in 2.19.0. I have the AWS CLI configured with a default profile, but this flag seems to be completely ignoring it.