# 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:** 9

<div class="post-metadata">

**Author:** ![michaeld](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/michaeld/32/1594_2.png) [@michaeld](https://meta.discourse.org/u/michaeld)\
**Post date:** [18 בדצמבר,‏ 2018,‏ 8:00pm UTC](https://meta.discourse.org/t/ec2-origin-exposed-by-google-web-crawler-with-discourse-cloudflare/104521/9 "2018-12-18T20:00:48Z")

</div>

> [@TempusOwl](#):
>
> adding security groups in AWS to only allow Cloudflare IPs inbound to force Cloudflare only (seems like it would break things in my opinion). My concern is this solution may break reverse nginx and NGINX rewrite rules I have to expose true IP of users instead of the cloudflare IP with moderation and logging

This is the correct solution. Your concern is unnecessary. Cloudflare is passing that IP in a HTTP header.

---

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