Nuno
Nuno
All posts

Moving Our Company Site from AWS Amplify to Cloudflare

Nuno's site moved from Amplify, CloudFront, Route 53 and SES to one Cloudflare Worker: the contact form, redirect domains, TLS and AI crawlers.
Vander Nunes
November 18, 2026
XInstagramYouTubeLinkedIn
Before and after diagram: four AWS services on the left, one Cloudflare Worker on the right

What it was

Until October 2026, nuno.io ran on AWS. The site is a Next.js app. Amplify built and hosted it. A separate CloudFront distribution served images. Route 53 held DNS. SES sent the contact form emails.

Four services for a marketing site. Each one was a reasonable choice when it was added, and each one was another console, another set of permissions and another line on the bill.

On 13 October 2026 the site went live on Cloudflare instead. What is left on AWS costs about $4 a month and is being retired.

Why move a site that worked

The site did not have a problem. It had more moving parts than it needed.

A company site is mostly static. It does not need a build-and-host platform, an image CDN and a DNS service from three different products. It needs a place to serve files fast, a way to handle one form, and DNS. Cloudflare does all three in one place, and the DNS was going to sit in front of the site anyway.

There was also a practical reason. I help clients put their platforms behind Cloudflare. Running my own site there means I use the same features I recommend.

A static export on a Worker

The Next.js site is built as a static export: plain HTML, CSS, JavaScript and images, no server rendering. The output is deployed to a Cloudflare Worker with static assets.

A static export only works if nothing on the site needs a server at request time. For a marketing site, that is usually true, and the one exception was the contact form.

Images moved with the rest of the files. The separate image distribution is gone.

The contact form

The form was the only part with a back end. On AWS it sent mail through SES.

Now the form is handled in the same Worker. Turnstile, Cloudflare's challenge, protects it from bots without a puzzle for real people. The Worker verifies the Turnstile token, then sends the message through Cloudflare Email Routing to my inbox.

One less service to run.

Redirect domains without a server

Like many companies, Nuno owns a few extra domains that should just redirect to the main site.

On Cloudflare, each redirect domain has a proxied DNS A record pointing at 192.0.2.1, an address reserved for documentation that goes nowhere. Because the record is proxied, Cloudflare answers the request itself, and a Redirect Rule sends visitors to the main site. The origin never exists. Nothing to run, nothing to patch.

Code
A   @    192.0.2.1   proxiedA   www  192.0.2.1   proxied

TLS settings

While moving, I tightened TLS: HSTS on, and a minimum of TLS 1.2. Clients older than TLS 1.2 are rare enough that a marketing site does not need to support them, and HSTS makes sure browsers never fall back to plain HTTP after the first visit.

HSTS is easy to turn on and slow to undo, because browsers remember it. Make sure every subdomain serves HTTPS before you enable it.

A separate domain for outbound email

Sales email goes out from a separate domain, not from nuno.io. If an outbound campaign hurts sending reputation, the main domain, the one clients write to, is not affected.

This is a small, cheap decision that is hard to make later, once the main domain has a history.

Letting AI crawlers in

Cloudflare makes it easy to block AI crawlers, and many sites do. I chose to allow them.

A consultancy site exists to be found. More and more people ask an assistant a question before they search. If the site is blocked, it cannot be the source of an answer. The content on nuno.io is written to be quoted: case studies, posts and solution pages. Blocking the tools that might quote it would work against the reason the site exists.

That is a choice for a marketing site. For a product with paid content or private data, I would decide differently.

The trade-off

Putting DNS, hosting, the form, email forwarding and redirects with one provider has a cost too. If Cloudflare has a bad day, all of it has a bad day together. On AWS, the pieces could fail separately.

For a company site I accept that. The site is a static export that any host can serve, and the DNS zone is small. For a product where every minute down costs customers money, I would think harder about where the single points are and keep a tested way out.

What I would tell someone doing the same

  • Check that your site really is static before choosing a static host.
  • Move DNS first, so the rest can be switched record by record.
  • Put the form in the same Worker, protected by Turnstile.
  • Use proxied records to a reserved address for redirect-only domains.
  • Turn on HSTS only after every subdomain serves HTTPS.
  • Keep sales email on its own domain.
  • Decide on AI crawlers on purpose, not by default.

If you want help moving a site or an application behind Cloudflare, get in touch.