Install and use Kong from the Kong 64-bit Amazon Machine Image (AMI) that’s available on the AWS Marketplace.
I created this ami and got a ec2 instance with no kong.conf and kong start failed. Is this the expected behavior of this image? Do you have any resources/installation steps I can attempt when the marketplace ami fails?
Hi @mister, EBS is listed as a required AWS service for Kong. Do you already have it set up?
Yes the ebs volume is created and attached to the ec2 instance. The documentation doesn’t mention where the kong.conf is created in the ami. I found kong.conf.default in etc/kong but I am not sure if this is the correct file. Also where should I look for any error logs, etc. I am new to Kong so I don’t really know where to look.