EDIT: resolved myself, answer below.
When I try to use "ask deploy" on the command line/terminal I get this error:
[Error]: Get Lambda ARN ask-custom-testcli-default failure for custom/default. AccessDeniedException: User: arn:aws:iam::123456789012:user/bob is not authorized to perform: lambda:GetFunction on resource: arn:aws:lambda:us-east-1:123456789012:function:ask-custom-testcli-default
- I've tried using "ask deploy -p default" and got the same error. (Default actually exists on my IAM Roles and is listed as a profile when I use "ask init" and get the same error. "bob" is not.)
- My name is Bob and I've presumably entered my first name at some point somewhere, BUT I'm not quite sure where "user/bob" is coming from, as it does not exist on my AWS/Alexa account, or my IAM Roles, or in my Skill's directory! (My Mac also does not have a "bob" user.)
- Permissions for GetFunction seem correct on IAM for default profile, and for the Lambda function itself.
- I've uninstalled and reinstalled ask-cli. I've deleted aws-cli in case that somehow interfered with it. I've tried it on an old skill that it used to work on, and I've tried it with two new skills using "ask-new".
Not sure if the error is caused by the mystery bob user it keeps bringing up or if that's a red herring - but if anyone has any ideas for getting to the bottom of where the user field draws from, I'd appreciate it.