Cloudformation stackset creates instance in default VPC

[Chan9390]

While self deploying metlo on custom VPC, the cloudformation stackset fails.

The reason is MetloSecurityGroup is created in a VPC provided in parameters however the MetloInstance doesnt consider the VPC parameter and creates in a default VPC.

So the stackset fails due to the following error and rolls back:

Security group sg-xxxxxxxxxxx and subnet subnet-yyyyyyyyyyyyy belong to different networks. (Service: AmazonEC2; Status Code: 400; Error Code: InvalidParameter; Request ID: aaa-bbb-ccc; Proxy: null)

[Chan9390]

I used the cloudformation script provided at https://my.metlo.com/ after signup

[akshay288]

Hey @Chan9390 sorry about that! Fixing ASAP

[Chan9390]

Heres the fix that worked for me:

Add a network interface instead of security group id:

                "NetworkInterfaces": [
                    {
                        "AssociatePublicIpAddress": "true",
                        "DeviceIndex": "0",
                        "GroupSet": [
                            {
                                "Ref" : "MetloSecurityGroup"
                            }
                        ],
                        "SubnetId": {
                            "Ref" : "SubnetId"
                        }
                    }
                ],

And add the subnet id in parameters.

As the cloudformation script for Metlo collector is not maintained in any public GitHub repo, I wasnt able to raise PR.