So the cname records sits nice and patiently in the admin panel. It’s been probably ~30hours. Atleast 24.
There used to be a records, which i deleted after i had added cname records. I don’t know what the ttl was on the a records. If the ttl on the now deleted A records were many days would it affect not seeing cname records at all?
How are you detecting that the records are not updating?
With hostnames, tools like dig and nslookup cannot see the underlying value you have set, and users only get A and AAAA responses with Cloudflare IPs in the response (even if you have a CNAME record defined in the dashboard). Internally within Cloudflare the change is essentially instant.
As @michael pointed out, a CNAME that’s set to (proxy) will appear as an “A” record that shows Cloudflare’s reverse proxy IP address.
However, neither hostname (www or the domain) load and show a 522 timeout. If you’ve pointed those records to a new server, it’s possible that it will only work with a CNAME record, so you will need to edit them so they’re DNS-Only.
Maybe S3 bucket did not have an SSL certificate as “default”?
I remember the Google Cloud Storage in start did not provide SSL certificate, so the only way to server a content via GCS bucket over HTTPS was to have “Flexible SSL” and being on a CNAME that points to GCS bucket.