Closed mikekhristo closed 8 years ago
Same issue as https://github.com/awslabs/aws-shell/issues/72. The aws
prefix should not be provided (it's already assumed), so you just need to type:
aws> lambda list-functions
Let's track this issue over at #72. Please feel free to add your thoughts there. The immediate thing we'll be adding is better error messages, but we may potentially change the aws-shell to also support providing the aws
prefix depending on customer feedback.
The command I entered was fully auto-completed so it should work (and it does work with the regular aws cli)