Connect your domain
Point an AWS Route 53 domain at your church website
Two records. About 5 minutes. Then usually under a minute.
The records
An example. Use the values on your own domain screen, which has a copy button beside each one — ours can change.
Do this
- 1Publish your site first. Route 53 is instant — your old site goes the moment you save.
- 2Route 53 → Hosted zones → your domain.
- 3Create record. Name empty. Type
A. Alias off. Value from the domain screen. Simple routing. - 4Add another record. Name
www. TypeCNAME. Value from the domain screen. - 5Create records.
- 6Back to the domain screen. It says Live on its own.
3 traps
- No
@The apex record name is genuinely blank. - Alias offAlias only targets AWS resources. We are not one.
- Wrong hosted zoneThe zone's
NSmust match Registered domains → your domain. If it does not, records save and nothing reads them.
Do not touch
NS · SOA · MX · TXT. MX is your church email — deleting one stops mail silently.
Not working
- Nothing after a few minutesWrong hosted zone. Check
NS. - Console rejected the recordOne already exists — edit it. Or Alias is on.
- One address works, not the otherOne record did not save.
- Permissions errorThe AWS user needs write access to the zone.
- Email stoppedAn
MXrecord was edited. Tell us, do not keep changing.
Please read. This is a guide, not professional advice. The AWS console changes without notice, so what you see may not match what is written here. These settings also control your church email, and a wrong change can stop mail arriving without any obvious sign. If anything does not match, or you are not sure, stop and ask whoever administers your AWS account — or ask us before you change it. You are making these changes in your own AWS account, and we cannot be responsible for them.