Connect Route 53 to DigitalOcean CDN

I’m using Route 53 as my DNS provider and I’d like to use DigitalOcean’s CDN, how would I go about routing a subdomain to a DO CDN?

I’ve setup 2 CNAME records, one to the origin endpoint and one to the edge endpoint CNAME CNAME

The first one gives me a 404 The second one gives me a NoSuchBucket response

How do you route a subdomain to your DigitalOcean Spaces CDN with a different DNS provider?


Submit an answer
You can type!ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

To use Let’sEncrypt certificate with your subdomain you would need to move you DNS management to DigitalOcean.

Steps to using Let’sEncrypt:

  1. Register a domain with a registrar. Update the name server on the registrar to point to DO’s name server. Check $ whois <TLD name> | grep ‘Name Server’ to make sure it’s pointing to DO DNS and not the registrar’s DNS.
  2. Go to the Networking tab and make an entry for your TLD in DO DNS.
  3. Create a bucket and enable CDN. Create a subdomain for xxx.<tld> using LE and assign it to the CDN url.
  4. Upload some assets on the bucket. Make sure it is accessible through the Edge url first.
  5. Then try accessing it through the subdomain url.
  6. If it does not work it’s almost always one of two reasons 1. The DNS routing isn’t working properly. 2. The cert was previously assigned to another CDN and the TTL was too long and hasn’t expired.

You can also bring your own certificate in which case the DNS management can be elsewhere (Route 53 for example) but you do need to setup the CNAME manually. For a Space named <space> in <region>which is configured with the domain, you would need a CNAME => <space>.<region>