ELKStackMultiAZinPrivateVPC about elk-stack

[satterly]

The ELK_Stack_Multi_AZ_in_Private_VPC.json cloudformation template assumes your VPC is configured as per AWS guidelines which is to have a public and private subnet in each availability zone for the region. See http://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/VPC_Subnets.html

If that isn't the case, then you would need to modify the ElkAutoScalingGroup section of the cloudformation template to explicity list the availability zones for the subnets you pass as parameters (or make the list of AZ's a new parameter). This option assumes that all AZ's have a private subnet configured...

"AvailabilityZones": { "Fn::GetAZs": "" },

The easiest thing to do would be to delete your existing VPC, if possible, and then use the EC2 instance launch wizard which will create a correctly configured VPC for you...

If you use the launch wizard in the Amazon EC2 console to launch a T2 instance type and you do not have any existing VPCs, the wizard creates a nondefault VPC for you, with a subnet in each Availability Zone, an Internet gateway, and a route table that routes all VPC traffic to the Internet gateway. For more information about T2 instance types, see T2 Instances in the Amazon EC2 User Guide for Linux Instances.