AWS Amplify + Cloudflare SSL Configuration

Tim Mendez
2 min readSep 12, 2020

TL;DR: Set proxy status to DNS only

I got stuck trying to configure AWS Amplify with Cloudflare while adding a custom domain in Amplify and ran into DNS issues that I just couldn’t for the life of me figure out.

Googling lead to nothing, so I’m hoping Googling will now lead to this.

SSL Configuration Step in AWS Amplify

This was the step I was stuck on. I let it run overnight but no dice. I had added the CNAME properly to my Cloudflare DNS list:

Cloudflare CNAME DNS Entry

I made sure that it didn’t include the extra periods at the end that AWS had added. Luckily, Cloudflare strips them by default, too.

Not sure if you caught it… but the `Proxy status` in the previous screenshot is set to Proxied. This is the no-no that by default Cloudflare does that will prevent the validation.

Simply changing Proxy status to DNS only will fix the issue.


Hope this helps.