Windows hosts created during `ecs-cli up` don't join the cluster.

[emisaacson]

Summary

Windows hosts created during ecs-cli up don't join the cluster.

Description

• Exact command run:

  ecs-cli up
    --keypair <my-keypair>
    --launch-type EC2
    --capability-iam
    --size 2
    --instance-type m5.large
    --vpc <my-vpc>
    --image-id ami-01b701d1a348a0d00 # Windows_Server-2016-English-Full-ECS_Optimized-2018.10.23
    --cluster-config <my-cluster-config>
    --ecs-profile <my-ecs-profile>
    --security-group <my-security-group-id (allows all ports 0.0.0.0/0 ingress and egress)>
    --region us-east-1
    --subnets <my-public-vpc-subnet>

• Which version of the CLI you are using? (Run: ecs-cli --version) 1.12.1 (e70f1b1)

• Which version of Go are you using? (Run: go version) No idea. Is the runtime bundled in the .exe on windows or something?

• What platform are you using to run ECS CLI commands? (E.g. Linux, MacOSX, Windows) Windows

Expected Behavior

Created hosts join the ECS cluster

Observed Behavior

Cloudformation completes successfully but the instances do not join the cluster.

If I run the same ecs-cli command above but substitute a linux AMI (e.g. "ami-045f1b3f87ed83659" # amzn-ami-2018.03.i-amazon-ecs-optimized) the instances join the cluster as expected.

Creating the Windows cluster through the AWS console with the same parameters above also works as expected.

[emisaacson]

I was able to fix this by replacing the mime-encoded bash script in UserData in the created CF stack with:

<powershell>
Initialize-ECSAgent -Cluster <ClusterName> -EnableTaskIAMRole -LoggingDrivers '[`"json-file`",`"awslogs`"]'
</powershell>