Custom S3 bucket

Custom S3 Bucket requires the SMALL plan or above.

You can store the discussion to your own S3 bucket and make search engines crawl the content under your own domain. Also good for backup. Here’s how you provide your bucket name: custom-s3Then you need to have a matching S3 bucket on Amazon with write permissions. Here’s how add one:

  1. Login to your AWS management console
  2. Click S3. Find your bucket or create a new bucket to the US standard region.
  3. Right-click to bucket properties
  4. Click Permissions from the right
  5. Click “Add more permissions”
  6. Add “” to the Grantee field and enable “Upload / Delete” checkbox

Without the permission we won't have access to drop anything there!

Proxy Content From Your Bucket

Now you will have the ability to proxy static content through your S3 bucket instead of, thus allowing you to disable indexing at so the content will only be indexed at your domain. You will first have to set up the S3 bucket to be publicly accessible as statically hosted content. Under the Permissions section of your bucket’s properties, click Add bucket policy. In the text field that opens, enter the following code block, but with your bucket name substituted:

    "Version": "2012-10-17",
    "Statement": [
            "Sid": "AddPerm",
            "Effect": "Allow",
            "Principal": {
                "AWS": "*"
            "Action": "s3:GetObject",
            "Resource": "arn:aws:s3:::YOURBUCKETNAME/*"

Save the policy, and then in the Static Website Hosting section of your bucket’s Properties, select Enable website hosting and enter your community name in the “Index Document” field (this will only be possible after the static indexes have been generated on your bucket at lease once). Then Save the setting and if you then visit your bucket’s publicly accessible URL (eg. you will see the index of your forum’s static content.

Links in your S3 bucket static page will not function properly when accessed this way. This is normal.

The final step is to set up the proxy from your website’s server. This will display Muut's static pages on your website, instead of By default, static pages reside on Muut’s servers. This can be changed to, instead, reside on your own server. First you need to change the URL on the Muut placeholder tag. Change from this:

<!-- Static content on Muut servers -->
<a class="muut" href="">
  Acme forums

to this:

<!-- Static content on your servers -->
<a class="muut" href="/i/your_forumname">
  Acme forums

Next you need to configure your webserver to serve this content from

Keep a close eye on the code difference between default and S3 bucket forwarding. In the examples, you simply have to replace with your S3 bucket’s public URL. These are notated/commented in the code below.

NGINX config
server {
  listen 80;
  # Muut configuration (this location block only)
  location ~* ^/i/ {
    # OR your S3 bucket URL
  location ~* ^/m/ {
Apache virtual host config
# Load these modules if not currently loaded
LoadModule proxy_module /usr/lib/apache2/modules/
LoadModule proxy_http_module /usr/lib/apache2/modules/
LoadModule ssl_module /usr/lib/apache2/modules/

<VirtualHost *:80>
  # Add this to your VirtualHost
  SSLProxyEngine On
  ProxyPass /i
  ProxyPassReverse /i
  # OR your S3 bucket URL (no /i on the end)
  ProxyPass /m
  ProxyPassReverse /m
Apache .htaccess config
<IfModule mod_rewrite.c>
  RewriteEngine On
  RewriteBase /
  RewriteRule ^i/(your-community-name)(/.*)?$$1$2 [P]
  # OR your S3 bucket URL (no /i in the middle)
  RewriteRule ^m/(.*)$$1 [P]
IIS 7 Web server web.config
    <rule name="Muut Index Rewrite" stopProcessing="true">
      <match url="^i/(.*)" />
      <action type="Rewrite" url="{R:1}" />
    <rule name="Muut Media Rewrite" stopProcessing="true">
      <match url="^m/(.*)" />
      <action type="Rewrite" url="{R:1}" />

The /m path is used for loading styles and scripts so you can customize with CSS. These /m proxy rules must remain pointing to If you have a working configuration for a different web server such as IIS or Lighttpd, please be kind and send it to Thank you!

You should also disable indexing on your muut settings so that if you have a custom bucket the content is not present in both locations.