# Discourse instance unreachable on AWS

**URL:** <https://meta.discourse.org/t/discourse-instance-unreachable-on-aws/55006>\
**Category:** Product Support\
**Created:** [31 Dicembre 2016, 4:40pm UTC](https://meta.discourse.org/t/discourse-instance-unreachable-on-aws/55006 "2016-12-31T16:40:30Z")\
**Posts on this page:** 1\
**Showing post:** 16

<div class="post-metadata">

**Author:** ![auryn\_macmillan](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/auryn_macmillan/32/56633_2.png) [@auryn\_macmillan](https://meta.discourse.org/u/auryn_macmillan)\
**Post date:** [1 Gennaio 2017, 12:59am UTC](https://meta.discourse.org/t/discourse-instance-unreachable-on-aws/55006/16 "2017-01-01T00:59:36Z")

</div>

Alright, so I just went through the install process on a fresh CentOS 7 EC2. Everything seems to have gone smoothly, although I do notice a something weird:

```plaintext
$ ./launcher start app
which: no docker.io in (/sbin:/bin:/usr/sbin:/usr/bin)
6dd44a3a02af
Nothing to do, your container has already started!

```

Anyway, this instance seems to be suffering the same problem. So I’m guessing this means it must be something to do with my security group settings. Although as far as I can tell, they are all as they should be.

---

_[View the full topic](https://meta.discourse.org/t/discourse-instance-unreachable-on-aws/55006)._