You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Can someone confirm this?
If you make a Script Task
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, 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.
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.