DreamObjects guy here (and upstream author of the majority of the static website functionality).
I’ve passed that remark on. I don’t use the DNS in the panel at all, because it doesn’t fit my own needs.
The DNS entry for the root of the domain should be manually inserted A/AAAA records that go to the same IP as objects-website-us-west-1.dream.io. Amazon has a bit of magic here, with their “Alias” type in Route53, that gives CNAME-like magic within the constraints of DNS.
For the content of http://graham.xyz/ itself, you have two options:
- Upload the same static website you have uploaded at http://www.graham.xyz/
- Set the RedirectAllRequestsTo property in the website configuration (s3cmd can’t do it, but boto & aws-cli can), and generate redirect from http://graham.xyz/ to http://www.graham.xyz/
That’s a matter of the definition of ‘properly’. The SSL specification says that wildcards only ever match a single element, and never go past the period. So properly according to the SSL spec is to fail it.
You have two options:
- Disable the hostname part of the check, in the s3cmd config file:
check_ssl_hostname = no
- Tell s3cmd to use the path-based calling format, and keep strict SSL validation on, again in the s3cmd config file:
host_bucket = objects-us-west-1.dream.io
Lastly, yes, HTTPS for website-hosting is on the radar (including LetsEncrypt support), but I don’t have any timeline on it yet.