CommandRunner fails silenty to run `lambda invoke`

[chuxau]

I am simply running the command:

!Sub "sleep 10; aws lambda invoke --function-name ${functionName} --region ${AWS::Region} ; echo FINISHED > /command-output.txt"

• Have followed the guide here
• Have registered the CommandRunner resource type following the guide,.
• Although I don't see a Cloudformation registry in the console (as the guide suggests), I see a stack created by running ./scripts/register.sh --set-default, as well as the role .. also CloudFormation accepts my template using the resource type CommandRunner without any issues

But although a run status of success is exported in the default command runner logs, the command fails to invoke the lambda function .. with no errors.

Things I have tried

• I thought it could be a permissions thing due to leaving out the role, assuming the role used would be the role provisioned by register.sh, so I created an explicit role, ensure I gave it permissions to run lambda, but this made no difference.
• Then to verify there are no issues with the lamba function itself, I have run it on the console and it works fine.
• I have tried other simple commands:
• • aws s3 ls | sed -n 1p | cut -d ' ' -f3 > /command-output.txt .. no output, and no other errors
• • aws --version | cut -d ' ' -f1 | cut -d'/' -f1 > /command-output.txt .. no output, and no other errors

So, it just seems as if CommandRunner is broken and unable to run any aws commands, although the additional stack it auto-provisions is always built. Both the SubnetId & SecurityId are good and in use in other stacks

Please, is this utility still supposed to work or am I missing anything ?