# Having problems with configuring new Chef Automate AMI on AWS Marketplace

**URL:** <https://discourse.chef.io/t/having-problems-with-configuring-new-chef-automate-ami-on-aws-marketplace/10484>\
**Category:** Chef Automate\
**Created:** [February 25, 2017, 7:53pm UTC](https://discourse.chef.io/t/having-problems-with-configuring-new-chef-automate-ami-on-aws-marketplace/10484 "2017-02-25T19:53:07Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![tayloredwebsites](https://avatars.discourse-cdn.com/v4/letter/t/848f3c/32.png) [@tayloredwebsites](https://discourse.chef.io/u/tayloredwebsites)\
**Post date:** [February 25, 2017, 7:53pm UTC](https://discourse.chef.io/t/having-problems-with-configuring-new-chef-automate-ami-on-aws-marketplace/10484/1 "2017-02-25T19:53:07Z")

</div>

FYI, I am just starting on AWS, as well as Chef.

I am having problems starting up a Chef Automate AMI on AWS Marketplace. I was following the instructions on:  
[https://docs.chef.io/aws\_marketplace.html#chef-server-title-ami](https://docs.chef.io/aws_marketplace.html#chef-server-title-ami), and I completed the instructions ‘Launch the AMI’.

I am having problems with the instructions in ‘Configure Chef Automate’.

Step 1 says to 'Access the initial configuration page by going to https:///biscotti/setup.

- I am using the public DNS(IPv4) as the fqdn -\> [ec2-n-n-n-n.us-west-2.compute.amazonaws.com](http://ec2-n-n-n-n.us-west-2.compute.amazonaws.com) (n-n-n-n is the IP address)
- I keep on getting Site Can’t be Reached ERR\_CONNECTION\_TIMED\_OUT

What I have checked:

- my instance state is ‘running’.

- I can successfully ssh into the server with:  
ssh -i “/Users/xxxx/.ssh/xxxx.pem” ec2-user@

- When I ssh in, I get the following message:  
If you have not completed setting up the Chef Server please run through  
the setup wizard: [https://ec2-54-202-82-242.us-west-2.compute.amazonaws.com/signup](https://ec2-54-202-82-242.us-west-2.compute.amazonaws.com/signup)  
which does not work either, because apparently the website is not working.

- Is there a step missing to setup and/or to make sure that the web server is up and running, because it seem like it is not running?

---

<div class="post-metadata">

**Author:** ![Matt\_Stratton1](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/matt_stratton1/32/1753_2.png) [@Matt\_Stratton1](https://discourse.chef.io/u/Matt_Stratton1)\
**Post date:** [February 26, 2017, 2:44pm UTC](https://discourse.chef.io/t/having-problems-with-configuring-new-chef-automate-ami-on-aws-marketplace/10484/2 "2017-02-26T14:44:22Z")

</div>

First thing I would check - have you done the step : "

1. 

Configure security group to include the required ports 22, 443 and 8989.

---

<div class="post-metadata">

**Author:** ![Matt\_Stratton1](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/matt_stratton1/32/1753_2.png) [@Matt\_Stratton1](https://discourse.chef.io/u/Matt_Stratton1)\
**Post date:** [February 26, 2017, 2:47pm UTC](https://discourse.chef.io/t/having-problems-with-configuring-new-chef-automate-ami-on-aws-marketplace/10484/3 "2017-02-26T14:47:08Z")

</div>

Although I see you can ssh in, so likely you’ve done that step.

---

<div class="post-metadata">

**Author:** ![tayloredwebsites](https://avatars.discourse-cdn.com/v4/letter/t/848f3c/32.png) [@tayloredwebsites](https://discourse.chef.io/u/tayloredwebsites)\
**Post date:** [February 26, 2017, 2:55pm UTC](https://discourse.chef.io/t/having-problems-with-configuring-new-chef-automate-ami-on-aws-marketplace/10484/4 "2017-02-26T14:55:26Z")

</div>

I didn’t do anything with the ports, so that is clearly my problem. Port 22 probably is already open by necessity, and others would likely be opened as needed.

thanks,  
Dave