# Setting up SSL with my domain name and Discourse instance

**URL:** https://meta.discourse.org/t/setting-up-ssl-with-my-domain-name-and-discourse-instance/51626
**Category:** Support
**Created:** [October 17, 2016, 5:26am UTC](https://meta.discourse.org/t/setting-up-ssl-with-my-domain-name-and-discourse-instance/51626 "2016-10-17T05:26:13Z")
**Posts on this page:** 1
**Showing post:** 9

<div class="post-metadata">

### Author: ![SouperC](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/souperc/32/62875_2.png) [@SouperC](https://meta.discourse.org/u/SouperC)
#### Post date: [October 20, 2016, 3:23am UTC](https://meta.discourse.org/t/setting-up-ssl-with-my-domain-name-and-discourse-instance/51626/9 "2016-10-20T03:23:15Z")

</div>

Ah, your assets (photos) should not be on the same server as your Discourse install in cases like that… and yes you could be in for a world of hurt if your computer gets damaged/fails, gets stolen, motherboard takes out both drives (it happens!) etc etc.

You should be using a cloud storage solution like [Amazon S3](https://aws.amazon.com/s3/). You’ll have more available bandwidth for your users when they upload/download simultaneously as well as built-in fault tolerance. You can even go a step further and periodically backup assets on to [Amazon Glacier](https://aws.amazon.com/glacier/). And/or you could setup home box to keep a copy of what’s in S3 as well.

The great news is that discourse [supports S3.](https://meta.discourse.org/t/setting-up-file-and-image-uploads-to-s3/7229).

So, move your Discourse install onto a VPS (with or without SSL, up to you), configure S3 and feast your eyes on the awesomeness.

Lastly, you can also [configure your Discourse installation to backup to S3](https://meta.discourse.org/t/configure-automatic-backups-for-discourse/14855) as well.

---

_[View the full topic](https://meta.discourse.org/t/setting-up-ssl-with-my-domain-name-and-discourse-instance/51626)._