# Discourse instance unreachable on AWS **URL:** \ **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:** 26
**Author:** ![CaptainChemist](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/captainchemist/32/121252_2.png) [@CaptainChemist](https://meta.discourse.org/u/CaptainChemist)\ **Post date:** [7 Febbraio 2017, 12:12am UTC](https://meta.discourse.org/t/discourse-instance-unreachable-on-aws/55006/26 "2017-02-07T00:12:29Z")
@auryn_macmillan haha your response is amazing! 🙂 Two other errors that I had to deal with just in case you run into it too, is that with the automatic setup , the `DISCOURSE_SMTP_PASSWORD` is put in quotes automatically while other variables in that block do not have the quotes. I removed those quotes to match. Also, my admin email was [admin@mydomain.com](mailto:admin@mydomain.com), while discourse by default expects in my case [admin@community.mydomain.com](mailto:admin@community.mydomain.com) (based on `DISCOURSE_HOSTNAME`). If you go down to the second to last line you can uncomment this line and fill in your details: `- exec: rails r "SiteSetting.notification_email='admin@mydomain.com'"` Then when you go to configure the site, it will properly send you the email you need to get started. That step is only necessary if the total domain of your website differs from your email. Good luck and thanks everyone for getting this conversation started. --- _[View the full topic](https://meta.discourse.org/t/discourse-instance-unreachable-on-aws/55006)._