This topic is a companion to another, which focuses on the Discourse configuration. Here we will set up a Cloudfront distribution as the reverse proxy before Discourse.
The only time you need this combination is when you already have a Cloudfront distribution for the primary hostname and would like to proxy a subfolder to a Discourse forum. This guide assumes the reader to have previous experience using Cloudfront in production.
When a user loads the site there are two network connections involved. Each has a different hostname:
- The web browser will issue a request to Cloudfront for the public hostname.
- Then Cloudfront will issue a request to the Discourse servers for the origin hostname.
.───────. .───────. .─────────. ( browser )───▶( CF )───▶( discourse ) `───────' `───────' `─────────'
For our example, we’re going to pretend your Discourse site will load from
This means there will be at least two origins defined – a default for the primary site and a second for the Discourse servers.
There will also be at least two behaviors, one pointing to each origin.
The default behavior and origin are not relevant for our purposes here; it must already be configured as appropriate to your needs. The Discourse-specific origin and behavior should be configured as follows.
The second origin for the Discourse servers should be pointed at the origin hostname.
Do not configure an origin path.
The protocol policy should be HTTPS, with TLSv1 as the minimum version.
The pattern needs to match the subfolder.
It should be attached to the origin configured as above.
It should redirect HTTP → HTTPS.
It should permit all HTTP verbs.
It should disable caching.
It should forward all client headers.