# HubSpot Domain behind AWS CloudFront **URL:** \ **Category:** CMS Development\ **Tags:** admin, enterprise\ **Created:** [March 16, 2021, 3:29pm UTC](https://community.hubspot.com/t/hubspot-domain-behind-aws-cloudfront/33969 "2021-03-16T15:29:42Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![NEdwards](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/nedwards/32/39641_2.png) [@NEdwards](https://community.hubspot.com/u/NEdwards)\ **Post date:** [March 16, 2021, 3:29pm UTC](https://community.hubspot.com/t/hubspot-domain-behind-aws-cloudfront/33969/1 "2021-03-16T15:29:42Z")
Our current website is behind an AWS CloudFront distribution because the same domain serves multiple sites. One of these sites is moving to HubSpot. We have found and followed the documentation here ([Accounts Dashboard | HubSpot](https://developers.hubspot.com/docs/cms/developer-reference/reverse-proxy-support)) but are having issues at the last confirmation step. The time changes, the user-agent is right, the accept-language is good, cookie is not blank, protocoal is https, leftmost IP is my IP, but the IP-Determined Location is not right; it shows the CDN POP the origin request is coming from. Results of `/_hcms/diagnostics`: ![39545i97881BB03C18B081.png](https://d2qpr2jzcazej7.cloudfront.net/original/3X/b/a/ba74e700994f640341456ed330e6e3858b4bff56.png) ---
**Author:** ![dennisedson](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/dennisedson/32/28044_2.png) [@dennisedson](https://community.hubspot.com/u/dennisedson)\ **Post date:** [March 19, 2021, 1:32pm UTC](https://community.hubspot.com/t/hubspot-domain-behind-aws-cloudfront/33969/2 "2021-03-19T13:32:28Z")
Hello @NEdwards Not sure how I missed this, but are you still working on this problem? ---
**Author:** ![NEdwards](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/nedwards/32/39641_2.png) [@NEdwards](https://community.hubspot.com/u/NEdwards)\ **Post date:** [March 24, 2021, 6:38pm UTC](https://community.hubspot.com/t/hubspot-domain-behind-aws-cloudfront/33969/3 "2021-03-24T18:38:43Z")
Hi Dennis, No we’ve moved on and decided to go about the problem from a different direction since this method isn’t officially supports/recommended. ---
**Author:** ![REE](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/ree/32/98997_2.png) [@REE](https://community.hubspot.com/u/REE)\ **Post date:** [April 13, 2021, 2:29pm UTC](https://community.hubspot.com/t/hubspot-domain-behind-aws-cloudfront/33969/4 "2021-04-13T14:29:54Z")
Hi NEdwards, Would you please share the different direction/solution as we are in the exact same situation (and have exhausted all HS support options - none)? We are considering another option, but would appreciate learning from your experience. Please consider emailing me at [ruth@csrhub.com](mailto:ruth@csrhub.com). Thanks. ---
**Author:** ![NEdwards](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/nedwards/32/39641_2.png) [@NEdwards](https://community.hubspot.com/u/NEdwards)\ **Post date:** [April 13, 2021, 3:26pm UTC](https://community.hubspot.com/t/hubspot-domain-behind-aws-cloudfront/33969/5 "2021-04-13T15:26:05Z")
REE, We were never able to get support from our hubspot support contacts, and were a little turned off running it behind CloudFront because of all the warnings. We ended up re-designing and migrating the “sub-site” to another domain so that we can host it seperatly behind CloudFront. This is by no means ideal because it will affect our SEO, but we didn’t see much of another option. ---
**Author:** ![robertainslie](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/robertainslie/32/1875_2.png) [@robertainslie](https://community.hubspot.com/u/robertainslie)\ **Post date:** [May 10, 2021, 9:02pm UTC](https://community.hubspot.com/t/hubspot-domain-behind-aws-cloudfront/33969/6 "2021-05-10T21:02:30Z")
@NEdwards @REE - While this post is slightly old, this should work now. There was an issue with case sensitivity of headers that is now resolved. You can see that referenced on this post: [https://community.hubspot.com/t5/CMS-Development/HS-s-Reverse-Proxy-has-anyone-used-this-in-production/m-p/433629/highlight/true#M22837](https://community.hubspot.com/t5/CMS-Development/HS-s-Reverse-Proxy-has-anyone-used-this-in-production/m-p/433629/highlight/true#M22837) The Cloudfront setup should work to show the IP location information of the originating client. I have a setup in AWS that is configured properly that I can privately share if you’re interested, just shoot me a DM. Additionally, I just posted a thread that highlights a few ‘lessons learned’ that the HubSpot Tech Consulting team has seen regarding reverse proxy setup - [https://community.hubspot.com/t5/CMS-Development/Lessons-Learned-from-Setting-up-a-Reverse-Proxy-With-HubSpot-CMS/td-p/435961](https://community.hubspot.com/t5/CMS-Development/Lessons-Learned-from-Setting-up-a-Reverse-Proxy-With-HubSpot-CMS/td-p/435961)