Bring your own CDN

Brandfolder can support any CDN provider. Simply create a new distribution in your current CDN provider and point it to Brandfolder's CDN origin domain.

Who can use this?

Plans:

  • Brandfolder

This isn't a native Brandfolder feature, but something that you set up and configure for your own account. If you choose to bring your own CDN, you need the Brandfolder Smart CDN feature and some Brandfolder CDN bandwidth. 

This article demonstrates configuration using Amazon CloudFront. As mentioned previously, you can set up any CDN provider with similar methods.

1. Select Create distribution. 

2. Designate your origin info using the following settings: 

  • Origin domain: cdn.bfldr.com
  • HTTPS only
  • HTTPS port: 443
  • Minimum origin SSL protocol: TLSv1.1
  • Origin path: Leave blank
  • Origin name: Any name of your choice. For example: Custom-CDN.bfldr.com
  • Enable origin shield: Yes
  • Origin shield region: Choose a region that makes the most sense for your usage.

3. Set up your default cache behavior with the following values:

  • Compress objects automatically: Your choice. We select yes
  • Viewer protocol policy: Redirect HTTP to HTTPS
  • Allowed HTTP methods: GET, HEAD
  • Restrict viewer access: No

4. Establish your cache key origin as follows:

  • Legacy cache settings
  • Headers: None
  • Query strings: All (This is important for image transformation functions)
  • Cookies: None
  • Object caching: Customize
  • Minimum TTL: 86400 (One day. We recommend one day at minimum or as long as one week, depending on your content workflows)
  • Maximum TTL: 86400
  • Default TTL: 86400
  • In this case, we're forcing everything to one day, but you can set your own timeframe.

5. Enable the following settings:

  • Price class: Use all edge locations (best performance)
  • AWS WAF web ACL: Blank
  • Alternate domain name (CNAME): Choose the domain or subdomain you'd like to use. We're using yourcustomcdn.brandfolder.com.
  • Custom SSL certificate: Select the certificate for the domain you want to use. If you don't have one, request a certificate from the AWS console.

6. Finally, make these selections:

  • Supported HTTP versions: HTTP/2
  • Standard logging: Off
  • IPv6: On

After entering all this information, select Create Distribution.

Then, point the alternate domain name to this distribution.  

Create a CNAME record and point that CNAME to the CloudFront distribution. You can find that value by going to Cloudfront, selecting your distribution, and finding the distribution domain name.

7. Test your new Brandfolder custom CDN.

All CDN providers are supported.

Keep in mind

  • Image management functions work as usual.
  • Logging of the pages your image lives on doesn't work within the Brandfolder platform. We use CDN logs for this, and since you're bringing your own CDN, we don't have access to those logs.  
  • Brandfolder automatically invalidates CDN objects when updated while using the Brandfolder-hosted CDN. If you bring your own CDN, that invalidation doesn't occur automatically. This is why you should set your caching TTL to a timeframe that makes sense for your use case.
  • To invalidate updates, you can use the Brandfolder API Webhooks to do this on your own.