Using ssm send-command with a Script named "NUnit Runner" throws error

[Jeremy Roelfs]

Can someone confirm this?

If you make a Script Task

• Name it "Run Test"
• Any interpreter
• inline

And in the script use the aws ssm send-command --instance-ids "<id>"

Make sure it passes when you run the plan.

Now go and change the Name of the Script Task to "NUnit Runner"

When you run the plan again you will receive this error:

Parameter validation failed:
Invalid length for parameter InstanceIds[0], value: 19, valid range: 10-10

 Once the Script fails on this error. It will continually fail no matter what you name it. You must remove the send-command or create a new script.

I think it is a bug.

[somethingblue]

Hi Jeremy,

I found a post that may explain this behavior, however, it's interesting this only happens if you rename the task. 

If you run the same command from terminal do you get the same behavior?  In case the instance id is causing the problem it would happen in the terminal too.

Let me know and we'll go from there.

Cheers,

Branden

[Jeremy Roelfs]

I do not seem to have any issues running it in cmd or powershell. But if my credentials are not set correctly, then it does throw an error on that instance-id.

EDIT: Not the same Parameter error though.

I'll try to reproduce and map my exact steps.

[somethingblue]

Thanks Jeremy.  Let me know the exact steps and we'll go from there.