# EC2 Origin Exposed By Google Web Crawler With Discourse & CloudFlare

**URL:** <https://meta.discourse.org/t/ec2-origin-exposed-by-google-web-crawler-with-discourse-cloudflare/104521>\
**Category:** Self-hosting\
**Created:** [18 בדצמבר,‏ 2018,‏ 5:32am UTC](https://meta.discourse.org/t/ec2-origin-exposed-by-google-web-crawler-with-discourse-cloudflare/104521 "2018-12-18T05:32:56Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![Stephen](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/stephen/32/95011_2.png) [@Stephen](https://meta.discourse.org/u/Stephen)\
**Post date:** [18 בדצמבר,‏ 2018,‏ 9:41am UTC](https://meta.discourse.org/t/ec2-origin-exposed-by-google-web-crawler-with-discourse-cloudflare/104521/3 "2018-12-18T09:41:20Z")

</div>

Did you use the AWS FQDN to configure your Discourse instance? It shouldn’t even be responding to that hostname unless you used it in your configuration.

Discourse doesn’t need to know the DNS name AWS has assigned, you just need an ‘a’ record pointed at the public IP for your ELB. Your machine doesn’t need to be addressable remotely at all.

---

_[View the full topic](https://meta.discourse.org/t/ec2-origin-exposed-by-google-web-crawler-with-discourse-cloudflare/104521)._
